Skip to content

Gateway errors

Mapped Gateway errors return a string code and a message. Use the code for handling; messages can include configuration details or change as validation improves.

{
"code": "18025",
"message": "Seller is not assigned to the authenticated integrator"
}
HTTP status Code Meaning and action
400 18012 Invalid request body or unsupported fields, including redirect or identity overrides. Remove those fields.
400 18016 Invalid checkout settings. Integrator requests cannot use optional checkout handover.
400 18020 Missing or blank sellerEntityId for an integrator. Supply the actual seller.
400 18030 Missing merchantTransaction. Put business fields inside that object.
401 18002 The certificate identity is not usable. Check that the certificate is active, current, and accepted for the environment.
403 18022 A direct merchant supplied another seller’s ID. Omit the ID or use its own entity ID.
403 18023 The authenticated account cannot submit payments. Ask your Integration Manager to check its access.
403 18024 The selected seller is not a merchant. Use the actual merchant’s entity ID.
403 18025 The seller is not assigned to this integrator. Ask your Integration Manager to verify the merchant assignment.
403 18028 Integrator submissions are disabled in this environment. Confirm availability with your Integration Manager.
404 18021 The supplied seller is unknown. Check its entity ID.
404 18026 The opportunity is unavailable for that seller, including an ownership mismatch. Check the seller/opportunity pair.
409 13002 The same caller/seller/key was reused with different business data. Retry with the original request.
422 18019 New acceptance lacks one or both opportunity return URLs. Net Money must configure the fields listed in the message.
422 18027 Configured return URLs are invalid. Net Money must configure absolute HTTPS URLs without embedded credentials.
422 16002 A required account is not billable. Check the caller’s complete billing address and, for new acceptance, the seller’s receiving account.
500 18029 Net Money could not process the payment. Contact your Integration Manager and retain the original request and idempotency key.

These are the integration-specific errors, not every possible payment failure. Amount, country, currency, risk, and other validation errors can also reject a request. Both return URLs are required for new acceptance; authorized retries retain the original accepted settings, as explained in Retry safely.

Connection failures and uncertain outcomes

Section titled “Connection failures and uncertain outcomes”

A TLS handshake failure occurs before any HTTP response. See mTLS troubleshooting. Some connection and server failures may use another response format.

For server errors or timeouts, retry with the same authenticated account, seller, idempotency key, and business data. A new key can create another payment. Contact your Integration Manager if the result remains uncertain.