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

# Overview - Resources

> Test, secure, and launch your RadiumOne integration, look up terms and version policy, and find help when you need it.

* **Test every path** — test cards and failure scenarios in sandbox.
* **Launch safely** — a go-live checklist for each integration.
* **Help when you need it** — FAQ, glossary, and support in one place.
* Start here: [Test your integration](/resources/test-your-integration) · [Go-live checklist](/resources/go-live-checklist)

The pages in this tab apply to every integration, whether you use hosted checkout, the Elements SDK, the Payments API, or a mix of them. The product tabs cover how to build. This tab covers how to prove your integration works, launch it safely, and get help.

## Your path to production

<Steps>
  <Step title="Test every scenario in sandbox">
    Run the happy path, declines, timeouts, idempotent replays, and webhook deliveries with sandbox keys and test cards. See [Test your integration](/resources/test-your-integration).
  </Step>

  <Step title="Check your security posture">
    Confirm your PCI DSS scope, where your keys live, and how you verify results server-side. See [Security and PCI scope](/resources/security-and-pci).
  </Step>

  <Step title="Work through the go-live checklist">
    Tick off every item for your integration before you ask for production keys. See the [Go-live checklist](/resources/go-live-checklist).
  </Step>

  <Step title="Switch to production">
    Swap your sandbox keys and hosts for production ones. See [Moving to production](/get-started/sandbox-and-api-keys#moving-to-production).
  </Step>
</Steps>

## Test and go live

<Columns cols={3}>
  <Card title="Test your integration" icon="flask-conical" href="/resources/test-your-integration">
    Test cards and the scenarios to run for each product.
  </Card>

  <Card title="Security and PCI scope" icon="shield-check" href="/resources/security-and-pci">
    PCI scope per integration, key safety, and callback verification.
  </Card>

  <Card title="Go-live checklist" icon="clipboard-check" href="/resources/go-live-checklist">
    Everything to confirm before you switch to production keys.
  </Card>
</Columns>

## Reference

<Columns cols={2}>
  <Card title="Versioning and deprecation" icon="git-branch" href="/resources/versioning">
    How each product is versioned, and the current version of each.
  </Card>

  <Card title="Glossary" icon="book-a" href="/resources/glossary">
    Key prefixes and terms used across this documentation.
  </Card>
</Columns>

## Help

<Columns cols={2}>
  <Card title="Frequently asked questions" icon="circle-question-mark" href="/resources/faq">
    Quick answers on keys, refunds, duplicates, and hosted checkout.
  </Card>

  <Card title="Support" icon="life-buoy" href="/resources/support">
    Contact support, revoke a leaked key, or request a feature enablement.
  </Card>
</Columns>