Skip to main content
You can send a UOB Rewards redemption and a 3D Secure result on the same purchase. 3D Secure authenticates the amount charged to the card, so the order of steps matters: you pin the card amount left after the redemption first, and only then authenticate.

How it works

1

Optional: verify the cardholder before showing a balance

To check that the shopper holds the card before you show their rewards balance, run a non-payment authentication (purpose: "non_payment" in the Elements SDK). It authenticates no amount and its ref can never be charged. See Verify the cardholder without a payment. This check has its own limits.
2

Check the balance and choose the redemption

3

Pin the card amount

Set the session’s net_payable_amount to the amount left for the card after the redemption, with PATCH /v1/sessions/{session_id}, before the browser starts the payment authentication. See 3D Secure overview: amount rules.
4

Authenticate the payment

Call authenticate() without purpose (or with purpose: "payment"). 3D Secure authenticates the pinned net amount, not the gross order total.
5

Send one purchase with both blocks

Send the gross amount, the loyalty block and three_ds.ref on the same purchase, as in Pay with points.

Limits on the cardholder check

These limits apply only to the non-payment authentication that runs before the balance is shown.
  • 3 challenges per card per checkout session. Only a challenge or decoupled approval that doesn’t end authenticated uses an attempt. A successful authentication restores all 3. After the last one, that card is refused for this check with 422 urn:radiumone:payment-gateway:three-ds:card-attempts-exceeded (retry_allowed: false), and the shopper needs a different card.
  • Up to 3 cards per checkout session, counting the first. On this path only, the shopper can switch to a different card in the same session. Going back to an earlier card counts as another card. Past the limit, the bind fails with 409 urn:radiumone:tokenization:session-card-limit-reached, nothing is charged, and the shopper starts a new checkout.
  • card_attempts_remaining (cardAttemptsRemaining on the Elements SDK result) reports the challenges left for the card, from 0 to 3, as of the final response of the authentication.
  • The session’s overall limit still applies. Both authentications, on every card, share one attempt budget, and answers without a challenge use it too. It can end the flow first, and then only a new session helps.
Payment authentication is unchanged. 3D Secure on the card amount has no per-card limit and no card switch: once it has started, a different card is refused with 409 urn:radiumone:tokenization:session-not-bindable.

When the redemption can’t carry 3D Secure

RadiumOne applies three_ds to a sale that redeems value only where the rewards program’s acquirer supports 3D Secure on redemptions. Otherwise the purchase is refused before anything is charged with 422 urn:radiumone:payment-gateway:three-ds:unsupported-for-redemption (retry_allowed: false), and your three_ds.ref stays usable. Resubmit with a new request_id, either:
  • without the redemption, as a card sale. Its three_ds.ref covers only the net amount you pinned, so set net_payable_amount to the full amount and run authenticate() again first, or
  • with the redemption and without three_ds: the sale is charged without 3D Secure, so you get no liability shift.
A loyalty block that redeems nothing is an ordinary card sale, and any three_ds you send is applied.

When there’s nothing to authenticate

A sale fully paid by vouchers whose values add up exactly to the sale amount, or a session whose net_payable_amount is 0, charges nothing to the card and needs no 3D Secure. See When 3DS is required.

Hosted checkout

Hosted checkout runs these steps for you: see 3D Secure with hosted checkout.

Next steps

Pay with points

The purchase request with a loyalty block.

3D Secure errors

Every 3D Secure error a purchase can return.
Last modified on October 31, 2026