Enkash Developer Portal
Home
Home
Login
  1. Prepaid Cards
  • Explore Our Product Suite
  • Payment Gateway
    • Set Up Payment Gateway
    • Payment Options
    • Easy API Setup
    • APIs - Payment Gateway
  • Payouts
    • Set Up Payouts
    • APIs - Payout
  • Prepaid Cards
    • Key Capabilities
    • Set Up Prepaid Cards
    • KYC Status Handling Guide
    • T&C Acceptance Flow
    • APIs - Prepaid Card
  • Wallet
    • APIs - Wallet
  • Bharat Connect (BBPS)
    • APIs - BBPS
  • Accounts Payable
    • APIs - Accounts Payable
  • Account Receivable
    • Accounts Receivable Overview
    • APIs - Account Receivable
  • Expense Management
    • About Authorization
    • APIs - Expense
    • Partner Integeation
  • Rewards & Incentives
    • About Rewards
    • Getting Started
    • Encryption & Decryption Guide
    • Reward Allocation
    • Incentive Allocation
    • APIs - Reward
  • Petty Cash
    • Request Encryption Using AES
    • API - Petty Cash
  • Verification Suite
    • Verification Suite Overview
    • APIs - Verification Suite
Home
Home
Login
  1. Prepaid Cards

T&C Acceptance Flow

This document defines the T&C (Terms & Conditions) acceptance redirect flow required for wallet activation, in alignment with RBI co‑branding guidelines. It is intended for backend and frontend developers integrating the wallet activation and T&C gating flow in both UAT and Production environments.

Purpose#

Wallet activation and usage are gated behind explicit user acceptance of the latest wallet T&C and, where applicable, minimum KYC.
A wallet may exist but must not be treated as active or usable until:
The user has accepted the latest T&C, and
Minimum KYC requirement is satisfied.
The system of record for T&C status is the wallet details API, via the field latestTncVersionAccepted.
This specification defines:
How to detect that T&C acceptance is pending.
How to construct and send the T&C redirect.
How to handle the post‑T&C redirect back to your application.
Security, validation, and test considerations.

Preconditions#

Before implementing this flow, ensure, you have access to the Wallet Details API that returns:
latestTncVersionAccepted (boolean)
walletId
You can generate a current access token for the wallet/user context.
You can define and control a return URL (in your application) where the user will be redirected after:
T&C acceptance, or
Minimum KYC completion.

Trigger Condition#

You must initiate the T&C redirect flow when the Wallet Details API returns:
{
  "walletId": "<walletId>",
  "latestTncVersionAccepted": false,
  ...
}

Trigger rule:#

If latestTncVersionAccepted === false:
The user must be redirected to the T&C URL.
If latestTncVersionAccepted === true:
Proceed with the normal wallet flow; no T&C redirect is required.

This rule must be evaluated:#

Whenever the user opens or re‑opens the wallet.
The user previously navigated away without completing T&C acceptance, and later returns to the wallet screen.

Environment‑Specific URLs#

Use the following base URLs for the T&C acceptance flow.
EnvironmentURL
Productionhttps://home.enkash.com/partner/tnc
UAT

URL Construction (Production Example)#

Step 1: Build the payload JSON
{
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
  "walletId": "WALLET_12345",
  "returnUrl": "https://your-app.com/wallet/home"
}
Step 2: Base64 encode the JSON
eyJ0b2tlbiI6ImV5SmhiR2NpT2lK...
Step 3: Construct the Production URL
https://home.enkash.in/partner/tnc?WID={cardId}==&at={token}&returnUrl={returnUrl}
Example (truncated for illustration):
https://invoice-uat.enkash.in/partner/tnc?WID={cardId}==&at={token}&returnUrl={returnUrl}
Apply the same construction logic for the UAT base URL.
Query parameters and payload format must be consistent across UAT and Production.

Redirect Flow#

When latestTncVersionAccepted = false:
1
Detect Pending T&C:
Call Wallet Details API.
Check latestTncVersionAccepted.
2
T&C Redirect URL
Choose the correct base URL (UAT or Production).
Build a Base64‑encoded JSON payload containing:
Current access token
Wallet ID
Return URL
3
Partner App
Redirect the user to the T&C URL provided by EnKash.
4
User Completes
T&C acceptance, and
Minimum KYC verification within Enkash’s platform
5
Redirect
EnKash redirects the user back to Partner's returnUrl.
6
Recommended
Call Wallet Details API again to confirm:
latestTncVersionAccepted === true
Before enabling wallet usage UI/features.
Modified at 2025-12-26 06:45:10
Previous
KYC Status Handling Guide
Next
APIs - Prepaid Card
Built with