Tokenization gives merchants the ability to securely save payment information. By tokenizing a customer's payment method, merchants can schedule future card-on-file charges and create recurring payment plans.
Info |
---|
Tokens save the payment method while fully protecting the cardholder’s sensitive data, simplifying your PCI compliance requirements. Payrix Tokens do not expire. |
Note: While Payrix Tokens do not expire, OmniTokens do have an expiration date, shown on the Transaction Details page.
Payrix provides the following resources for implementing tokenization and card-on-file/recurring payments:
...
This page includes the following information about Payrix’s tokenization and recurring payments solutions:
...
...
How to Tokenize a Customer’s Payment Method
...
Info |
---|
Technically, the customer’s address is not required when creating a token. However, we strongly recommend including it to prevent future payments from being blocked/declined due to AVS mismatch. Please visit our API Reference for optional fields & additional information. |
Location | Syntax | ||
---|---|---|---|
URL |
| ||
HEADER |
| ||
BODY |
|
Creating a Token SimultaneouslyAs You Submit a Transaction in the API
...
Info |
---|
Please note, the syntax for creating a token simultaneously as you submit a transaction differs slightly for card payments and eCheck payments (as shown in the sample code below). |
Location | Syntax | ||
---|---|---|---|
URL |
| ||
HEADER |
| ||
BODY (for card payments) |
| ||
BODY (for eCheck payments) |
|
...
Recurring Payments
One of the key features of tokenizing a payment method is the ability for Merchants to use it to schedule recurring payments. This solution gives a Merchant the ability to charge their customer’s tokenized payment method in their desired amount and at their desired frequency. For example, Merchants can utilize recurring payments to charge their customers a monthly fee or for billing on a subscription-based business model.
...
Info |
---|
The API syntax for CoF card payments and CoF eCheck payments differs slightly as shown below: |
Location | Syntax | ||
---|---|---|---|
URL |
| ||
HEADER |
| ||
BODY (for card payments) |
| ||
BODY (for eCheck payments) |
|
...
Related Articles
Child pages (Children Display) |
---|