Eko Platform Services Logo

    POSTPay BBPS Bill

    Process a bill payment or recharge for any BBPS-connected biller.

    POST/customer/payment/bbps

    The core money-debit API that executes a bill payment or prepaid recharge on the BBPS network. For operators where billFetchResponse = 1, the billfetchresponse token returned by the Fetch Bill API must be included.

    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

    utility_acc_nostringRequired

    Customer's account or consumer number with the biller.

    example: 1234567890

    confirmation_mobile_nostringRequired

    Customer's mobile number for payment confirmation.

    example: 9999988888

    sender_namestringRequired

    Customer's full name.

    example: Ramesh Kumar

    operator_idstringRequired

    Biller identifier from the Get Operators response.

    example: 83

    amountstringRequired

    Payment amount in rupees (e.g. '1350' for ₹1,350).

    example: 1350

    source_ipstringRequired

    IP address of the agent or retailer making this request.

    example: 192.168.1.1

    latlongstringRequired

    Agent's GPS coordinates as `latitude,longitude`. Mandatory for agent activation compliance.

    example: 28.6139,77.2090

    billfetchresponsestringoptional

    The opaque token returned by the Fetch Bill API. Required when the operator's `billFetchResponse = 1`.

    example: eyJhbGciOiJSUzI1NiJ9...

    dobstringoptional

    Date of birth of the policy holder in DD/MM/YYYY format. Required for LIC policy payments.

    example: 15/08/1985

    postalcodenumberoptional

    6-digit PIN code of the customer. Required for MSEB electricity payments.

    example: 400001

    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.

    • tx_statusstring

      Transaction state: 0=Success, 1=Fail, 2=Awaited, 3=Refund Pending, 4=Refunded, 5=On Hold.

    • txstatus_descstring

      Human-readable transaction status.

    • dataobject

      API-specific response payload.

      • tidstring

        Eko's unique transaction identifier. Use this for status enquiry and dispute resolution.

      • operator_ref_idstring

        Reference number issued by the biller / BBPS network confirming receipt of payment.

      • amountstring

        Amount debited for this transaction.

      • balancestring

        Remaining wallet balance of the agent after this transaction.

      • utility_acc_nostring

        Consumer/account number against which the payment was made.

      • client_ref_idstring

        Your reference ID echoed back.