Skip to main content
An operation that timed out at the switch can leave a transaction in an indeterminate state. Rather than leaving that charge stuck, RadiumOne automatically reverses it once the outcome resolves. You’ll see this most often after a switch timeout.
TL;DR — REVERSAL_PENDING / REVERSED means the charge didn’t ultimately go through — treat it as not paid. Wait for the confirming webhook.

When this happens

  • A purchase, authorize, capture, void, or referenced-refund request times out with an indeterminate outcome (host_forwarded: "maybe"). RadiumOne treats it as a reversal candidate rather than leaving it unresolved — so a timeout with an unknown outcome never ends as FAILED, and a FAILED purchase means the host didn’t approve it. A capture that timed out this way reverses the capture, never the authorization: the transaction reads REVERSAL_PENDING, then returns to AUTHORIZED so you can capture it again (see Capture). A void that timed out reverses the void, not the sale: the sale reads REVERSAL_PENDING, then returns to CAPTURED (see Void). A refund that times out with an unknown outcome is armed for reversal the same way, rather than being left in a terminal FAILED state.
  • A purchase, authorization, or standalone refund reached the card network, but RadiumOne couldn’t save the answer — for example, you got 503 urn:radiumone:payment-gateway:database-unavailable. RadiumOne saves each attempt before it sends it, so it still knows about the attempt: it checks with the network, and reverses an approval it couldn’t record (REVERSAL_PENDING → REVERSED, then the *.reversed webhook) instead of leaving the card charged. A same-request_id replay returns PENDING until that’s resolved.
  • A reversal itself gets stuck after repeated attempts — 409 urn:radiumone:payment-gateway:transaction:reversal-limit-exceeded, which needs support to clear.

What you see

What to do

1

Treat it as not paid, not as an error

REVERSAL_PENDING and REVERSED both mean the charge didn’t ultimately go through (except after a timed-out capture or void: RadiumOne reverses that capture or void, not the sale, so the hold or the captured sale stands once it’s undone — and no *.reversed webhook is sent for it). Don’t fulfil the order, and don’t treat the reversal as a failure on your side — it’s RadiumOne resolving an indeterminate outcome safely.
2

Confirm the final state

Wait for the *.reversed webhook (recommended), or check its status directly. After a timed-out capture or void no webhook follows when the reversal clears, so check the status if you don’t use webhooks or need an answer now (API reference):
3

Escalate a stuck reversal

reversal-limit-exceeded means the reversal itself needs manual intervention — contact support with the transaction or reversal ID.

Payment lifecycle

Where REVERSAL_PENDING/REVERSED fit in the full state diagram.

Void a payment

Cancel a captured payment while its batch is open.

Handle timeouts and unknown outcomes

The switch-timeout case that most often leads here.

Payment operation errors

The full URN catalog for automatic-reversal errors.
Last modified on October 25, 2026