TABLE OF CONTENTS
RocketGate's gateway allows you to process your payment using the Network Tokens provided by VISA and Mastercard, for your Merchant. The use of Network Token instead of PAN (Primary Account Number, in other word the credit card number) increases the security level of the payment, and by doing so reduces the cost at the acquirer side and increase the approval rate.
Token is a widely used term, in this particular context we refer to VISA / Mastercard using a combination of “PAN + Merchant” to create a Network token. This Network Token can be used for subsequent transactions, for ONE merchant only. Merchant in this context means the company, the legal entity, and can have multiple accounts at different banks.
When a customer joins for the first time (CIT), and provide his credit card. A token is created, and a cryptogram is created, which means there are 2 Network Tokens events.
When an existing customer does a 1-click payment (CIT), or any other sort of CIT. The existing token is reused, a cryptogram is created, which means there is 1 Network Token event.
When a transaction is triggered by the merchant (MIT recurring or MIT unscheduled), the existing token is reused, no cryptogram is needed, which mean there is 0 Network Token event.
- RocketGate is billing the Network token service per event, as per the logic above. An event can be a token creation attempt, or a cryptogram creation attempt. Please note some issuers do not support Network Token yet, in such case the Network Token creation will be declined. When it happens, RocketGate is not attempting to create a cryptogram.
- The Network token will be used when the processor / acquirer supports it, and the PAN will be used if the processor / acquirer does not support Network Tokenization. To know if your processor / acquirer support Network Token, please ask at firstname.lastname@example.org
- Cascading logic: if cascading is enabled, and if the transaction with Network Token is declined, then RocketGate will cascade to PAN on the same account. Then existing cascading logic will apply.
- A Network token will be created for new customers only.
- If a RocketPay user is joining the merchant for the first time, then a Network Token will be created as well.
- If you are using Hosted Page, you could use the Split testing feature to share traffic between sites, enable Network Token on one site only, and measure performance. See article here: https://help.rocketgate.com/a/solutions/articles/28000003885?portalId=28000007151
Here are a list of the features and options RocketGate will implement gradually:
- 3DS: the flow of event to combine Network token and 3DS is the following: create the token, create a cryptogram, do the 3DS authentication using the token, run the transaction
- Even when cascading is not configured, if the Network Token is declined, then the transaction could be cascaded to the PAN on the same account. This would be controlled by a merchant option, CascadeNetworkTokentoPAN.
- Migration of existing Customers: for the existing customers and card-on-file, a Network Token could be created on the next payment, either CIT or MIT.
- Card Art: the Schemes could send an actual image of the credit card (without the PAN) replicating all the look and feel of the physical card provided by the issuer. This card art image could be used by the merchant to showcase it on the customer.
- Use Network Token for Xsell and Upsell
How to get started?
Please contact our support team at email@example.com to setup your merchant for Network Tokenization.
Here is the information that RocketGate requires to enroll your merchant with VISA and Mastercard:
- company primary legal name
- primary website url
- company city
- company country code
- primary contact email
- business identification type
- business identification value (like the EIN in the US)
You can provision Network Tokenization on your RocketGate Merchant or specific accounts, and then enable it on specific site(s).
TABLE OF CONTENTS