Important Note: Card Tokenization is currently available via API integration only. See the Recurring Payments Developer Documentation for the required endpoints and payloads.

Card Tokenization allows you to charge a customer's card automatically on a recurring basis. Once a customer completes their first payment, Monnify generates a secure token linked to that card. Every subsequent charge uses that token.

This is the right fit for subscription platforms, membership services, or any business that needs to bill customers on a schedule without interrupting their experience.

How Card Tokenization Works

The process runs in four steps:

1. Charge the Card at First Transaction: The customer makes their first payment through your web or mobile application and enters their card details as normal. This initial transaction confirms the card is valid and active.
2. Retrieve the Card Token: Once the first transaction is successful, query the Get Transaction Status API to retrieve the cardToken from the cardDetails object in the response. This token is your key to all future charges on that card.
3. Store the Token and Email: Save the cardToken alongside the email address used for that transaction. This pairing is crucial as Monnify requires both the token and the original email to process any subsequent automated charge.
4. Charge the Card Token For every recurring payment, call the Charge Card Token API with the saved token and matching email. The charge goes through without any input from the customer.

How to Activate Card Tokenization

To get Card Tokenization enabled on your account, send an email from the address linked to your Monnify account:

1. To: [email protected]
2. Subject: Recurring Payments using Card Tokenization: [Your Business Name]
3. Body: Include your Monnify Business Code and a brief description of the services you intend to offer.

Tip: Your Business Code is displayed at the top of your dashboard menu.

Our team typically reviews and activates requests within 24 hours. You'll receive a confirmation in the same email thread once the feature is live.

A Few Things to Note

1. Card Tokenization is currently supported on Mastercard and Verve cards.
2. Every charge against a card token must include the same email used during the original transaction. A mismatch will cause the request to fail.
3. The token is reusable. Once saved, you can charge the same token as many times as needed, no repeat authorizations required from the customer.

Ready to Set This Up?

Since Card Tokenization is configured entirely via the API. See the Recurring Payments Developer Documentation to get started