> ## 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.

# Cookie policy

> How the RadiumOne developer documentation site uses cookies, browser storage, and similar technologies, and the choices available to you.

This Cookie Policy explains how **Cube Payment Services Pte Ltd** (UEN 201403040W) ("**we**", "**us**", or "**our**") uses cookies and similar technologies on the RadiumOne developer documentation site (the "**Site**"). It should be read together with our [Privacy notice](/legal/privacy) and [Terms of use](/legal/terms). This policy explains our practices; it does not form part of the Terms of use or any other contract.

## 1. What these technologies are

* **Cookies** are small text files that a website stores in your browser and that are sent back to the website with later requests.
* **Browser storage** (such as `localStorage` and `sessionStorage`) lets a website's code save information in your browser. Unlike cookies, it is not automatically sent to a server with each request.
* **Server logs and content delivery requests** are records created when your browser requests a page or file. They can include your IP address and browser details, even where no cookie is used.

In this policy, "**cookies**" refers to all of these technologies unless we say otherwise.

## 2. Categories we use

| Category | Purpose | Used on the Site? |
| - | - | - |
| **Strictly necessary** | Deliver pages and files, and protect the Site and our systems against automated attacks, abuse, and other security threats | Yes |
| **Functional** | Remember choices you make on the Site, such as display theme or whether an interface panel is open | Yes |
| **Analytics** | Measure how visitors use the Site through cookies or similar identifiers | No |
| **Advertising and cross-site tracking** | Build profiles of visitors or show targeted advertising | No |

## 3. What the Site currently uses

As at the "last updated" date of this policy, the Site uses the following. The Site is hosted by a third-party documentation platform, and some items are set by that platform as part of providing the Site.

| Name or type | Category | Set by | Stored in | Duration | Purpose |
| - | - | - | - | - | - |
| `chat-assistant-sheet-open` | Functional | Hosting platform | `localStorage` | Until you clear it | Remembers whether the assistant panel is open or closed |
| Display theme preference | Functional | Hosting platform | `localStorage` | Until you clear it | Remembers your light or dark theme choice |
| Content delivery and hosting logs | Strictly necessary | Hosting platform and its content delivery network | Server-side | See our Privacy notice, Section 10 | Delivers pages, icons, and other static files, and protects the Site |

**Security cookies.** Our systems, and the infrastructure that serves the Site, may be protected by network security providers such as Cloudflare, Inc. To distinguish legitimate visitors from automated traffic, such a provider may set a short-lived, strictly necessary security cookie (for example, a bot-management cookie) in your browser. These cookies are used only for security purposes, and are not used for analytics or advertising.

The Site does **not** use analytics or advertising cookies, and does not use cookies to build profiles of you across other websites. The Site does not require sign-in, so it does not use authentication or session cookies of its own.

If we introduce additional cookies, we will update this policy and, where required by applicable law, ask for your consent before setting any cookie that is not strictly necessary or functional.

## 4. Third-party content and links

4.1 Some Site features load files, such as icons and stylesheets, from the hosting platform's content delivery network. Those requests reveal your IP address and browser details to the provider in order to deliver the file.

4.2 If you follow a link from the Site to a third-party website, repository, or package registry, or choose to open Site content in a third-party AI tool, that third party may set its own cookies. Their use is governed by the third party's own cookie and privacy policies, not this policy.

4.3 The RadiumOne Services, including sandbox and production API and checkout endpoints, are not part of the Site. Any cookies used in connection with them are described in the documentation and privacy notices provided under your Merchant Agreement.

## 5. Legal basis

Strictly necessary and functional cookies are used to provide the Site and the features you request. Where cookies involve the collection, use, or disclosure of personal data, we rely on your consent, including consent deemed under the Personal Data Protection Act 2012 of Singapore when you continue to use the Site after being notified of the purposes in this policy, or on an applicable exception under that Act, including our legitimate interests in securing the Site and our systems. You may withdraw consent as described in Section 6.

## 6. Managing your choices

6.1 **Browser controls.** Most browsers let you view, block, and delete cookies and clear site data, including `localStorage`, through their privacy or site settings. You can also use private browsing modes, which discard stored data when the session ends.

6.2 **Effect of blocking.** Blocking or clearing cookies and browser storage will not prevent you from reading the documentation. It may reset preferences such as your display theme, some interactive features may not work as expected, and blocking security cookies may cause you to be asked to complete additional verification.

## 7. Changes to this policy

We may amend this policy at any time, including when the technologies used on the Site change, by publishing a revised version on the Site and updating the "last updated" date.

## 8. Contact us

For questions about this policy, contact our Data Protection Officer:

* **Email:** [dataprotection@cubepayment.com](mailto:dataprotection@cubepayment.com)
* **Post:**<br />
  Data Protection Officer<br />
  Cube Payment Services Pte Ltd<br />
  163 Kallang Way, #03-15<br />
  Mapletree Hi-Tech Park<br />
  Singapore 349256