Errors
TLS connection failures
Section titled “TLS connection failures”A TLS handshake failure produces no HTTP response from the API.
| Symptom | Action |
|---|---|
| The server requires a certificate | Supply --cert and --key |
| The server rejects the client certificate | Confirm the certificate issuer and environment |
| The client cannot verify the server certificate | Configure the correct server CA |
| The client reports a protocol error | Confirm the deployed TLS protocols |
Do not disable TLS verification.
HTTP errors
Section titled “HTTP errors”Mapped service errors contain a string code and a message.
| HTTP status | Code | Cause |
|---|---|---|
| 400 | 20003 |
The from parameter is absent or blank |
| 400 | 20004 |
A timestamp is invalid |
| 400 | 20005 |
The country is absent or blank |
| 400 | 20006 |
The end time is not after the start time |
| 401 | 20002 |
The service rejected the certificate identity or entity eligibility |
Example:
{"code": "20003", "message": "Missing 'from' date"}A missing or blank to, or a non-integer limit, returns HTTP 400. Some validation and server errors use a different response format; check the HTTP status before reading code and message.
For HTTP 500 or a connection timeout, you can retry the report query with the same filters.
For HTTP 401, ask your assigned Net Money Integration Manager to check the certificate status and entity eligibility.
For repeated server errors, contact your Integration Manager with the request time and response.
Never include your private key.
Empty results
Section titled “Empty results”HTTP 200 with an empty array is not an authentication error.
Check the entity, country, time range, and optional filters.
A missing fee does not exclude a payment from the report. If an expected payment is missing, ask your Integration Manager to investigate. Use a certificate for the merchant whose report you need; consolidated reports across an integrator’s merchants are unavailable.

