Troubleshooting
mTLS failures happen in two places: during the TLS handshake, before any HTTP response, or after it, when the gateway checks your certificate against your merchant account.
The connection fails (no HTTP response)
Section titled “The connection fails (no HTTP response)”| Symptom | Cause | Fix |
|---|---|---|
alert certificate required / handshake failure |
No client certificate was sent | Pass --cert and --key (or configure your HTTP client) |
unknown ca / bad certificate |
The certificate was not signed by Net Money for this environment | Use the certificate issued for this environment |
protocol version / unsupported protocol |
Your client does not offer TLS 1.3 | Enable TLS 1.3 |
unable to get local issuer certificate |
Your client does not trust the gateway’s server certificate | Add --cacert with the CA certificate from Net Money |
401 Unauthorized
Section titled “401 Unauthorized”The handshake succeeded but the certificate is not usable for your merchant account:
{ "code": "18002", "message": "Unauthorized: ..." }The certificate may be unknown, expired, revoked, inactive, or no longer current. Ask your assigned Net Money Integration Manager to verify its status. If a replacement is needed, create a new CSR and send it to them.
Check what you are sending
Section titled “Check what you are sending”openssl x509 -in merchant.crt -noout -subject -serial -enddateThis shows the subject, the serial number and the expiry date. Include the serial number when you contact your assigned Net Money Integration Manager. Never send your private key.

