Unknown macro: {style}

.page-metadata

Unknown macro: {display}

Developer Reference
Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Overview

The auto-debit functionality or future payment takes advantage of token-based approach to obtain one-time authorization and user consents 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 follow:

  • Merchant requests for user authorization code or OTP
  • Zeta sends OTP to user that he/she shares with merchants
  • Merchant verifies the OTP and obtain 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

Before You Begin

Take care of the following:

Integration Flow

  1. Account Creation: Create a developer account with Auto-Debit whitelisted.

    We can also provide the same permission to an existing account as well.

  2. 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.

    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.

  3. 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.
    1. 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.
    2. Once the transaction is done, you can get the details of the transaction from Get Transaction details API.
  4. Refund Transaction: The merchant can issue a refund to the user using the Refund a transaction API

On this page:

  • No labels