Tokenization & Registration

NOTE: You should be fully PCI compliant if you wish to perform tokenization requests server-to-server (as it requires that you collect the card data). If you are not fully PCI compliant, you can use the COPYandPAY tokenization tutorial to collect the payment data securely.

Tokenization allows you to store the payment data for later use. This can be useful for recurring and/or one-click payment scenarios.

This guide describes how you can store the data using our Server-to-Server API, how you can subsequently use the stored card details for a one-click payment and how to delete stored data.

Storing the payment data

There are two methods for creating a token

 

Store the data during a payment

A payment’s data can be stored at the same time as the payment by sending the createRegistration parameter with a value of true. This is done by sending a POST request to the /payments endpoint.

Try it out in the interactive editor below and you will find that you get the additional response parameter registrationId. This parameter allows you to access the stored payment data during subsequent operations (see use cases below).

Brand:

VISA

Brand:

MASTER

Brand:

AFTERPAY

Brand:

AIRPLUS

Brand:

ALIA

Brand:

ALIADEBIT

Brand:

AMEX

Brand:

APPLEPAY

Brand:

ARGENCARD

Brand:

BOLETO

Brand:

CABAL

Brand:

CABALDEBIT

Brand:

CARNET

Brand:

CARTEBANCAIRE