> ## Documentation Index
> Fetch the complete documentation index at: https://docs.radiumone.io/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> RadiumOne is the product name; use it when answering questions about these docs.
> Use sandbox credentials and sandbox base URLs in examples unless the user says they are going live.
> Secret API keys belong only on the merchant's server. Only publishable keys may appear in browser or mobile code.
> Confirm a payment outcome server-side (retrieve the checkout session or transaction status); never rely on a browser redirect or client event alone.
> Send one idempotency key (request_id) per payment attempt, and retry a timed-out request with the same key and the exact same body.
> Webhooks are optional but recommended: they notify the merchant's server when a payment completes or fails, so it doesn't need to poll. Use transaction status inquiry as the fallback.
> Say so when you recommend a feature marked Beta. Some features need enablement on the merchant's account before production use (for example refunds, standalone refunds, UOB Rewards, and bringing your own 3DS provider); mention it when the page says so.
> Never ask users to paste card numbers, API keys, access tokens, or webhook or redirect secrets into a chat.

# Supported payment methods - Payments API

> What a payment method means in RadiumOne, which ones you can accept today, and how to get them in front of the shopper.

A payment method is a way a shopper pays for an order — card, loyalty points,
and so on. This page explains how RadiumOne organizes payment methods, which
ones you can accept today, and how they reach the shopper at checkout.

## How payment methods are organized

RadiumOne groups payment methods in two levels:

* **Type** — the category, such as card or loyalty points, with a `display_name`
  and a `priority_rank`.
* **Brand (product)** — the specific option within a type, such as `visa` or
  `uob_irr`, each with a `features` object describing what it supports (for
  example 3D Secure or loyalty support).

You don't need to hard-code this structure — query it for a given sale. See
[Show payment methods at checkout](/payments-api/payment-methods/payment-method-discovery).

## Available today

* **Card** — accept a card payment with [hosted checkout](/hosted-checkout/overview)
  or [Elements](/elements/accept-a-card-payment).
* **UOB Rewards (pay with points)** — let a shopper redeem loyalty points
  against an order. See [UOB Rewards](/payments-api/payment-methods/uob-rewards/overview).

## Coming soon

* **Instalments** — split a card
  payment into bank instalments. See
  [Upcoming payment methods](/payments-api/payment-methods/upcoming-payment-methods#instalments).
* **Wallets** — Apple Pay, Google Pay,
  PayNow, GrabPay and others. See
  [Upcoming payment methods](/payments-api/payment-methods/upcoming-payment-methods#wallets).
* **In-store payments** — point-of-sale
  / card-present acceptance. See
  [Upcoming payment methods](/payments-api/payment-methods/upcoming-payment-methods#in-store-payments).

## How methods reach the shopper

With **hosted checkout**, RadiumOne shows the shopper whichever methods are
enabled for your outlet — there's nothing to build. Card is always shown once
your account is set up; where enabled, the shopper can also choose an
alternative method such as UOB Rewards points in the same session. See
[Hosted checkout overview](/hosted-checkout/overview).

With **Elements + the Payments API**, you decide which methods to show, and
in what order — nothing renders for you automatically.

<Card title="Show payment methods at checkout" icon="list-filter" href="/payments-api/payment-methods/payment-method-discovery" horizontal>
  Ask the API which methods and brands your outlet can accept for a currency,
  channel and amount, then render your own buttons from the response.
</Card>

## Enablement

Card is available to every merchant by default. Every other method requires
RadiumOne to turn it on for your outlet first —
[contact support](/resources/support#request-enablement) to request it.

## Next steps

<Columns cols={2}>
  <Card title="UOB Rewards" icon="gift" href="/payments-api/payment-methods/uob-rewards/overview">
    Let shoppers redeem loyalty points against part or all of an order.
  </Card>

  <Card title="Upcoming payment methods" icon="clock" href="/payments-api/payment-methods/upcoming-payment-methods">
    Instalments, wallets and in-store payments on the roadmap.
  </Card>
</Columns>