Prefixes
RadiumOne identifiers are prefixed by type, so you can tell what an ID is from its shape alone.| Prefix | Identifier | Where it’s used |
|---|---|---|
r1sk_test_… / r1sk_prod_… | Secret key | Server-only Payments API and Checkout API requests |
r1pk_test_… / r1pk_prod_… / r1pk_mock_… | Publishable key | Browser-safe: Elements, hosted-checkout session verification |
r1rt_… | Refresh token | Server-only; exchanges for a new access token |
rsec_… | Redirect secret | Signs and verifies hosted-checkout redirect callbacks |
whsec_… | Webhook secret | Verifies webhook signatures |
chk_ + 32 lowercase hex chars | Checkout session ID | Hosted-checkout session, returned from session create and used in the payment URL |
evt_… | Webhook event ID | Envelope id on every webhook delivery, used for dedup |
Terms
| Term | Meaning |
|---|---|
| Outlet | A store or location within your merchant account. A key can be bound to a specific outlet; omitting outlet_id on a request uses the key’s bound outlet. |
| Channel | How the payment was initiated: CARD_PRESENT, ECOMMERCE, MOTO, PAYMENT_LINK, IN_APP, or RECURRING. |
| Scope | A permission on a secret or publishable key (for example, payment-gateway:transaction-create, transaction-refund-unreferenced). See Sandbox and API keys. |
| Idempotency key | A caller-supplied value (request_id or operation_id) that makes a create or follow-up request safely retryable. See Prevent duplicate payments. |
| Replay | Sending the same idempotency key and body a second time. RadiumOne returns the original transaction instead of creating a new one — whatever its status, including PENDING or DECLINED. |
request_id | A caller-supplied idempotency key (8–64 characters) on create-type requests (purchase, authorize, standalone refund, balance inquiry). Reusing the same request_id with the same body replays the original result; a different body under the same key fails with 409 idempotency-body-mismatch. |
operation_id | The idempotency key used to reference an existing transaction for capture, void, or referenced refund. A replay with the same operation type returns the original result without comparing the body — a changed amount is silently ignored, not rejected. Reusing it for a different operation type fails with 409 duplicate-operation. |
order_reference | Your own reference for a checkout session. RadiumOne deduplicates on it only for the session’s TTL (5–60 minutes; default 10 minutes in production, 25 in sandbox) — after it expires, the same value creates a new session. Not a durable order ID: store the resulting transaction_id in your own order record instead. |
| Bind / tokenization | The process by which Elements exchanges raw card details for a card.token, without the card number ever reaching your server. |
| Card token | The opaque, digit-only reference returned by tokenization. Not a PAN — see Security and PCI scope. |
| Settlement batch | The window during which a terminal’s captured transactions can still be voided; once it closes, only a refund can reverse a transaction. See Void or refund, never both. |
| Capture window | The number of days after authorization within which a capture is still allowed. |
3DS arm (three_ds) | One of three mutually exclusive request shapes for supplying 3D Secure evidence to a charge: a ref from RadiumOne’s own 3DS flow, {mode: "non_payer_auth"}, or external-provider evidence (cavv, eci, ds_transaction_id, version). |
| ECI (electronic commerce indicator) | The scheme-specific code returned by a 3DS authentication that determines whether liability shifts to the card issuer. See Use your own 3DS provider. |
| CAVV / AAV | The cryptographic authentication value a 3DS provider returns as evidence that a challenge was completed. |
| MPI (merchant plug-in) | A merchant’s own 3D Secure authentication component, as opposed to RadiumOne’s built-in 3DS. See Use your own 3DS provider. |
| URN | The structured error identifier RadiumOne returns in error responses, for example urn:radiumone:auth:insufficient-scope. See Problem format and retries. |
| Loyalty redemption / net payable amount | The portion of an order paid with loyalty points versus card. amount on a purchase is always the gross order total; net_payable_amount (Beta) pins the card-payable remainder that 3DS authenticates. See UOB Rewards. |
| Discovery | The mechanism by which a checkout surface advertises which payment methods and loyalty programmes are potentially available — advisory only, not a guarantee the method will complete. |
| Enablement | Support-provisioned account configuration required before certain features work in production — see Request enablement. |
Next steps
Sandbox and API keys
Key types, prefixes, and scopes in full.
Problem format and retries
URN error shapes and HTTP codes.