Skip to main content
RadiumOne doesn’t expose a general list or search endpoint for transactions. The one merchant-facing read is the status inquiry: given a transaction id you already have, it returns the transaction as RadiumOne holds it — the same transaction object the operation that created or last changed it returned, in the same state its webhooks report. It’s read-only: it writes nothing and sends nothing to the card network.
This request requires a valid access token. See Authentication to obtain one with POST /v1/auth/token before you continue.

When to use it

  • You have a transaction id (from a create response, a replay, or a webhook) and want its current status before you decide what to do next.
  • A transaction is PENDING or REVERSAL_PENDING and the webhook is late — poll the status inquiry every 60 seconds until it settles.
  • A create-type call timed out and you’ve already replayed it with the same request_id to recover the id — see Handle timeouts and unknown outcomes.
If you don’t have a transaction id yet, status inquiry can’t help — replay the original purchase, authorize, or refund with the same request_id first, or wait for the confirming webhook.

Steps

1

Query the transaction's status

API reference.
2

Branch on data.status

data.status is the transaction’s lifecycle status — see Poll until the outcome settles. Never derive the outcome from data.response_code alone; that’s the verbatim acquirer code, for display and reconciliation only.

Poll until the outcome settles

How often, and for how long:
  • Poll every 60 seconds while the status is PENDING or REVERSAL_PENDING. RadiumOne resolves unsettled transactions in the background on a regular cycle, so polling faster doesn’t settle them sooner, and the webhook usually arrives on its own.
  • Stop after 60 minutes and contact support if it still isn’t final. Count the 60 minutes from when your server sent the request whose response you didn’t get (the purchase, authorize, capture, void or refund). Use your own send time: without a response, you have no RadiumOne timestamp to read. RadiumOne’s own recovery runs on the same clock, so any reversal completes within this window. For a hosted checkout session that expired mid-payment, the session’s expires_at is an equally safe starting point, because the purchase can only be sent before it.
  • On INCONSISTENT, stop straight away and contact support.
Any other documented status is final; treat an unrecognised status as not final and keep it for support.

Response fields

The response is the same transaction object that purchase, authorize, capture, void, and refunds return (see the API reference). The fields you’ll use most:

Relation to webhooks and replay

Status inquiry, webhooks, and replaying the same idempotency key are the three ways to learn a transaction’s outcome — reach for whichever fits the moment:
  • Replay a purchase, authorize, or refund with the same request_id is the only way to recover a transaction id you never received — for example, a client-side timeout before the first response arrived. The replay is a lookup: it returns the stored result, whatever it is, and never sends the payment again (a request refused before it reached the card network is run again — it was never sent). A capture or void is replayed the same way with its operation_id.
  • Status inquiry is the safest tool once you already have an id. It’s read-only, so calling it repeatedly is always safe, and it needs no idempotency key of its own. It reports the same state as the webhooks.
  • Webhooks push the eventual outcome to your server without polling. Prefer them for routine updates, and use status inquiry when a webhook is late or you need an answer now.
See Handle timeouts and unknown outcomes for the full recovery walkthrough, and Webhook event types for the events that carry the same outcome asynchronously.

Errors

The status inquiry reads RadiumOne’s own record and never calls the acquirer, so it has a short error list: All three are safe to retry because the status inquiry only reads. It never returns a 409 or 422: a terminal that’s mid-settlement, or has an operation switched off, never blocks a status inquiry.

Test your integration

See Test your integration for simulated timeout and status-inquiry scenarios.

Go-live notes

  • Handle PENDING, REVERSAL_PENDING, and INCONSISTENT from the status inquiry before you go live — not just the final statuses.
  • Prefer webhooks for routine updates; poll the status inquiry every 60 seconds when a webhook is late, and stop after 60 minutes — see Poll until the outcome settles.
  • Review the full go-live checklist.

Next steps

Handle timeouts and unknown outcomes

The full recovery walkthrough after a timed-out request.

Webhooks

Get transaction updates pushed to your server instead of polling.
Last modified on September 29, 2026