GETGet Sender Information

Fetch a DigiKhata wallet sender's profile and onboarding/OTP state by mobile number.

GET/customer/payment/ppi-digikhata/sender/{customer_id}

First step of the PPI DigiKhata flow. For an enrolled sender the response returns an otp_ref_id and asks you to validate the OTP (call Verify Sender OTP). If the customer is not enrolled (response_type_id 308), proceed to Onboard Sender.

Request

Path parameters

Field	Type	Required	Description
`customer_id`	string	required	Sender's 10-digit mobile number.e.g. 8617567988

customer_idstringRequired

Sender's 10-digit mobile number.

example: 8617567988

Query parameters

Field	Type	Required	Description
`initiator_id`	string	required	Registered mobile number of the API user (see Platform Credentials).e.g. 9962981729
`client_ref_id`	string	optional	Unique reference ID per API call, generated by your system (max 20 characters).e.g. 2026010100123456789

initiator_idstringRequired

Registered mobile number of the API user (see Platform Credentials).

example: 9962981729

client_ref_idstringoptional

Unique reference ID per API call, generated by your system (max 20 characters).

example: 2026010100123456789

These headers authenticate and sign every request. See How Auth Works for details.

Field	Type	Required	Description
`developer_key`	string	required	Static API key issued to your account after KYC.
`secret-key`	string	required	Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).
`secret-key-timestamp`	string	required	Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.
`content-type`	string	required	application/jsone.g. application/json

developer_keystringRequired

Static API key issued to your account after KYC.

secret-keystringRequired

Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).

secret-key-timestampstringRequired

Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.

content-typestringRequired

application/json

example: application/json

Responses

statusnumber
Primary success indicator (0 = success).
messagestring
Human-readable response / error message.
response_status_idnumber
Granular status id; see the shared error-codes table.
response_type_idnumber
A unique id for every possible response shape (success or error) — useful for client logic branching and analytics.
dataobject
API-specific response payload.
- intent_idnumber
  Intent flag for the next onboarding/validation step (19 = sender onboarding).
- kyc_request_idstring
  KYC request reference, when a KYC step is pending.
- otp_ref_idstring
  OTP session reference — pass to Verify Sender OTP.

Next steps

NextPOSTOnboard SenderRegister a new customer as a PPI DigiKhata wallet sender using basic KYC details.

import { EpsClient } from "@ekoindia/eps-sdk";

const client = new EpsClient({

developerKey: process.env.EPS_DEVELOPER_KEY,

accessKey: process.env.EPS_ACCESS_KEY,

initiatorId: "9962981729",

environment: "sandbox",

});

const result = await client.call("ppi-digikhata-get-sender", {

"customer_id": "8617567988"

});

console.log(result);

{

"response_status_id": 1,

"data": {

"intent_id": 19,

"kyc_request_id": "",

"otp_ref_id": "IXrygqm0vTNbN35Lp5AfcbP69ifPhQ1Ee3u74AHY5fA9aMp2d94Yii3g+9fOBmbMsVTuaEQpDOEateP4tSTkQw=="

"response_type_id": 2129,

"message": "Validate the OTP",

"status": 2129

}

Request

Path parameters

Query parameters

Responses

Next steps

Related