GETGet Recipients

Retrieve the list of saved beneficiaries for a DMT sender.

GET/customer/payment/dmt-fino/sender/{customer_id}/recipients

Returns all beneficiaries (recipients) previously registered under the sender's DMT-Fino account. Use this before initiating a transfer — if the desired beneficiary already exists you can use their recipient_id directly to send money, skipping Add Recipient.

Tip

This endpoint is one step in a complete workflow:

DMT (Fino) — Send Money — Full Fino DMT money-transfer flow: look up the sender, onboard and biometric-eKYC them if new, pick or add the recipient, then send an OTP-verified transfer.

Request

Path parameters

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

customer_idstringRequired

Sender's 10-digit mobile number.

example: 9123456789

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

Response types

response_type_id	Meaning	Next step
`22`	No recipients — add one before transacting	Add Recipient
`23`	Recipients found — proceed to Send Transaction OTP	Send Transaction OTP

Responses

23Recipients found — proceed to Send Transaction OTPNext:Send Transaction OTP

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.
- pan_requirednumber
  PAN requirement flag for the sender.
- remaining_limit_before_pan_requirednumber
  Amount the sender can still transfer before PAN becomes mandatory (INR).
- recipient_listarray
  Registered beneficiaries for this sender.
  - recipient_idnumber
    Identifier used in the Send Transaction OTP and Execute Transaction APIs.
  - beneficiary_idnumber
    Beneficiary identifier (mirrors recipient_id).
  - bank_recipient_idnumber
    Bank-side recipient identifier.
  - recipient_namestring
    Beneficiary name.
  - recipient_mobilestring
    Beneficiary mobile number.
  - bankstring
    Beneficiary bank name.
  - ifscstring
    Beneficiary bank IFSC code.
  - accountstring
    Beneficiary bank account number.
  - account_typestring
    Type of the beneficiary account.
  - ifsc_statusnumber
    Whether the IFSC is valid/active (1 = valid).
  - is_verifiednumber
    Whether the account has been penny-drop verified (1 = verified).
  - is_otp_requiredstring
    Whether an OTP is required to transact to this recipient.
  - pipesobject
    Available settlement pipes for this recipient, keyed by pipe id.

Next steps

NextPOSTAdd RecipientRegister a new beneficiary under a sender's DMT-Fino account.