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

GETTransaction Inquiry

Get the status of any transaction by Eko TID or your client_ref_id.

GET/tools/reference/transaction/{transaction-reference}

Get the current status of a transaction using either Eko's TID or your own client_ref_id. This is a generic inquiry endpoint — it works for all Eko financial transaction types (fund transfer, BBPS, AePS settlement, NEFT, and more).

The transaction reference goes in the URL path. Pass an Eko TID as-is; to look up by your client_ref_id, prefix it with client_ref_id::

  • By TID — /tools/reference/transaction/<TID>
  • By client_ref_id — /tools/reference/transaction/client_ref_id:<your client_ref_id>
Note

Examples

To check the status of a transaction using TID 2886601782, call /tools/reference/transaction/2886601782.

If you never received Eko's TID (say, due to a network timeout) but sent your own unique reference 567890, look it up with /tools/reference/transaction/client_ref_id:567890.

Warning

Transaction timeout

A transaction can time out for many reasons — a slow partner-bank response, or network connectivity causing a delayed or missing response.

In such cases the transaction must not be treated as declined or failed. Inquire about its real status using this API with your own client_ref_id, instead of retrying the payment.

tx_status values

tx_statusDescription
0Success
1Fail
2Response Awaited / Initiated (in case of NEFT)
3Refund Pending
4Refunded
5Hold (Transaction Inquiry required)

Request

Path parameters

transaction-referencestringRequired

Eko TID or your `client_ref_id` that identifies the transaction. Pass a TID as-is; to look up by `client_ref_id`, prefix it — e.g. `client_ref_id:567890`.

example: 12971397

Query 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 (max 20 characters).

example: 2026010100123456789

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.

    • tx_statusstring

      Transaction status (0 Success, 1 Fail, 2 Awaited, 3 Refund Pending, 4 Refunded, 5 Hold).

    • txstatus_descstring

      Human-readable transaction status.

    • tidstring

      Eko transaction ID.

    • client_ref_idstring

      Your reference id for the transaction.

    • amountstring

      Transaction amount (INR).

    • bank_ref_numstring

      Bank/UTR reference number.

    • recipient_namestring

      Recipient's name.

    • timestampstring

      Transaction timestamp.

Next steps

NextPOSTGet Refund OTPRequest the refund OTP for a failed transaction (sent to the customer's mobile).

Related