# Radom

{% hint style="danger" %}
Radom does not support rebills. Radom does not support an Auth/Capture model.
{% endhint %}

{% hint style="danger" %}
Upsells are supported on Radom. However the process requires the consumer to repeat the entire checkout flow with their Radom wallet. 1-click upsells are not possible with cryptocurrency.
{% endhint %}

<figure><img src="https://3790748257-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT43PzcNjyZtWby9yrGd3%2Fuploads%2FHZCp2lQArb4BzaCrWVD6%2FUntitled.png?alt=media&#x26;token=3a0e5923-38cf-465e-971b-3613fccb75bd" alt="" width="375"><figcaption></figcaption></figure>

#### Step 1 <a href="#step-1" id="step-1"></a>

Setup at Radom

* Obtain API Key from your Radom account
* Enter this webhook URL at Radom. The webhook is required to receive refunds from Radom. Radom will provide a “Verification Key” after creating a webhook. Copy this value and store it for later use.

`https://api.checkoutchamp.com/billers/radom/notification/`

&#x20;

#### Step 2 <a href="#step-2" id="step-2"></a>

Go to CRM > Gateways > Gateway Integrations

Click the Radom gateway tile and press the Activate button

&#x20;

<figure><img src="https://3790748257-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT43PzcNjyZtWby9yrGd3%2Fuploads%2FE9ftbRk0fcamQ6A4W4eZ%2FUntitled.png?alt=media&#x26;token=648e2cf5-3540-4fc8-ba69-e61db6a09595" alt="" width="375"><figcaption></figcaption></figure>

&#x20;**Step 3**

Enter **apiKey** and **verificationKey** from Step 1

Enter **networks** (payment methods)

* Use the list at <https://docs.radom.com/additional-resources/payment_methods/#mainnet>
* Enter each accepted Network in the **networks** box. Use the full name from the Network column in the link. Do not use the Asset column.
* To accept only a specific token on a network, enter Network:Token Address
* The screenshot below contains an example of what the **networks** input may look like. This is only an example. Use actual values from Radom.

Enter **customData** to customize Radom branding

* Specify the leftPanelColor, primaryButtonColor, and slantedEdge for the Radom checkout
* Enter the customization key, a colon, and the desired value
* The screenshot below contains an example

&#x20;

<figure><img src="https://3790748257-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT43PzcNjyZtWby9yrGd3%2Fuploads%2FAcKdbxhAeEjHSoirfTOP%2FUntitled-1.png?alt=media&#x26;token=dddc9679-37fb-4f04-9a63-d271bbbfaf7e" alt=""><figcaption></figcaption></figure>

#### Step 4 (if NOT using CheckoutChamp hosted pages) <a href="#step-4-if-not-using-checkoutchamp-hosted-pages" id="step-4-if-not-using-checkoutchamp-hosted-pages"></a>

Radom processing on your checkout page requires the same script handling as standard 3DS processing. Follow instructions in this document.

[ Direct API 3DS Instructions](https://help.checkoutchamp.com/crm/gateway-setup/direct-api-3ds-instructions)

**Step 5 (if using CheckoutChamp hosted pages)**

* Edit the funnel on which to process with Radom
* Go to Settings > Payments > Alternate Payment Methods. Select the Radom gateway on which to process
* Edit the checkout page
* Drag a Radom button onto the page. Style the button as needed. Set Action=Submit + Route.
* Save and exit the page builder
* Select the Radom button on an arrow leaving the checkout page.
* Publish

{% hint style="warning" %}
**Additional considerations**

* All cryptocurrency transactions are stored in the campaign (fiat) currency
* All refunds must be initiated at Radom. When the refund completes at Radom it will be updated by the webhook defined in Step 1.
  {% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.checkoutchamp.com/crm/gateway-setup/gateway-integrations/radom.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.