T&C Acceptance Flow

This document defines the T&C (Terms & Conditions) acceptance redirect flow required for card activation, in alignment with RBI co‑branding guidelines. It is intended for backend and frontend developers integrating the card 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 card 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 card 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 card Details API that returns:

latestTncVersionAccepted (boolean)

cardId

You can generate a current access token for the card/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 card Details API returns:

{
  "cardId": "<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.

Environment	URL
Production	`https://home.enkash.in/partner/tnc?WID={cardId}==&at={token}&returnUrl={returnUrl}`
UAT	`https://invoice-uat.enkash.in/partner/tnc?WID={cardId}==&at={token}&returnUrl={returnUrl}`

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:

Detect Pending T&C:

Call Card Details API.

Check latestTncVersionAccepted.

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

Partner App

Redirect the user to the T&C URL provided by EnKash.

User Completes

T&C acceptance, and

Minimum KYC verification within Enkash’s platform

Redirect

EnKash redirects the user back to Partner's returnUrl.

Recommended

Call Card Details API again to confirm:
latestTncVersionAccepted === true

Before enabling Card usage UI/features.

Purpose#

Preconditions#

Trigger Condition#

Trigger rule:#

This rule must be evaluated:#

Environment‑Specific URLs#

URL Construction (Production Example)#

Redirect Flow#

Purpose

Preconditions

Trigger Condition

Trigger rule:

This rule must be evaluated:

Environment‑Specific URLs

URL Construction (Production Example)

Redirect Flow