Skip to main content
No terminal that could route your request is currently able to perform the operation you asked for — distinct from a card decline, which always requires a live terminal to have been reached in the first place.
TL;DR — resolution: "operator" means a configuration change is needed, not a retry. Contact support with the request_id. The exceptions are resolution: "transient" (device-settling, device-busy, acquirer-circuit-open, all retry_allowed: true): wait, then resend the same request with the same key.

When this happens

  • Every candidate terminal has the requested operation toggled off — 409 urn:radiumone:payment-gateway:routing:operation-disabled (resolution: operator).
  • No usable terminal could be routed for the channel/acquirer/currency at all — 409 urn:radiumone:payment-gateway:routing:no-device-available (resolution: operator).
  • Every candidate terminal exists but isn’t ACTIVE — 409 urn:radiumone:payment-gateway:routing:terminal-inactive (resolution: operator).
  • The terminal that processed the original transaction has the operation toggled off (capture, void, or refund) — also 409 urn:radiumone:payment-gateway:routing:operation-disabled.
  • The terminal’s settlement batch is closing right now — 409 urn:radiumone:payment-gateway:settlement:device-settling (resolution: transient, retry_allowed: true). It clears on its own.
  • On a purchase, authorize, or standalone refund, a terminal that could take the request is busy with another operation, and no other terminal could take it — 409 urn:radiumone:payment-gateway:routing:device-busy (resolution: transient, retry_allowed: true). It clears as soon as the other operation finishes — it’s not a configuration problem, unlike operation-disabled.
  • On a purchase, authorize, standalone refund, or 3D Secure authentication, every acquirer that could take the request is briefly out of service while it recovers — 503 urn:radiumone:payment-gateway:routing:acquirer-circuit-open (resolution: transient, retry_allowed: true). No transaction is created. It clears on its own; it’s not a configuration problem, unlike 422 routing:no-acquirer-available.
  • The terminal’s last settlement batch was rejected, so it takes no new operations until an operator fixes it — 409 urn:radiumone:payment-gateway:settlement:device-batch-rejected (resolution: operator).
  • The outlet itself is disabled and takes no new payments — 403 urn:radiumone:payment-gateway:merchant:outlet-disabled.
  • A follow-up operation (capture/void/refund) inherits its acquirer channel from the original transaction, and that channel doesn’t have the operation enabled — 422 urn:radiumone:payment-gateway:routing:capability-not-supported. This is the error you’ll see if you attempt a refund before requesting enablement, since refunds are disabled by default.

What you see

The settling and blocked-batch errors come from purchase, authorize, capture, void, standalone refunds, and UOB Rewards balance inquiries — the operations that need the terminal’s current batch. A refund of an earlier transaction and a status inquiry aren’t blocked by a settling terminal (a refund while the batch is still open gets tx:refund-on-open-batch instead). Nothing was sent to the card network, so no money moved.

What to do

1

Retry only a transient refusal

If the resolution is transient (settlement:device-settling, routing:device-busy, or routing:acquirer-circuit-open), wait, then resend the same request with the same request_id/operation_id: a settling batch takes a few minutes; the others clear once the terminal is free or the acquirer has recovered. The retry can’t create a second transaction: after device-settling or device-busy it’s re-run on the same transaction, and after acquirer-circuit-open nothing was recorded, so it runs as new. Nothing else here clears on its own or with backoff — a resolution: operator conflict needs a configuration change, not a retry.
2

Contact support with the request_id

Contact support with the failing operation and the request_id from the response, so they can check enablement for your outlet/terminal.
3

Confirm enablement before you rely on an operation in production

Card is enabled by default; every other operation and payment method requires explicit enablement — see Payment methods: enablement and work through the go-live checklist before launch.

Charge or authorize a payment

Where this can surface on a create-type call.

Supported payment methods

Which operations and methods need enablement.

API errors

The full routing/capability error table.

Support

Request enablement or report a routing gap.
Last modified on September 29, 2026