Card schemes introduced the Scheme Token technology for e-commerce card payments. As a certified Token Requestor - Token Service Provider, Pay-Jet supports Scheme Tokenization and can provide tokenization advantages to it's customers.

Briefly explained: What are Scheme Tokens?

Scheme tokens (also Network tokens) are used to process card payments in e-commerce and mobile wallets (like Google Pay or Apple Pay, enabling payments also in brick-and-mortar shops). The card company (Scheme) fills the role of the token service and manages the token system. This architecture ensures end-to-end tokenization of the payment flow from the merchant to the responsible Scheme.

Like the credit card wallet Click to Pay (see here), the Scheme Token technology is based on a unified set of technical rules defined by EMVCo. EMVCo is the international association of the six leading credit card companies Visa, Mastercard, American Express, Discover, JCB, and China Union Pay.

The development of the Scheme Token concept aims to make online payments by credit and debit card even more secure and easier for consumers while at the same time achieving similar authorization rates as in stationary retail. To this end, in the future, shoppers’ card data – such as the card number (PAN) – is to be kept out of the online payment flow as far as possible. The physical card will be replaced by the Scheme Token (sometimes also referred to as the Network Token), which has several additional advantages over already established gateway token systems.

Scheme Tokens in Pay-Jet Cockpit

Pay-Jet Scheme Token Service (CSTS) is engine that provides connection to Card Scheme Token Services:

  • Visa VTS (Visa Token Service)
  • MasterCard MDES (MasterCard Digital Eneblement Service)

CSTS is able to replace PAN with Scheme Token and use Scheme Token for payment processing.

CSTS also provides additional functionalities, like Account Updater and Digital Card image.

Payment processing

Payment processing with Scheme Tokens is core functionality of CSTS.

CSTS is completely taking over of Token payment processing on your behalf, without you needing to modify your current integration.

You can keep and continue to use Pay-Jet Pseudo Card Number and CSTS takes care of translation to Scheme Tokens.



To configure CSTS for your MerchantID, please contact Pay-Jet Support.

Helpdesk will also able to provide information if your Acquirer is supporting Scheme Tokens.


There is no impact on your current integration, no new Request or Response parameters.


Account updater (Optional functionality)

New card information coming from the issuing bank is also part of Scheme Tokens solution suite.

Suppose the card associated with the token expires and is renewed. In that case, changes like the expiration date, PAN, cardholder contact information can be updated directly in the Token Vault of the token service without creating a new token.


In case of token expiry, Pay-Jet Cockpit is able to push this information to you via HTTP Notification.

You then do not need to worry anymore about expired tokens which can result in payment declines and customer friction.


In order to use this service, you would need to set up notification endpoint on your side and inform our Helpdesk about it.

HTTP POST to Merchant's endpoint

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

KeyFormatCNDDescriptionBeschreibung

MID

ans..30

M

MerchantID, assigned by Pay-Jet

HändlerID, die von Pay-Jet vergeben wird

KeyFormatCNDDescriptionBeschreibung
PayID

an32

M

ID assigned by Cockpit for the payment, e.g. for referencing in batch files as well as for capture or credit request.

Vom Cockpit vergebene ID für die Zahlung; z.B. zur Referenzierung in Batch-Dateien sowie im Capture- oder Credit-Request.

KeyFormatCNDDescriptionBeschreibung
XID

an32

M

ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Cockpit

Vom Cockpit vergebene ID für alle einzelnen Transaktionen (Autorisierung, Buchung, Gutschrift), die für eine Zahlung durchgeführt werden

KeyFormatCNDDescriptionBeschreibung
TransID

ans..64

MTransactionID provided by you which should be unique for each paymentIhre eigene TransaktionsID, die für jede Zahlung eindeutig sein muss

KeyFormatCNDDescriptionBeschreibung
cardJSONMCard response dataObjekt der Kartendaten

Parameters in Request are encrypted with Blowfish password.

Card JSON object contains new expiry date for given Pay-Jet Pseudo Card Number.

Digital card image (Optional functionality)

Merchants can obtain the appropriate “Card Art” for a token from the relevant token service, i.e., information on the actual visual appearance of the physical card. The cardholder sees an authentic image of his card in the design of the issuer bank in his customer account. This creates a higher level of trust in the payment process.

Coming soon.




  • No labels