Skip to main content
A tokenization request collects and securely stores a payer’s payment details for future use. It allows you to save a payment method as a token without initiating a payment. Tokenization requests are used when you need to charge later, reuse payment methods, or support off-session payments.

​
How tokenization requests work

Tokenization requests follow a simple flow: create, collect details, store, and reuse.
  1. Create a tokenization request Define the payer (optional) and supported payment methods.
  2. Present the collection experience Use a hosted page or embedded element to collect payment details.
  3. Payer submits details The payer provides payment method information (e.g. card or bank details).
  4. Store tokenized payment method The payment method is securely stored as a token and can be used in future payment flows.

​
Hosted vs embedded

Tokenization requests can be fulfilled through two integration models:

​
Hosted pages

A hosted page is a secure, Acclaim-managed page accessed via a link. Use hosted pages to:
  • Collect payment details without building UI
  • Share links via email or messaging
  • Ensure secure handling of sensitive data

​
Embedded elements

Embedded elements allow you to collect payment details directly within your application. Use embedded elements to:
  • Control the user experience
  • Embed secure payment forms
  • Maintain a consistent product flow

​
What is stored

When a tokenization request is completed:
  • Payment details are securely stored and tokenized
  • Sensitive data is not exposed to your systems
  • A payment method token is returned for future use
This token can be used to:
  • Create future payment requests
  • Initiate payments without re-collecting details

​
Relationship to payment requests

  • Tokenization requests collect and store payment details
  • Payment requests collect funds
You can combine both flows:
  1. Tokenize a payment method
  2. Use the stored method in a future payment request

​
Payment methods

Tokenization requests support payment methods that can be stored for reuse. Examples include:
  • Cards
  • Bank debit methods
Supported methods vary by country and currency.

​
Payers

A tokenization request can optionally be associated with a payer.
  • Known payer → store and reuse payment methods
  • Unknown payer → collect and associate during the flow

​
Status and tracking

Each tokenization request has a lifecycle and status. Statuses typically include:
  • Pending or awaiting completion
  • Completed
  • Failed
Use webhooks to:
  • Track completion
  • Store tokens in your system
  • Trigger follow-up workflows

​
When to use tokenization requests

Use tokenization requests when you need to:
  • Collect payment details without charging immediately
  • Support future or recurring payments
  • Enable off-session payments
  • Reduce friction for repeat payers

​
Best practices

  • Tokenize once, reuse many times
  • Associate tokens with payers for easier reuse
  • Limit supported payment methods to relevant options
  • Use webhooks to capture completion events

​
Summary

  • Tokenization requests collect and store payment details for future use
  • No funds are moved during tokenization
  • Payment methods are stored as secure tokens
  • Tokens can be reused in future payment flows
Last modified on March 29, 2026