Get Transaction by Reference
Bill Payment
Get Transaction by Reference
Look a transaction up by the ref you supplied
GET
Get Transaction by Reference
Overview
Finds a transaction by theref you sent when you started the discovery. It returns exactly the same object as Get Transaction by ID.
This is the recovery path. When a response is lost to a timeout, a crash or a redeploy, look the ref up — never resend the write.
A
ref is unique per partner, not globally. If you reuse the same ref string for two different partners, pass partner as well so the lookup is unambiguous.Query Parameters
string
required
The reference you supplied when you created the discovery. Maximum 100 characters.
string
Optional. One of
ADE, SONELGAZ, SEAAL, AADL, Algérie Télécom. Narrows the lookup to that biller.Response
Identical to Get Transaction by ID — the full transaction object, wrapped in the standard envelope. See that page for the field-by-field reference and for which fields appear in which status.boolean
required
true when a transaction was found.object
required
The transaction object. Full field reference →
object
required
string
required
Correlation identifier, also sent as the
X-Request-Id response header.Examples
Success Response
Error Responses
400 — Validation error
400 — Validation error
ref was missing, too long, or partner was not a known value.ref as a query parameter, URL-encoded, at most 100 characters.401 — Missing or invalid access token
401 — Missing or invalid access token
404 — Transaction not found
404 — Transaction not found
No transaction with that What to do: after a failed write, a
ref belongs to your account in this environment.404 here is the proof that the request never landed — it is safe to send it again with the same ref. Check too that you are using the key for the environment the transaction was created in.Recovering from a lost response
The pattern is the same for a discovery and for a payment: if the write failed in a way you cannot explain, ask what theref resolved to before you send anything again.
Best Practices
Look up, do not resend
Every timeout and every
DUPLICATED_REF is answered here, not by a second write.Pass the partner
It costs nothing and removes any ambiguity when the same
ref string exists for two billers.Store the ref with your order
A
ref you cannot reconstruct is a transaction you cannot recover.Poll by ID once you have it
Use this endpoint to recover, then poll by
transactionId — one fewer parameter to get wrong.Related Endpoints
Get Transaction by ID
The full transaction object
List Transactions
Filter and paginate history
Discover Bills
Where a
ref is createdStatus Polling
A production-grade poller

