Skip to content

Get a client certificate

Net Money signs your client certificate. You create the private key yourself and send Net Money only a certificate signing request (CSR). Your private key never leaves your systems.

The CSR must use an RSA key of at least 2048 bits and contain a Common Name (CN).

Terminal window
openssl req -new -newkey rsa:2048 -nodes \
-keyout merchant.key \
-out merchant.csr \
-subj "/CN=your-company.example"

This writes two files:

  • merchant.key: your private key. Store it like a password and never send it to anyone.
  • merchant.csr: the signing request you send to your Integration Manager.

Each CSR can be submitted only once. To request another certificate, create a new CSR.

2. Send the CSR to your Integration Manager

Section titled “2. Send the CSR to your Integration Manager”

Send merchant.csr to your assigned Net Money Integration Manager. Confirm which merchant or integrator account should own the certificate. Your Integration Manager arranges certificate issuance and activation for that account. Send only the CSR; never send merchant.key or another private key.

An integrator uses its own account’s certificate when submitting for sellers. Do not request or use each seller’s private key.

Your Integration Manager provides the issued certificate in PEM format. Save it as merchant.crt and use it with the private key you created in step 1.

Certificates are valid for 365 days. Renewal is due 30 days before expiry: create a new CSR and send it to your assigned Integration Manager. Coordinate issuance and the client switch with them before the old certificate expires. A request with an expired, revoked or inactive certificate fails with 401.

Gateway requests also require the account’s current certificate. Coordinate the client switch when a replacement becomes current; do not assume the old certificate remains usable until its expiry date. Rotation within the same account preserves its caller identity and payment retry scope.