Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Overview
The auto-debit functionality or future payment takes advantage of token-based approach to obtain one-time authorization and user consent for future payments from Zeta users. The user token works conceptually similar to OAuth access tokens. This functionality allows you to save user payment details (including the user token) once and use the stored details to charge Zeta user for any future transactions.
A typical auto-debit payment flow would be as follows:
- Merchant requests for user authorization code or OTP.
- Zeta sends OTP to user that he/she shares with merchants.
- Merchant verifies the OTP and obtains the user token from Zeta.
- Merchant generates a payment request to Zeta using the user token.
- Zeta authorizes the payment and returns payment status back to merchant application.
Note |
---|
|
Before You Begin
Take care of the following:
- Create a new Zeta merchant account.
- Provision a Zeta developer account that enables you to securely communicate with Zeta payment server and invoke API requests.
Integration Flow
Create Zeta Developer Account: Create a developer account with Auto-Debit whitelisted.
Note We can provide the same permission to an existing account as well.
Link Zeta Account: A first time user has to open the Developer/Merchant app and select the option to authenticate with Zeta. Please follow the save source flow to enable the linking of zeta details of the user to your account.
Note While saving a source for the purpose of Auto-debit flow please request for the following permissions - "SAVE_FOR_FUTURE", "GET_BALANCE", "AUTO_DEBIT". Refer to the Save a source API in the API reference for more details.
- Create Transaction: The merchant can then make any transaction for the user (upto a configurable amount limit preset during on-boarding) without a 2nd factor authentication.
- As per the designed checkout flow of the merchant, whenever the merchant needs to collect payment from user, merchant will call Charge With Auth API (v2.0) using the
sourceId
received in the Save Source flow. - Once the transaction is done, you can get the details of the transaction from Get Transaction details API.
- As per the designed checkout flow of the merchant, whenever the merchant needs to collect payment from user, merchant will call Charge With Auth API (v2.0) using the
- Refund Transaction: The merchant can issue a refund to the user using the Refund a transaction API
Panel | ||||||
---|---|---|---|---|---|---|
|