> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# Razer Gold

> Accept Razer Gold wallet payments from gamers in Asia Pacific, the Americas and Turkey, and check the PSPs that process Razer Gold.

Razer Gold is a prepaid digital wallet for games and digital entertainment. Customers top up their Razer Gold balance and spend it with merchants that accept it, without sharing card details at checkout.

Payrails processes Razer Gold through Razer as the payment service provider (PSP). Open the Razer guide below for its setup steps and request examples.

## How a Razer Gold payment works

Razer Gold is a redirect payment method:

1. The customer selects Razer Gold at checkout.
2. Payrails returns a redirect URL from Razer, and the customer goes to the Razer Gold checkout page in a full browser window.
3. The customer signs in to their Razer Gold wallet and approves the payment.
4. The customer returns to your `returnInfo` URL, and Payrails checks the payment status with Razer.
5. Payrails also receives the signed result from Razer and updates the payment.

Payrails captures Razer Gold payments immediately, so a successful payment is final.

## Supported currencies and countries

Razer Gold supports these presentment currencies: AUD, BDT, BRL, CAD, CLP, COP, HKD, IDR, INR, JPY, MMK, MXN, MYR, NZD, PHP, PKR, SGD, THB, TRY, TWD, USD and VND.

Razer Gold is available to customers based in:

<table>
  <thead>
    <tr><th>Regions</th><th>Countries</th></tr>
  </thead>

  <tbody>
    <tr><td>**Asia Pacific**</td><td>🇦🇺 Australia🇧🇩 Bangladesh🇭🇰 Hong Kong🇮🇳 India🇮🇩 Indonesia🇯🇵 Japan🇲🇾 Malaysia🇲🇲 Myanmar🇳🇿 New Zealand🇵🇰 Pakistan🇵🇭 Philippines🇸🇬 Singapore🇹🇼 Taiwan🇹🇭 Thailand🇻🇳 Vietnam</td></tr>
    <tr><td>**Europe**</td><td>🇹🇷 Turkey</td></tr>
    <tr><td>**Latin America**</td><td>🇧🇷 Brazil🇨🇱 Chile🇨🇴 Colombia🇲🇽 Mexico</td></tr>
    <tr><td>**North America**</td><td>🇨🇦 Canada🇺🇸 United States</td></tr>
  </tbody>
</table>

## Integrate Razer Gold

Choose the PSP that processes Razer Gold for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

> Razer logo
>
> RazerRazer Gold via Razer
>
> [Open](/docs/orchestration/payment-methods/razer-gold/razer)

## Check PSPs

<table>
  <thead>
    <tr><th>Workflow</th><th>[Razer](/docs/orchestration/payment-methods/razer-gold/razer)</th></tr>
  </thead>

  <tbody>
    <tr><td>Payrails SDK</td><td>✔</td></tr>
    <tr><td>Payrails API</td><td>✔</td></tr>
    <tr><td>[Delayed / Manual Capture](/docs/orchestration/payment-acceptance/capture-and-cancel-modes#capture-mode)</td><td>✖</td></tr>
    <tr><td>[Instant Capture](/docs/orchestration/payment-acceptance/capture-and-cancel-modes#capture-mode)</td><td>✔</td></tr>
    <tr><td>[Cancel / Void](/docs/orchestration/payment-acceptance/cancel-a-payment)</td><td>✖</td></tr>
    <tr><td>[Refund / Reverse](/docs/orchestration/payment-acceptance/refund-a-payment)</td><td>✖</td></tr>
    <tr><td>[Save Instruments](/docs/resources/manage-instruments)</td><td>✖</td></tr>
    <tr><td>[Merchant Initiated Transaction (MIT)](/docs/resources/payments/authorization-flags)</td><td>✖</td></tr>
  </tbody>
</table>

## Ways to integrate Razer Gold

* **Payrails SDK:** the [Web SDK](/docs/orchestration/checkout-sdks/web) shows Razer Gold when your workflow returns it as a payment option, and redirects the customer to the Razer Gold checkout page. To control how the redirect opens, listen for the [`actionRequired` event](/docs/orchestration/checkout-sdks/web/guides/action-required-event). Razer Gold opens in a full page, not in a frame.
* **Payrails API:** call [lookup payment options](/docs/orchestration/payment-acceptance/lookup-payment-options), then authorize with `razerGold` as the `paymentMethodCode`. Each PSP guide lists the fields that PSP requires.

In both cases, confirm the final result through [webhook notifications](/docs/orchestration/payment-acceptance/receive-notifications) or the execution status. Don't treat the customer's return to your `success` URL as proof of payment.


## Related topics

- [Razer](/docs/orchestration/integrations/razer.md)
- [Razer Gold via Razer](/docs/orchestration/payment-methods/razer-gold/razer.md)
- [Create a new Ruleset](/reference/createruleset.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.