Save your loyal customers’ payment information securely and PCI-compliant in the background as a token (aka alias) to make repeat purchases or one-click checkouts easily. Check the section saving payment information in our docs to see how this process works.
By default, the alias option is not active in your merchant configuration. Please contact us to activate the tokenization option for your account.
Except for credit & debit cards and loyalty & gift cards, you will be required to contact your acquirer or payment method provider to activate an additional option for your account. If the required option is not active on the acquiring level, an error will be returned if you try to create an alias.
Any alias created after a payment or a dedicated registration is unique. All payment methods share a common format:
- Possible characters:
- Length: 32 characters
The following table shows the payment methods supporting tokenization. It also shows you if a payment method supports registration only or payment and registration at the same time.
Credit and Debit Cards
Loyalty & Gift Cards
Apple Pay ¹
Google Pay ¹
Migros Bank E-Pay
Samsung Pay ¹
¹ Apple Pay, Google Pay, and Samsung Pay transactions are processed as card transactions. In other words: The saved cards in your customer's Apple Pay, Google Pay, or Samsung Pay wallets are processed by your configured debit or credit card acquirers.
² For Byjuno registrations you will need to provide additional parameters within your init requests in the objects
INT. The required parameters may vary from merchant to merchant. Please double-check with Byjuno which information will be required for your contract. No additional parameters are required in your requests to debit a Byjuno alias. For payments with a Byjuno alias you may send optional parameters within
customData located in the object
Updated 24 days ago