Net Money Gateway
The Net Money Gateway is the merchant-facing API for Net Money payments. You use it to create payments, check their status, and configure payment callbacks.
Authentication
Section titled “Authentication”Every request is authenticated with mutual TLS (mTLS). There are no API keys: your client certificate identifies your merchant or integrator account. Set it up once:
If something fails, see Troubleshooting.
API reference
Section titled “API reference”The API Reference lists every endpoint, request body and response.
Transaction IDs and statement references
Section titled “Transaction IDs and statement references”Payment creation returns transactionId, the Net Money identifier for the payment. Treat it as an opaque string: store it exactly as returned and use it for status requests, callbacks, and reports. Your merchantTransactionId remains your own order or payment reference.
The bank statement reference includes the Net Money transaction ID and, where space permits, a shortened version of your merchantReference. Statement formatting varies between banks. Use the transaction ID to match a bank statement entry to a payment. Your full original merchantReference is available in reports.
Direct and integrator payment requests
Section titled “Direct and integrator payment requests”The same POST /v1/payment shape serves direct merchants and integrators:
{ "idempotencyKey": "order-123", "merchantTransaction": { "monetaryValue": { "amount": 39.99, "currencyCode": "EUR" }, "merchantOpportunityId": "online-shop", "merchantTransactionId": "order-123", "merchantReference": "Order 123", "country": "DE" }}For integrator traffic, add the actual merchant’s sellerEntityId at the top level.
Direct merchants may omit it; a supplied ID must match the merchant identified by the client certificate.
A merchant working with an integrator can also submit payments directly using its own certificate.
Confirm with your Integration Manager that integrator submissions are available for your account and environment.
Follow Integrator payments for a complete request, caller/seller/fee attribution, onboarding requirements, retry rules, and current status/reporting limitations. See Gateway errors for stable error codes.
For a new payment, both success and failure redirect URLs must already be configured on the selected seller opportunity.
Neither URL may be supplied in the payment request, at the top level or inside merchantTransaction.
If either configured URL is missing, empty or blank, new payment acceptance returns HTTP 422, code 18019
(MISSING_REDIRECT_URL_CONFIGURATION), with a message listing the missing field(s).
The new payment is not created. Ask your Integration Manager to check the return URLs configured for that opportunity.
An authorized retry retains the original accepted destinations. Later configuration changes do not replace them; see Retry safely.
Optional Stripe Checkout handover remains available to approved direct merchants; it is not enabled for integrator requests.

