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.
|Payment method||Registration Only||Payment + Registration|
|Credit and Debit Cards|
|Loyalty & Gift Cards|
|Apple Pay ¹|
|Google Pay ¹|
|Migros Bank E-Pay|
¹ Token creation only supported via Redirect and Lightbox. The Mobile SDKs support the creation of a pseudo alias (
savedPaymentMethod) to facilitate recurring customer-initiated transactions. However, this pseudo alias cannot be used for charging merchant-initiated transactions.
² For CembraPay 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 CembraPay which information will be required for your contract. No additional parameters are required in your requests to debit a CembraPay alias. For payments with a CembraPay alias you may send optional parameters within
customData located in the object
Updated 8 days ago