For additional flexibility with real-time, recurring, and card-on-file transactions, Merchants have the ability to securely save their customers' card payment and eCheck data by creating a token. 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. Tokens do not expire. |
Table of Contents |
---|
...
How to Tokenize a Cardholder’s Payment Method
There are two ways in which a cardholder’s payment data can be saved for CoF & recurring payment transactions:
...
Merchants have the ability to tokenize a cardholder’s payment method data directly in the Portal via the Customers section on the Dashboard menu. When creating a Customer customer, the Merchant will be prompted to enter the cardholder’s personal information, including name, address, and email address.
Info |
---|
Saving address information on a Customer customer is not technically required to create a token. However, it is strongly recommended that it the customer’s address be saved to the record to increase successful recurring and card-on-file transactions with when using the token. |
...
Once a Customer customer is created, the a Merchant can attach a saved payment method (token) to that Customer customer for future CoF or recurring billing.
A Merchant can also attach multiple tokens to a customer if they have more than one payment method that will be used for future CoF and recurring payment transactions.
Info |
---|
For our full step-by-step instructions for creating a Customer & attaching a tokenized payment method, please visit our Portal User Guide. |
Tokenizing a Payment Method Via the API
A customer’s payment method can also be saved (tokenized) via the Payrix API. This is done by sending a POST request to the /tokens endpoint. Within the BODY of the request, you will include the customer’s personal information (name, address etc.), as well as the payment method (card/account number, exp. date etc.) that you would like to tokenize.
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. |
...
You also have the ability to tokenize a customer’s payment method simultaneously as you submit a transaction via the API. To do this, you will need to include the customer’s personal information within the BODY of your POST request to the /txns endpoint.
...
Location | Syntax | ||
---|---|---|---|
URL |
| ||
HEADER |
| ||
BODY (for card payments) |
| ||
BODY (for eCheck payments) |
|
...
Recurring Payments
One of the key features of Tokenizing 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.
...
To summarize, a plan determines the amount & frequency of a recurring payment, and customers can be added to a plan via a subscription.
...
Related Articles
Child pages (Children Display) |
---|