Server-to-Server Registration Tokens

Server-to-Server Registration Tokens

This Server-to-Server guide describes how you can store card and non-card data and subsequently use the stored details to perform payment transactions.

To better understand registration tokens in eCommerce, please read Tokenization Guide.
To use network tokens issued by the card networks for your payments, please refer to Server-to-Server Network Tokens.
To collect card data, you must be PCI-DSS compliant. To minimize your compliance requirements, please use PIPE Registration Tokens.

Use cases

Standalone tokenization

The merchant collects card data from shopper and initiates the registration tokenization. No payment request/flow involved. A registration token is synchronously provisioned and returned to the merchant. The registration token can then be used in subsequent payments.


How it works

Create the token

Send the tokenization request with the collected card data.

OPTIONAL

Send payment using the token

Send payment using the stored registration token.

Transactions:
RG
RG
DB
DB

1. Create the token

Perform a server-to-server POST request with the required customer data, but excluding paymentType. The response to a successful request is an id that should be stored and used in subsequent payments.


Sample request:

2. Send payment using the token

Perform a server-to-server POST request over the registration token retrieved in the previous step.
Alternatively, use one-click payment to authorize the payment with a selected stored registration token.

Sample request:


See also