POSTOnboard Sender

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

Registers a new DigiKhata sender. Provide name, date of birth, and residence address. For a new sender an OTP is dispatched and an otp_ref_id returned — call Verify Sender OTP next. If the wallet already exists the response confirms Wallet opened successfully.

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

Body 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
`name`	string	required	Name of the sender as per ID.e.g. Yashwant Basnett
`dob`	string	required	Date of birth of the sender in YYYY-MM-DD format.e.g. 1990-05-15
`residence_address`	array	required	Sender's address as an array of strings.e.g. 123 MG Road,Bangalore,Karnataka,560001

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

namestringRequired

Name of the sender as per ID.

example: Yashwant Basnett

dobstringRequired

Date of birth of the sender in YYYY-MM-DD format.

example: 1990-05-15

residence_addressarrayRequired

Sender's address as an array of strings.

example: 123 MG Road,Bangalore,Karnataka,560001

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

NextPOSTGenerate Sender Verification OTPSend a verification OTP to a DigiKhata sender's registered mobile number.

Request

Path parameters

Body parameters

Responses

Next steps

Related