Skip to main content
Every amount you send to or receive from the Payments API is an integer count of the currency’s minor units. This page shows you how to find which currencies your outlet accepts, how to state amounts, and how to read a currency’s minor units from RadiumOne instead of keeping your own table.
Only currencies with 2 minor units are supported today. A valid ISO 4217 currency with 0 or 3 minor units (for example JPY or KWD) is refused with 422 urn:radiumone:payment-gateway:currency:minor-units-not-supported. Don’t hard-code which currencies or scales are accepted — read them from the API as described below, so your integration keeps working when support widens.

How to use currencies

1

List the currencies your outlet accepts

At setup, or when you build a checkout, call GET /v1/merchant/currencies with your access token. Pass outlet_id to ask about a specific outlet; omit it to use your default outlet. Offer your shoppers only the currencies in this list.
2

Send every amount as an integer in minor units

SGD has 2 minor units, so SGD 10.50 is 1050. Never send a decimal. See Request shapes for where the amount goes on each call.
3

Format amounts for display from the response

Transaction, session, balance inquiry and settlement responses carry currency_minor_units beside currency (payment method discovery responses don’t). Divide the amount by 10 to the power of currency_minor_units to get the major-unit value: 1050 with currency_minor_units: 2 displays as 10.50.
4

Validate codes against the public list

To validate a currency code or build a currency picker, call GET /v1/currencies. It needs no access token and lists every currency RadiumOne supports. It doesn’t tell you which currencies your outlet accepts — use GET /v1/merchant/currencies for that.
5

Cache both lists with their ETag

Store the ETag from each response and send it back in an If-None-Match header. An unchanged list answers 304 Not Modified with no body. See Cache the currency lists.
6

Treat currency refusals as permanent

422 currency:unknown-currency and 422 currency:minor-units-not-supported both carry retry_allowed: false. Fix the currency; don’t retry the same request. See What is refused.

Request shapes

Response fields

  • Transactions, sessions, and balance inquiries return integer amounts in minor units with currency and currency_minor_units.
  • Session create also returns allowed_currency_details: one {code, minor_units} entry per currency in allowed_currencies, in the same order. Use it to format and parse amounts.
  • Settlement batches carry two currencies, so they return presented_currency_minor_units and settlement_currency_minor_units. See Retrieve a settlement batch.
  • UOB Rewards vouchers return redeem_value_minor, an integer in the sale currency’s minor units. redeem_value (a decimal) is deprecated — see Check a rewards balance.
  • Webhooks state amounts as {currency, value, minor_units}, with value a minor-units numeric string: {"currency": "SGD", "value": "12000", "minor_units": 2} is SGD 120.00. See Webhook event types.

Read the currency lists

Both lists use the standard success envelope. Each entry in data.items has the same shape:

Your enabled currencies

GET /v1/merchant/currencies returns the currencies enabled for one of your outlets, default currency first, plus the outlet_id the list applies to. It’s exactly the list that new sessions and sales accept for that outlet. Follow-up calls such as capture and refund always use the original transaction’s currency.
  • outlet_id is null when you have no default outlet and didn’t name one; the list then applies to your merchant account as a whole.
  • A key bound to an outlet gets 403 auth:outlet-binding-violation for any other outlet. An outlet that doesn’t exist returns 404 checkout:outlet-not-found.
  • Reading it needs the payment-gateway:merchant-config-read scope.
  • A currency that RadiumOne can’t process is left out of the list, because every request in it would be refused.
data.items[0] is your outlet’s default currency — a sensible preselected value for a currency picker.

Every supported currency

GET /v1/currencies is public: no access token, sorted by code. It’s a static reference list that changes only with a RadiumOne release. Use it to validate a code before you send it, not to decide what your outlet accepts.

Cache the currency lists

Both responses carry a weak ETag (W/"..."). Send it back in If-None-Match; when the list hasn’t changed, you get 304 with no body and the same ETag and Cache-Control headers.

What is refused

None of these refusals is worth retrying unchanged. Fix the currency first:

Next steps

Charge or authorize a payment

Send your first amount in minor units.

List your enabled currencies

The full API reference for GET /v1/merchant/currencies.
Last modified on October 25, 2026