Skip to main content
UOB Rewards lets a cardholder in an eligible bank loyalty programme (today, UOB UNI$) redeem points or vouchers against a purchase. You check the shopper’s balance first, then send one purchase request that includes the redemption — RadiumOne redeems the points first, then charges the card for whatever remains.

How it works

  1. Your server checks the shopper’s points and voucher balance.
  2. Your UI shows the available vouchers and lets the shopper choose.
  3. Your server sends a single purchase with the gross order amount and the selected redemption. RadiumOne redeems the points, then charges the card for the residual — or nothing, on a full redemption.
UOB Rewards is available with both integrations: with hosted checkout, RadiumOne shows it to the shopper automatically where enabled; with Elements + the Payments API, you build the balance/voucher UI yourself — see Check a rewards balance and Pay with points.

Eligibility

  • The shopper’s card must belong to a participating bank loyalty programme (UOB UNI$ today).
  • Your outlet’s acquirer must be paired with a loyalty acquirer, and the loyalty product must be enabled for it. Without this, a purchase that includes loyalty fails with 422 urn:radiumone:transaction:loyalty-leg-required.
  • The BIN of the card presented decides eligibility at the acquirer level — not every card at an eligible bank is guaranteed to route to the loyalty leg.

Enablement checklist

Before you can use UOB Rewards in production, contact support to confirm:
  • Your acquirer is paired with a loyalty acquirer for the currencies you sell in.
  • The loyalty product is enabled on that pairing.
  • Your terminals are provisioned and validated on the loyalty host.
  • The routing rules that decide which cards get the loyalty leg (for example, UOB BIN ranges) are configured for your account.
Until these are confirmed, a redemption attempt degrades gracefully — see Pay with points for what your server sees.

Limitations

  • Points and voucher redemption only (kind: "sale"). Standalone voucher or coupon redemption (kind: "voucher" / "coupon") is accepted by the schema but always rejected with 422 urn:radiumone:loyalty:redemption-kind-not-supported — don’t send it.
  • No merchant self-void of a grouped sale. A single-leg void returns 409 urn:radiumone:transaction:single-leg-void-forbidden; cancelling a redeemed sale is support-driven. See Refunds and cancellations.
  • 3D Secure isn’t combinable with a redemption yet — see Rewards with 3D Secure.

Next steps

Check a rewards balance

Look up points and vouchers before the shopper pays.

Pay with points

Send the purchase that redeems the balance.
Last modified on September 15, 2026