Skip to main content

Card Tokenization

Tokenization allows you to have more control around initiating payments for users and their cards. This approach facilitates recurring and Merchant-Initiated Transaction (MIT) use-cases.

At a high-level, a payment flow involving tokenization would entail:

  • Consent token creation for a user's card: Card details may be specified via Stitch's Hosted UI (directly by the user), or to Stitch's Secure API. Following this, Stitch provides you with a consent token ID to represent the card.
  • Transaction Initiation using a previously-created consent token: For any valid consent token ID, you may then initiate a transaction to be charged on the respective card. For 3DS-enforced transactions, the card user would be required to 3DS-verify before the transaction is successfully completed.