Eko Platform Services Logo

    POSTAdd Recipient

    Register a new beneficiary under a PPI Levin sender's account.

    POST/customer/payment/ppi-levin/sender/{customer_id}/recipient

    Adds a beneficiary (bank account) to a PPI Levin sender. On success a recipient_id is returned — use it to send transaction OTP and initiate the transfer. Maximum 5 recipients per day.

    Path parameters

    customer_idstringRequired

    Sender's 10-digit mobile number.

    example: 9444444444

    Body parameters

    initiator_idstringRequired

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

    example: 9962981729

    user_codestringRequired

    User code of the retailer/agent the service is run for.

    example: 20810200

    client_ref_idstringoptional

    Unique reference id per API call, generated by your system.

    example: REQ-20260101-001

    bank_idintegerRequired

    Unique ID assigned to the beneficiary's bank.

    example: 12

    recipient_namestringRequired

    Full name of the recipient.

    example: Aditya

    recipient_mobilestringRequired

    Recipient's 10-digit mobile number.

    example: 9775597777

    recipient_typestringRequired

    Recipient type. Value will be 3.

    example: 3

    accountstringRequired

    Recipient's bank account number.

    example: 1234567890657

    ifscstringRequired

    IFSC code of the recipient's bank branch.

    example: KKBK0000878

    typestringoptional

    Recipient identifier type. Defaults to `ifsc`.

    example: ifsc

    account_typestringoptional

    Account type. Defaults to 1.

    example: 1

    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 recipient identifier — use to transact.

      • recipient_mobilestring

        Recipient's mobile number (echoed back).

      • customer_idstring

        Sender's mobile number (echoed back).