Server-to-Server Network Tokens

Last updated:November 15, 2026

This Server-to-Server guide describes how you can store the data, provision a network token with the involvement of the card network and then subsequently use the network token authorization data for a payment.

To better understand what network tokens are, please read Tokenization guide.
To know which acquirers do support network tokenization, please reach out to your Customer Success Manager.
To collect card data, you must be PCI-DSS compliant. To minimize your compliance requirements, please use COPYandPAY Network Tokens.

Explore More

You can switch the content of this page to learn how to use Omni Tokens as merchant tokens alongside network tokens for payments. Toggle the switch below to see detailed information and update the page content accordingly.


Use cases

Tokenization during payment

The merchant collects card data from shopper and initiates tokenization along an account verification (zero amount authorization) or initial purchase. A merchant token is synchronously created and returned to the merchant once the payment is complete. The merchant token can then be used in subsequent payments. In the background, a network token is being provisioned by the card network with Issuer involved in the token approval process. The payment is authorized with real card data or with the network token if available and active.

How it works

Create the token during payment

Send the payment request with the collected card data asking for the card to be tokenized.

Transactions:
RG
RG
TK
TK
DB
DB
TF
TF
or
RG
RG
TK
TK
PA
PA
TF
TF

1. Create the token during payment

To create a token during payment, perform a server-to-server POST request with createRegistration=true and all required payment and customer data, including payment type, amount, and currency. A successful request will return a registrationId that should be stored and used in subsequent payments.

Tokenization response

The response will include a token transaction history, indicating that the network token provisioning process has started with the card network. Due to a simulated 2-second delay in the test environment, the network token provisioning request will be in flight, and the payment will continue using the original PAN. The network token fetching is attempted, but the response will indicate that the provisioning request is still in progress.

When the network token is fetched, the response will also provide the original PAN BIN. This information will be exposed in the payment response as part of the card.bin parameter. It’s important to note that the network token BIN is different from the original PAN BIN. This distinction is crucial for post-authorization issuer BIN management, ensuring that you have the necessary details to handle the transaction accurately.

Add the Card on File agreement parameters (standingInstruction) to mark this payment as the initial cardholder-initiated transaction (CIT · INITIAL) of the agreement. The agreement type determines how the stored card can be used later.

Card on File agreement type
Unscheduled Recurring Installment

Select the pills to see how the standing-instruction parameters and the sample request below change for each agreement type. Unscheduled covers one-click payments and once-off industry practice payments; Recurring and Installment cover merchant-initiated charges on a schedule.

Cardholder creates agreement (CIT · INITIAL)

			

Sample request:

What this creates
The Card on File agreement is established with this initial CIT. Storing standingInstruction.initialTransactionId and standingInstruction.agreementId in your own system is optional. They are saved together with the card and agreement in the token, and are added automatically to each following MIT transaction. For all parameters see the COF parameter reference and the Card on File guide.

See also