Skip to content

Authentication

Reporting requires mutual TLS (mTLS). Send a client certificate and its private key with each request. The environment must trust the certificate issuer.

Use a certificate issued for your merchant account and the environment you are calling. Reports are limited to that account. An integrator’s certificate does not provide consolidated access to its merchants’ reports. See Scope and data limits.

Your account also needs the billing and bank-account details agreed with Net Money. Ask your Integration Manager to confirm that the account is ready for reporting.

  1. Get the Reporting URL from your Integration Manager.
  2. Ask your assigned Net Money Integration Manager to arrange a client certificate for that environment and entity. Follow the CSR and certificate guide; send only the CSR, never your private key.
  3. Store the private key securely.
  4. Confirm the server CA requirements with your Integration Manager.

Staging and production use separate certificate authorities. Use the client certificate issued for the requested environment.

Use HTTPS with TLS 1.3.

Terminal window
export REPORTING_URL=https://reporting.example.com
curl --cert merchant.crt --key merchant.key \
--get "$REPORTING_URL/v1/reporting/transactions" \
--data-urlencode 'from=2026-08-01T00:00:00Z' \
--data-urlencode 'to=2026-08-02T00:00:00Z' \
--data-urlencode 'country=DE'

Replace the example URL and filters with values for your environment. If your environment uses a private server CA, add --cacert net-money-ca.crt. Do not disable server certificate verification.

A TLS handshake failure occurs before an HTTP response. A certificate identity rejection after the handshake returns HTTP 401.

The API reference describes mTLS, but a web page cannot attach your private key to an API request. Use curl or an HTTP client with client-certificate support.