A Recurring Token, also known as a Commerce Token (CT), is a reusable token that securely stores a customer's card information for future transactions. It is ideal for registered users, subscriptions, and one-click checkouts.

🔄
Unlike One-Time Tokens, CTs do not expire and can be used multiple times for authorized customers.

How to Generate a Recurring Token

Recurring Tokens are generated when capturing a card associated with a registered customer. There are two supported flows:

Tokenization Form

Hosted form for capturing card data securely.
Include the customer.uniqueId to associate the token.

Direct Tokenization

Send the CustomerId in the API request to generate a reusable token.

⚠️
Recurring Tokens require a valid customer record. Make sure the customer is created before invoking the tokenization.

How to Use the Recurring Token

Once generated, the recurring token must be sent in the Token field when creating a purchase.

Refer to Create a Purchase for full request structure and options.

🧠
If the issuer supports it, purchases can be made without CVV for stored cards, enabling one-click checkout experiences.

Best Practices

✅

Always retrieve the CommerceToken from the customer profile using the Get Customer API.

Never expose CTs in the frontend.

Only use CTs with trusted customers and ensure data privacy.

Validate expiration date before attempting a charge.

Use the CVV Form if CVV is required for verification.

Next Steps

Create a Purchase

Use the Token field with the CT to process a transaction.

Get a Customer

Retrieve stored tokens from the customer profile.

Tokenization Form

Learn how to collect cards and associate them with registered customers.