Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

For additional flexibility with real-time, recurring, and card-on-file transactions, Merchants have the ability to securely save their customers' card payment and/or 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.

Tokens save the payment method while fully protecting the cardholder’s sensitive data, simplifying your PCI compliance requirements. Tokens do not expire. 


How to Tokenize a Cardholders’s Payment Method

There are two ways in which a cardholder’s payment data can be saved for CoF & recurring billing transactions:

Creating a Customer in the Payrix Portal

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, the Merchant will be prompted to enter the cardholder’s personal information, including name, address, and email address.

Once a Customer is created, the Merchant can attach a saved payment method (token) to that Customer for future CoF or recurring billing.

For our full step-by-step instructions for creating a Customer & attaching a tokenized payment method, please visit our Portal User Guide.

The Payrix Platform offers a Recurring Payments (/subscriptions) solution that enables you to schedule recurring transactions directly via our Portal.

As an alternative, you can create your own recurring transaction database. In this case, there are a few required fields you will need to submit in order to be in accordance with card brand mandates - see recurring payment guidelines here.

Because the customer's information (e.g. address) remains linked to each token, issuer declines due to AVS mismatch or similar are a lot less likely. If your client would like to be able to keep multiple payment methods on file, they can save multiple tokens per customer.

Saving AVS information on a Customer is not required to create a token. However, it is strongly recommended that it be saved to the record to increase successful recurring and card-on-file transactions with the token.

  • No labels