Fintech APIs & Platform for KYC, Verification & Transactions in India | Eko Platform Services
Eko Platform Services Logo

POSTAdd Recipient

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

POST/customer/payment/dmt-fino/sender/{customer_id}/recipient1

Adds a new beneficiary to the sender's saved recipients list. Provide the recipient's full name, bank account number, IFSC code, and mobile number. The bank_id identifies the destination bank (fetch from the bank list if needed). On success a recipient_id is returned; use it in Send OTP and Initiate Transfer. The system may validate the account via penny-drop before activating the recipient.

Path parameters

customer_idstringRequired

Sender's 10-digit mobile number.

example: 9123456789

Body parameters

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.

example: REQ-20260101-001

recipient_namestringRequired

Full name of the beneficiary as it appears on their bank account.

example: Sunil Sharma

accountstringRequired

Beneficiary's bank account number.

example: 012345678901

ifscstringRequired

IFSC code of the beneficiary's bank branch.

example: SBIN0001234

bank_idnumberRequired

Unique bank identifier from Eko's bank list API.

example: 20

recipient_mobilestringRequired

10-digit mobile number of the recipient.

example: 9988776655

recipient_typestringRequired

Recipient type. Fixed value: "3" for DMT-Fino bank account recipients.

example: 3

Headers

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.

    • recipient_idnumber

      Unique identifier assigned to the newly added recipient. Required for Send OTP and Initiate Transfer.

    • recipient_namestring

      Name of the recipient as registered.

    • accountstring

      Bank account number of the recipient.

    • ifscstring

      IFSC code of the recipient's bank branch.

    • is_verifiedboolean

      Whether the account passed penny-drop verification.

Next steps

Related