Skip to main content
A redeemed sale creates a group of one or two transaction legs (payment and loyalty) that share a group_id. Grouped sales follow different cancellation rules than a plain card payment.

Can and can’t

See Handle UOB Rewards void and refund restrictions for the step-by-step walkthrough.
Void while the settlement batch is OPEN. Refund once it’s CLOSED. You can’t do either the other way around:
  • Voiding a transaction whose batch has already closed returns 409 urn:radiumone:tx:void-on-non-open-batch.
  • Refunding a transaction whose batch is still open returns 409 urn:radiumone:tx:refund-on-open-batch.
The boundary is the settlement batch closing, not the card network settling with the issuer. Check GET /v1/transactions/{id}/status or a settlement.* webhook if you’re unsure which state you’re in. See Resolve void and refund conflicts if you hit either error.

Cancelling a redeemed sale

Because a merchant can’t self-void a grouped sale, cancelling one before its batch closes is a support-driven process today — contact support with the group_id from your records or the original response. Once the batch has closed, refund the payment leg for whatever amount the card was actually charged. The redeemed points themselves aren’t reversible through the API; treat a full-redemption return as a case for support.

Next steps

Refund a payment

The referenced-refund flow for the payment leg.

Pay with points

Where group_id and the loyalty block come from.
Last modified on September 15, 2026