# MoonPay Commerce — Full Documentation

> MoonPay Commerce (formerly Helio) is a crypto payment infrastructure API that lets developers accept payments, deposits, and subscriptions on Solana, EVM chains (Ethereum, Polygon, Base), and Bitcoin. Create Pay Links, embed checkout widgets, run headless payment flows, and manage transactions programmatically.

Important notes:

- **API base URL:** Production: `https://api.hel.io/v1` | Devnet: `https://api.dev.hel.io/v1`
- **Authentication:** Pass your public API key as a `publicKey` query parameter and your secret API key as a `Authorization: Bearer <secret>` header. Partner integrations also require an `x-merchant-id` header.
- **Dashboard:** Production: [moonpay.hel.io](https://moonpay.hel.io) | Devnet: [moonpay.dev.hel.io](https://moonpay.dev.hel.io)
- **SDK packages** are published under the `@heliofi/*` namespace on npm.
- **Supported blockchains:** Solana, Ethereum, Polygon, Base, Bitcoin, and more.
- **Webhook verification:** All webhook payloads include an `X-Signature` header containing an HMAC-SHA256 hex digest of the request body, signed with your webhook's `sharedToken`.
- **Error responses** return JSON: `{ "message": "...", "code": <http_status>, "errorCode": "...", "errorType": "..." }`.
- **Rate limiting** is enforced per IP. Specific endpoints (e.g. Pay Link creation) enforce stricter limits per API key.

---

# Introduction
Source: https://docs.hel.io/docs/introduction



## Welcome to MoonPay Commerce

Accept crypto payments globally with ease. MoonPay Commerce integrates directly into your product, enabling customers to pay with assets they already hold while you avoid delays, chargebacks, and high fees.

<img alt="MPC Banner Docs 1" />

## Start Building

Choose how you want to get started:

<Columns>
  <Column>
    <Card title="No Code" icon="stars" href="/docs/for-creators">
      Create payment flows and accept crypto, no code required.
    </Card>
  </Column>

  <Column>
    <Card title="For Developers" icon="laptop" href="/docs/for-developers">
      Build a custom crypto checkout with our APIs and SDKs.
    </Card>
  </Column>
</Columns>

## Core Products

<Columns>
  <Column>
    <Card title="Pay Links" icon="sparkles" href="/docs/for-creators#create-payments">
      Create shareable links to accept crypto payments anywhere.
    </Card>
  </Column>

  <Column>
    <Card title="Checkout Widget" icon="cart-shopping" href="/docs/checkout-widget">
      Embed a customisable crypto checkout on your site.
    </Card>
  </Column>
</Columns>

<Columns>
  <Column>
    <Card title="Subscriptions" icon="arrows-repeat" href="/docs/subscriptions">
      Accept recurring crypto payments automatically.
    </Card>
  </Column>

  <Column>
    <Card title="Deposits" icon="money-check-dollar" href="/docs/deposits">
      Accept and swap crypto directly in your app.
    </Card>
  </Column>
</Columns>

<Columns>
  <Column>
    <Card title="Solana Pay" icon="sparkles" href="/docs/solana-pay-shopify-plugin">
      Accept crypto payments on Shopify with a seamless checkout.
    </Card>
  </Column>

  <Column />
</Columns>

# For Developers
Source: https://docs.hel.io/docs/for-developers

Get started on MoonPay Commerce as a developer and build custom crypto payment flows

# Getting Started

* Log into [moonpay.hel.io](https://moonpay.hel.io/) or [moonpay.dev.hel.io](https://moonpay.dev.hel.io/) with a wallet or email, then use Settings to finish your profile, set up wallets, and invite team members.
* The Developer section provides full access to MoonPay Commerce's API and webhooks.
  * Check out the [API Reference](https://docs.hel.io/reference#/) for detailed endpoints, parameters, and response formats.
  * [**Webhooks**](https://docs.hel.io/reference/webhook/overview#/): The webhooks panel allows you to create new webhooks, track event deliveries, and replay failed events as needed.

<Info>
  MoonPay Commerce also provides an [SDK for developers](https://docs.hel.io/docs/helio-sdk#/).
</Info>

<img alt="" />

# Payment Integration Options

Developers can initiate payments using two primary methods: Pay Links (via `paylinkId`) for structured checkouts, or Deposits (via `depositId`) for flexible, wallet-to-wallet transfers in any crypto.

**Pay Links:** [Generate via API](https://docs.hel.io/reference/paylink/overview) to configure product details, pricing, themes, and redirect URLs.

* Dynamic Pay Links: For flexible pricing, set `"dynamic": true` in the features object. This allows you to define the specific `amount` at the time of payment / charge creation rather than use the same fixed price at the `paylinkId` level.
* Charges: Use a `paylinkId` to create [one-off Charges](https://docs.hel.io/docs/charges) for single-use payments. You can pass custom JSON (e.g., customer IDs or SKU data) with each request.
* Subscriptions: Programmatically manage [recurring billing](https://docs.hel.io/docs/subscriptions#/) with full control over intervals, grace periods, and renewal reminders.

**Deposits:** [Set up Deposits](https://docs.hel.io/reference/deposits/create) to create unique `depositCustomers`and associated deposit addresses across SVM, EVM, and BTC networks. This method is optimized for letting users fund your app with any crypto, ideal for gaming deposits, embedded wallets & trading apps.

# Embed Widgets

* Embed a `paylinkId` as a [Checkout Widget](https://docs.hel.io/docs/checkout-widget#/) in your application for a seamless payment experience. The widget supports customisation and integrates with all the same features as Pay Links.
* Embed a `depositId` as a [Deposit Widget](https://docs.hel.io/docs/deposits#3-serve-the-deposit-ui-in-your-app) in your app

<Info>
  Test and customise your configurations with our easy to use [Widget Builder](https://demo.hel.io/)
</Info>

# Transaction Management

Using the API, you can export all transactions from your account and apply filters such as `paylinkId` or `depositId`, sender key, or date range. This makes it easy to build custom reporting or integrate transaction data into your own systems. See txs endpoint for [depositId](https://docs.hel.io/reference/deposits/list-transactions) and [paylinkId](https://docs.hel.io/reference/transactions/list).

# Code Integrations

MoonPay Commerce also supports more advanced, code-driven integrations, including:

* [Create subscription payments via API](https://docs.hel.io/docs/subscriptions#setting-up-a-subscription)
* [Headless payments](https://docs.hel.io/docs/headless-payments#/)
* [Platform APIs merchant account creation](https://docs.hel.io/reference/platform/overview)

# No Code
Source: https://docs.hel.io/docs/for-creators

Get started on MoonPay Commerce and launch crypto payments in minutes

# Getting Started

* Log into [moonpay.hel.io](https://moonpay.hel.io/) or [moonpay.dev.hel.io](https://moonpay.dev.hel.io/) with an email or wallet, then use Settings to finish your profile, set up wallets, and invite team members.

<img alt="" />

* If you're an existing MoonPay customer, Log in to the [MoonPay Dashboard](https://dashboard.moonpay.com) and select Pay with Crypto > Go to MoonPay Commerce Dashboard. Your account and existing KYB data will sync automatically.

<img alt="" />

## Embedded Wallet

If you sign up via email, we automatically create an embedded wallet for you. You don’t need a browser extension, seed phrases, or an existing wallet, making onboarding seamless and enabling instant access to Web3 apps.

<Warning>
  For users who previously used the Helio wallet, the new login flow uses a different wallet setup. To move funds from your existing Helio wallet, visit [https://legacy.hel.io/](https://legacy.hel.io/) and follow the transfer steps.
</Warning>

***

# Create Payments

MoonPay Commerce supports four payment types:

1. **Pay Links** - MoonPay hosted checkout page
2. [**Checkout Widget**](https://docs.hel.io/docs/checkout-widget#/) - embed payments in your app
3. [**Deposits**](https://docs.hel.io/docs/deposits#) - accept any crypto inside your app
4. [**Subscriptions**](https://docs.hel.io/docs/subscriptions#/) - recurring payments

**Pay Link Creation Flow:**

* **Set product details:** name, price, payout wallets, networks, card payments, swaps, and dynamic pricing.
  * **Subscriptions** include billing intervals (weekly, monthly, quarterly, biannual, yearly), renewal reminders, grace periods, and annual discounts.
* **Token swaps:** allow customers to pay with any supported token while you receive **USDC** (0.25% conversion fee). Can be configured via the UI or the [API](https://docs.hel.io/reference/paylink/overview#token-swaps).
  * **USDC on Solana only:** all payments are converted to **USDC on Solana**.
  * **USDC on Base & Solana:** Solana payments → **USDC on Solana**, EVM payments → **USDC on Base**.

<Info>
  You can only receive funds on EVM networks like Arbitrum and BNB Chain when Token Swaps are enabled. If Token Swaps are disabled, you can’t receive directly in these currencies.
</Info>

* **Advanced options:** [affiliate links](https://docs.hel.io/docs/affiliate-links#/), [discounts](https://docs.hel.io/docs/discounts#/), [split payments](https://docs.hel.io/docs/split-payments#/), [Discord](https://docs.hel.io/docs/discord-memberships#/)/[Telegram](https://docs.hel.io/docs/telegram-memberships#/) memberships, and [gated payments](https://docs.hel.io/docs/gated-payments#/).
* **Final customisation:** pay link theme (light/dark mode, colors), success redirect URL.

<img alt="" />

***

# Managing Payments

* All transactions appear in the dashboard under the Transactions tab. Each record shows the type of payment (single, subscription, or refund), transaction ID, amount, time, and detailed information.
* From here, you can also issue refunds when needed.
* For reporting, all transaction data can be exported as a CSV file.

<img alt="" />

### Updating Your Payout Wallet

If you need to change the wallet that receives payments:

1. Go to **Settings → Wallets** in your Helio Dashboard.
2. Add a **Linked** or **Payout Wallet**.
3. When creating a payment (Step 1 of the payment creation flow), you can choose which wallet will receive the funds for that specific payment.

<img alt="" />

<Info>
  **Note:** Your **main wallet** is used as the **default recipient** for all payments unless another wallet is explicitly selected during payment setup.
</Info>

***

# No Code Integrations

MoonPay Commerce also makes integration simple with out-of-the-box options, including:

* [Shopify Solana Pay Plugin](https://docs.hel.io/docs/solana-pay-shopify-plugin#/)
* [Telegram Bot Integration](https://docs.hel.io/docs/telegram-memberships#/)
* [Discord Bot Integration](https://docs.hel.io/docs/discord-memberships#/)

# Deposits
Source: https://docs.hel.io/docs/deposits

Let users fund your app with any crypto, ideal for gaming deposits, embedded wallets & trading apps.

<Info>
  Before going live, you're required to complete [<u>KYB verification</u>](https://docs.hel.io/docs/verification) via the dashboard. Alternatively, get a link from your MP Account Manager.

  **Note:** KYB is not required to start the integration process.
</Info>

## 1. Create your Deposit

Create a deposit via the [<u>Create Deposit endpoint</u>](https://docs.hel.io/reference/deposits/create) or the [<u>dashboard</u>](https://moonpay.hel.io/). Upon creation, a `depositId` will be returned. Configure the following options:

* **Deposit Name:** Assign a unique name to the deposit. Within this section, you can:
  * **Recipient Currency:** Specify the blockchain/currency in which you wish to receive fund
  * **Payment Options:** Enable **Transfer Manually, Connect Wallet** and **Add Money**.

    <Info>
      **The Add Money option (card, Apple Pay, etc.) requires MoonPay Ramps to be enabled.**

      * Set up MoonPay and obtain your API keys via the [Ramps documentation](https://dev.moonpay.com/v1.0/docs/ramps)
      * Add your MoonPay keys in the MoonPay Commerce Dashboard **(Settings → Integrations → MoonPay Ramps)**.
        For questions, contact [support@moonpay.com](mailto:support@moonpay.com)
    </Info>

    * **Customisation:** Update badges and CTA (Call to Action) copy
  * **Notifications:** Enable email notifications to receive updates when a deposit is successfully completed.

## 2. Create a Deposit Customer

Generate a [<u>Deposit Customer</u>](https://docs.hel.io/reference/deposit-customers/create) via the API and their associated deposit addresses across SVM, EVM, and BTC networks.

* **Required Parameters:** To create a customer, you must specify a unique `customerId`, a `recipientWallet`, and any optional metadata via the `additionalJson` payload.
* **Save the token:** Store the returned Deposit Customer token. This token allows you to reuse the same deposit address for subsequent transactions from the same customer.
* **Related endpoints:** use the [<u>Update Deposit Customer</u>](https://docs.hel.io/reference/deposit-customers/update) and [<u>Get Deposit Customer</u>](https://docs.hel.io/reference/deposit-customers/retrieve) endpoints as needed.
* **Test Customer Deposit Session:** In this step you can simulate a deposit widget. You must define a `customerId` and a `recipientWallet` to generate the test environment.

## 3. Build Your Own or Serve our Deposit UI in Your App

### Headless support

* Serve deposit addresses in your own UI. Create and store the `depositCustomerToken` -> use the [<u>Get Deposit Customer</u>](https://docs.hel.io/reference/deposit-customers/retrieve) endpoint to get the `depositWallets` array
* Use the [<u>Record Wallet Activity endpoint</u>](https://docs.hel.io/reference/deposit-wallet/record-activity) whenever you display a deposit wallet to a customer. This increases balance polling and detect incoming payments more quickly
* Use [<u>Get Deposit Currencies</u>](https://docs.hel.io/reference/currency/list-deposit) to check available currencies

### Deposit Widget Setup

Embed the deposit widget in your app using the following [<u>NPM package</u>](https://www.npmjs.com/package/@heliofi/deposit-react) . The below configuration options are available for customising your deposit widget via config:

<Info>
  Use our [demo environment](https://demo.hel.io/) to test display and other configurations. Simply toggle to the Deposit view and paste the Deposit Customer token.
</Info>

`display`

Controls how the deposit flow is rendered on your page.

* **Type**: `'inline' | 'button' | 'new-tab'`
* **Default**: `'inline'`
* **Required**: No

**Values**:

* `'inline'` - Embeds the deposit flow directly in the container element
* `'button'` - Renders a button that opens the deposit flow in a modal
* `'new-tab'` - Renders a button that opens the deposit flow in a new browser tab

<Info>
  If you enable **Add Money** and use the deposit widget in **inline** or **button** mode, your domain(s) must be whitelisted by MoonPay Ramps. In some cases, this may require additional KYB. You can always use **new-tab** mode without domain whitelisting, or disable the Pay with Cash option.
</Info>

***

`network`

Specifies the environment for the deposit flow.

* **Type**: `'test' | 'main'`
* **Default**: `'main'`
* **Required**: No

**Values**:

* `'test'` - Use the test/sandbox environment for development and testing
* `'main'` - Use the production environment for live transactions

***

`themeMode`

Specifies the default light/dark mode. Alternatively you can also set a fixed Company Theme (Settings -> Merchant settings) that overrides this config.

* **Type**: `'dark' | 'light'`
* **Default**: `'undefined'`
* **Required**: No

**Values**:

* `'dark'` - The widget uses dark mode
* `'light'` -The widget uses light mode

<Info>
  If `themeMode` is **undefined** and **no Company Theme is set**, the deposit flow will automatically match the user’s system light/dark mode.
</Info>

***

`variant`

Minimal removes padding and background for inline embeds

* **Type:** `'default' | 'minimal'`
* **Default**: `default`
* Required: no

**Values:**

* `'default'` – Standard embed with padding and background
* `'minimal'` – Removes padding and background for inline embeds

***

`openWalletConnectInNewTab`

Controls whether the WalletConnect flow opens in a new browser tab.

* **Type:** boolean
* **Default:** false
* **Required:** No

**Values:**

* `true` – WalletConnect opens in a new browser tab
* `false` – WalletConnect opens in the current tab or modal

<Info>
  **Note:** For better UX, consider setting this conditionally (e.g. `openWalletConnectInNewTab={wallet.isConnected}`) so a new tab is only opened when needed.
</Info>

***

`forcedStep`

Forces the deposit flow to begin at a specific step, skipping any preceding steps in the default deposit journey.

* **Type:** 'connect-wallet' | 'wallet-display' | 'moonpay-onramp'
* **Default:** undefined
* **Required:** No

**Values:**

`'connect-wallet'` — Forces the flow to start at the **Connect Wallet** step.

`'wallet-display'` — Forces the flow to start at the **Wallet Display** step.

`'moonpay-onramp'` — Forces the flow to start directly at the **MoonPay Onramp** step.

***

`currentlyConnectedWallet`

Allows the host application to pass an already connected user wallet into the deposit flow, surfacing it as an additional selectable option.

* **Type:** ConnectWalletSelection
* **Default:** undefined
* **Required:** No

**Fields:**

* `wallet` — The connected wallet provider.
* `blockchain` — The chain the wallet address belongs to.
* `address` — The connected wallet address.

`wallet` values (DepositConnectWallet)

* `'METAMASK'`, `'PHANTOM'`, `'TRUST_WALLET'`, `'WALLET_CONNECT'`

`blockchain` values

* `'SOL'`, `'ETH'`, `'BASE'`, `'POLYGON'`, `'ARBITRUM'`, `'BSC'`, `'ABSTRACT'`, `'HYPERLIQUID'`

```javascript theme={null}
// Optional: Pre-provides a wallet that is already connected in the host application.
  currentlyConnectedWallet?: {
    wallet: string;
    blockchain: string;
    address: string;
  };
```

### Embedding the widget inside a React app

Embed the deposit widget in your React application using the [Deposit Widget on npm](https://www.npmjs.com/package/@heliofi/deposit-react).

```typescript theme={null}
import { MoonpayCommerceDeposit } from '@heliofi/deposit-react';

interface MoonpayCommerceDepositConfig {
  // Required: Your unique deposit customer token
  // Create it from https://commerce.moonpay.com
  depositCustomerToken: string;

  // Optional: Network to use
  // 'main' = Mainnet
  // 'test' = Testnet
  network?: 'test' | 'main';

  // Optional: Controls how the deposit flow is rendered on your page.
  // 'inline' = Embeds the deposit flow directly in the container element
  // 'button' = Renders a button that opens the deposit flow in a modal
  // 'new-tab' = Renders a button that opens the deposit flow in a new browser tab
  display?: 'inline' | 'button' | 'new-tab'
  
	// Optional: Theme to use
  // 'dark' = Dark mode
  // 'light' = Light mode
  themeMode?: 'dark' | 'light';
  
  // Optional: Opens WalletConnect in a new browser tab when enabled	
  // Tip: Best used conditionally (e.g. openWalletConnectInNewTab={wallet.isConnected})
	openWalletConnectInNewTab?: boolean;
  
	// Optional: Forces the deposit flow to start at a specific step
	// 'connect-wallet' = start at wallet connection
	// 'wallet-display' = start at wallet display/selection
	// 'moonpay-onramp' = start directly at MoonPay onramp
  forcedStep?: 'connect-wallet' | 'wallet-display' | 'moonpay-onramp';

  // Optional: Called when deposit completes successfully
  // Note: this might not be working in the current beta version
  onSuccess?: (data: {
    transaction?: string;
    depositCustomer?: unknown;
  }) => void;

  // Optional: Called if an error occurs
  // Note: this might not be working in the current beta version
  onError?: (error: { errorMessage?: string; transaction?: string }) => void;
}

function App() {
  return (
    <MoonpayCommerceDeposit
        config={{
    			depositCustomerToken: 'your-deposit-customer-token',
        	onSuccess: (data) => {
          	console.log('Deposit completed:', data);
        	},
        	onError: (error) => {
          	console.error('Deposit failed:', error);
        	},
      }}
    />
  );
}
```

### Optional: Preload Assets with the Provider

To improve load performance, you can optionally wrap your application with the `MoonpayCommerceDepositProvider`.

The provider preloads the required JavaScript assets ahead of time, so when `<MoonpayCommerceDeposit />` renders, it does not need to wait for the scripts to load.

**Import**

```text theme={null}
import { MoonpayCommerceDepositProvider } from "@heliofi/deposit-react";
```

**Usage (Next.js example)**

The provider takes no props and should be placed near the root of your application (e.g. `layout.tsx` or `_app.tsx`):

```text theme={null}
// layout.tsx or _app.tsx
export default function RootLayout({ children }) {
  return (
    <YourOtherProviders>
      <MoonpayCommerceDepositProvider>
        {children}
      </MoonpayCommerceDepositProvider>
    </YourOtherProviders>
  );
}
```

**Notes:**

* `children` should include the rest of your application, including any usage of `<MoonpayCommerceDeposit />`.
* This setup is optional. If you do not use the provider, assets will still load automatically when `<MoonpayCommerceDeposit />` is rendered.

**Vanilla JS**

If you are not using React.js, you can alternatively embed using the pure JS approach like below:

```html theme={null}
<script type="module" src="https://embed.deposits.hel.io/assets/index-v1.js" id="deposit-script"></script>

<div id="deposit-container"></div>

<script>
  document.getElementById('deposit-script').addEventListener('load', () => {
    window.moonpayCommerceDeposit(
      document.getElementById('deposit-container'),
      {
        depositCustomerToken: 'your-token-here',
        network: 'test',
        display: 'inline',
        onSuccess: () => {
          console.log('Deposit completed!');
        },
        onError: (error) => {
          console.error('Deposit error:', error.message);
        },
      }
    );
  });
</script>
```

**Iframe**

Alternatively you can embed an iframe using the HTML snippet below. It lets users deposit crypto or pay by card directly on your site without leaving your app.

```html theme={null}
<iframe
  allow="clipboard-write"
  style="width:420px; height:260px;"
  src="https://moonpay.hel.io/embed/deposit/acac3ec9-f8f6-4128-8159-a91e418e2581"
/>
```

Replace the token at the end of the `src` URL with your own `token` returned when creating the customer deposit via the API (e.g. `acac3ec9-f8f6-4128-8159-a91e418e2581`) to render the correct deposit widget.

**Iframe Post Message Events**

Our deposit widget emits structured postMessage events that let your application react instantly to lifecycle changes such as completion, errors, or height updates, keeping your interface responsive and in sync without requiring a page reload.

| **Event**       | **Payload**                   | **When it fires**                                                   |
| --------------- | ----------------------------- | ------------------------------------------------------------------- |
| onSuccess       | `{}` (empty object)           | Deposit flow completed and the merchant has been successfully paid. |
| onError         | `{ message: string }`         | Something went wrong                                                |
| onHeightChanged | `{ height: number } `(pixels) | The widget needs a new height (e.g. after a step change)            |
| onReady         | `{}` (empty object)           | Widget has fully initialised and is ready                           |

The snippet below illustrates how to integrate and respond to our postMessage events within a React component.

```typescript theme={null}
import { useEffect, useState } from "react";

export const Deposit = () => {
  // Dynamic height set by the deposit widget via postMessage
  const [iframeHeight, setIframeHeight] = useState(0);

  useEffect(() => {
    // Handle events sent from the deposit widget iframe
    const handleMessage = (event: MessageEvent) => {
      // Only process messages coming from the Helio/MoonPay widget
      if (event.origin !== "https://moonpay.hel.io") return;

      const data = event.data;

      switch (data.type) {
        // Widget requests the parent to resize the iframe
        case "onHeightChanged":
          setIframeHeight(data.height || 0);
          break;

        // Deposit flow completed successfully
        case "onSuccess":
          alert("Deposit completed");
          break;

        // An error occurred inside the widget
        case "onError":
          alert(`Deposit error: ${data.message}`);
          break;

        default:
          break;
      }
    };

    // Subscribe to postMessage events
    window.addEventListener("message", handleMessage);

    // Clean up on unmount
    return () => window.removeEventListener("message", handleMessage);
  }, []);

  return (
    <iframe
      allow="clipboard-write"
      className="rounded-3xl shadow-2xl"
      // Apply dynamic height returned by the widget
      style={{ width: 420, minHeight: 260, height: iframeHeight }}
      src="https://moonpay.hel.io/embed/deposit/ad1ecf2d-f535-41f8-96df-fd6a45a27cdd"
    />
  );
};
```

<Info>
  Always validate the `event.origin` before handling messages from the widget. This ensures you only process events coming from our domain and ignore anything unexpected.
</Info>

## 4. Use Webhooks to Confirm Deposits on Your Backend

Create a webhook to listen for customer deposit events either in the dashboard under Developer Settings (see [<u>here</u>](https://docs.hel.io/docs/for-developers#getting-started) for more information) or via the [<u>Create a Deposit Webhook endpoint</u>](https://docs.hel.io/reference/webhook/deposit/create). You can find payload examples here.

## Supported Chains and Currencies

Use [**Get Deposit Currencies**](https://docs.hel.io/reference/currency/list-deposit) to check all available currencies and chains. Users can choose their preferred network and currency when making a deposit. Deposited funds are then bridged and swapped into your specified recipient currency.

You can request support for additional currencies and blockchains by contacting [commerce@moonpay.com](mailto:commerce@moonpay.com).

### Demo

<iframe title="YouTube video player" />

# Charges
Source: https://docs.hel.io/docs/charges

Create single-use Pay Links and checkout sessions

**Charges** are single-use checkout pages generated from a `paylinkId`. They’re ideal for mobile flows, deep-linking, QR codes, embedded pay buttons, simple website builders (like Wix), e-commerce plugins, and other custom payment flows.

<img alt="" />

## How to Set Up and Use a Charge

1. **Via API:** Generate a charge using the API, see endpoint [here](https://docs.hel.io/reference/charge/create). This will return a URL to the charge page that users can use to complete their payment.
2. **Via Embedded Widget:** To use a charge within your [checkout widget](https://docs.hel.io/docs/checkout-widget), pass the `chargeToken` field in your configuration code. This value can be found at the end of the charge page URL returned when generating a charge via the API e.g. `a1f67a3a-2152-4124-ad71-a8129e6d2e63`. This allows you to integrate charges directly into the checkout widget. For more information see [here](https://docs.hel.io/docs/checkout-widget#common-config-options).

## Charges vs Pay Links

Below is a comparison of standard MoonPay Commerce Pay Links and Charges, highlighting their descriptions, use cases, and key advantages.

|             | **Charges**                                                                                                                                                                                                                                                                                                                                                                                                                                                  | **Pay Links**                                                                                                                                                                                                                                                                                                                              |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Description | A single-use checkout page generated from a `paylinkId`. Once the payment succeeds, the link cannot be reused. Can be hosted or embedded                                                                                                                                                                                                                                                                                                                     | A reusable payment link that opens a checkout page where users can connect their wallet and pay in crypto. The same link can be shared and used multiple times. Can be hosted or embedded.                                                                                                                                                 |
| Use Cases   | <ul><li>One-off payments</li><li>E-commerce where each cart needs a unique charge</li><li>When you need to attach order-specific details</li></ul>                                                                                                                                                                                                                                                                                                           | <ul><li>Accept ongoing payments</li></ul>                                                                                                                                                                                                                                                                                                  |
| Pros        | <ul><li>Works well for integrations that need single-use checkouts</li><li>Unique per transaction</li><li>Supports `additionalJson` via API for passing customer details (e.g. item, customer data) enabling granular tracking per charge</li><li>Supports [<u>dynamic creation</u>](https://docs.hel.io/docs/for-developers#payment-integration-options) via API with price set at checkout</li><li>Payment status can be tracked programatically</li></ul> | <ul><li>Easy to share and reuse</li><li>Supports `additionalJson`via the [<u>Embedded Widget</u>](https://docs.hel.io/docs/checkout-widget) for passing customer details (e.g. item, customer data) enabling granular tracking per transaction.</li><li>Great for merchants and businesses that want a "universal checkout link"</li></ul> |

## How to Show Pay Link Details on a Charge Page

Within MoonPay Commerce, you can display the product name, description, and image from your pay link directly on the charge page, mirroring your original pay link.

To do this:

1. Ensure your `paylinkId` uses [**dynamic pricing**](https://docs.hel.io/docs/for-developers#payment-integration-options). This can be toggled in the dashboard or set via the API when [creating](https://docs.hel.io/reference/paylink/create) or [updating](https://docs.hel.io/reference/paylink/update) a `paylinkId` by setting `"dynamic": true` in the features object.
2. In **Step 3** of the Pay Link creation process, toggle **“Show product details”** under the Pay Link tab. Alternatively, you can enable this via the API by setting `showDetailsForCharge` to `true` within the `features` object when [creating](https://docs.hel.io/reference/paylink/create) or [updating](https://docs.hel.io/reference/paylink/update) a pay link.
3. You can also define a `successRedirectUrl`paramter when creating a charge. This is the redirect URL to use after a successful payment. The parent Pay Link must have a redirect URL enabled, and this value overrides the default success redirect URL.

<img alt="" />

# Subscriptions
Source: https://docs.hel.io/docs/subscriptions

Crypto subscription payments made easy

Set up and manage subscription payments using renewal reminders & charges (single-use checkout sessions), ideal for SaaS apps, Discord memberships, digital services, and more.

# How It Works

1. Create your [subscription payment](/docs/subscriptions#/setting-up-a-subscription) via the dashboard. Generate a shareable Pay Link or embed the Checkout Widget in your app.
2. Customers connect their wallet and provide their email during their first checkout. Use [webhooks](https://docs.hel.io/reference/webhook/overview) and the [API](https://docs.hel.io/reference) to confirm and query subscriptions records (started, renewed, ended).
3. Each month, customers receive email reminders directing them to a [Charge](/reference/charge/overview#) page to renew with a single tap of their wallet. Users can also renew at any time from the [buyer dashboard](/docs/buyer-dashboard#/).

<img alt="" />

# Setting up a Subscription

Follow these steps to configure a Subscription in your dashboard:

1. [**Create a Pay Link**](http://docs.hel.io/docs/for-creators#create-payments)

* On the dashboard, navigate to **Create Payment** and select the **Subscription** template. You can also embed the Pay Link in your app as a Checkout Widget.

<img alt="" />

<Info>
  You can also create subscriptions via the API using the [Create a Pay Link endpoint](https://docs.hel.io/reference/paylink/create). Set `isSubscription: true` in `features` and define `subscriptionDetails`.
</Info>

2. **Configure your Subscription Pay Link**

* **Billing Settings:** Choose between monthly or annual subscriptions. If you choose monthly you can also enable an optional annual discount.

<img alt="" />

* **Renewal Reminders:** Set the number of days before expiration to send renewal reminders. Customers will receive daily notifications until their subscription ends.
  * **Example:** If set to 3, users will receive reminders once per day for the last 3 days of their subscription before it expires.

<img alt="" />

<Info>
  You can test renewal reminders on our development environment [moonpay.dev.hel.io](https://moonpay.dev.hel.io/) . In this environment subscriptions operate on a 5-minute cycle: renewal reminders are sent at 5 minutes, the grace period begins at 10 minutes, and subscription ends after 15 minutes.
</Info>

* **Grace Period:** Define the number of extra days (if any) during which the customer can still make a payment. The customer’s renewal date remains unchanged. If no payment is made by the renewal date or within the grace period, the subscription will expire automatically.

# Managing and Tracking Subscriptions

Merchants have multiple ways to track and manage subscriptions on the platform:

1. [**Webhooks**](/reference/webhook/overview#/)

* Setup webhooks to receive real time notifications when a subscription starts, renews and ends.
* This enables you to automate subscription management and integrate it into your existing system.

2. [**API**](https://docs.hel.io/reference/getting-started)

* You can retrieve a specific subscription by querying its details via API, allowing you to check its status and other relevant information.
* You can also fetch all subscriptions under your account, providing an overview of active, expired, and canceled subscriptions.
* You can programatically create subscription pay links

3. [**Discord Memberships**](/docs/discord-memberships#/)

* The Discord bot assigns a role when a subscription starts and removes the role when a subscription ends.

# Cancelling Subscriptions

1. **Cancel and Individual Subscription**

* The subscription automatically expires when the user decides not to renew.

2. **Cancel All Subscriptions**

* Disable the Pay Link, which will prevent all users from renewing their subscriptions.

# Anonymous Subscriptions

You can disable email reminders and rely entirely on webhooks, allowing you to handle renewal notifications through your own in-app reminders or automated workflows.

**To set this up:**

1. **Create the Subscription Pay Link via API**

* [Create a pay link via API](https://docs.hel.io/reference/paylink/create) . In your request, set `"isSubscription": true` inside the features object, and include the subscriptionDetails object with relevant subscription configuration. To disable email reminders, set `"isAnonymous": true` inside the `subscriptionDetails` object.

<CodeGroup>
  ```bash JSON theme={null}
  "features": {
      "isSubscription": true
    }
  ```
</CodeGroup>

<CodeGroup>
  ```bash JSON theme={null}
  "subscriptionDetails": {
      "renewalReminders": 2,
      "gracePeriod": 3,
      "annualDiscountBps": 10,
      "interval": "QUARTER",
      "isAnonymous": true
    }
  ```
</CodeGroup>

2. **Create a Subscription Webhook**

* Once the subscription is created, you can set up a [subscription webhook](https://docs.hel.io/reference/webhook/paylink-subscription/create). We will send the following webhook events to your system: `SUBSCRIPTION_STARTED` (when the subscription begins), `SUBSCRIPTION_PENDING_PAYMENT` (for renewal and grace period payments) and `SUBSCRIPTION_ENDED` (if the buyer fails to pay or the subscription finishes)
* Each webhook payload will include a `nextChargeUrl` and `chargeTokenfield`. This is the direct link to the buyer’s payment page for the next renewal. You can use this URL to prompt the buyer within your own product or notification system. For example:

<CodeGroup>
  ```bash JSON theme={null}
  "nextChargeUrl": "https://app.dev.hel.io/charge/7e75a4fb-32fd-4aa9-b787-b4ca04289932",
  "chargeToken": "7e75a4fb-32fd-4aa9-b787-b4ca04289932"
  ```
</CodeGroup>

Alternatively, the buyer can log into [moonpay.hel.io](https://moonpay.hel.io/) and access the Buyer Dashboard by toggling between the Merchant/Buyer Dashboard option at the top of the page.

You can view more about our webhooks [here](https://docs.hel.io/reference/webhook/overview#/).

# Headless Payments
Source: https://docs.hel.io/docs/headless-payments

Run complete payment flows via API - no UI required

Using MoonPay Commerce, you can make end-to-end headless payments with no UI required. This is ideal for seamless integrations with third-party services, allowing merchants to accept payments through MoonPay Commerce without a UI.

<Info>
  This feature is currently supported **only on the Solana network**.
</Info>

<Info>
  There's also an OpenClaw skill available for headless functions - [https://clawhub.ai/mavagio/mpc-accept-crypto-payments](https://clawhub.ai/mavagio/mpc-accept-crypto-payments)
</Info>

# How It Works

* Merchants generate Pay Links that define the payment request, including supported currencies.
* Payers prepare a transaction via the API using the Pay Link and their public key.
* MoonPay Commerce provides the transaction payload (serialized transaction, message, and token) needed for signing.
* Payers sign and submit the transaction, completing the payment fully through the API without a UI.

## How to Get Started

1. **Create a Pay Link**

The merchant creates and shares a **Pay Link ID**. Optionally, they may also specify a **currency ID**.

* If no currency is provided, it will default to **USDC**.
* If USDC is not available, the first enabled currency on the Pay Link will be used.

2. **Prepare the Transaction**

The payer calls the [**prepare endpoint**](https://docs.hel.io/reference/transaction/headless/prepare), passing the following parameters:

* `paymentRequestId` - The Pay Link ID
* `senderPublicKey `- the payer's public key
* `currencyId` (optional)
* any other required fields (see API reference for full list)

3. **Sign the Transaction**

The `/prepare` endpoint responds with:

* `transactionToken` - Identifier required to submit the signed transaction.
* `transactionMessage` - Metadata or message tied to the transaction.
* `serializedTransaction` - Unsigned transaction data to be signed by the payer.
* `addressLookupTableAccounts` - Accounts used to resolve addresses in the transaction.

To sign the transaction, you can use the `WalletService` helper shown below:

<CodeGroup>
  ```bash TypeScript theme={null}
  import { Keypair, VersionedTransaction } from '@solana/web3.js'
  import bs58 from 'bs58'
  import { PrepareTransactionExtended } from '@heliofi/common'

  class WalletService {
    private getPrivateKey(): string {
      // The base58 encoded private key.
      const privateKey = import.meta.env.VITE_WALLET_PRIVATE_KEY
      if (!privateKey) {
        throw new Error('Wallet private key not configured.')
      }
      return privateKey
    }

    createWallet() {
      try {
        const privateKey = this.getPrivateKey()
        // The Keypair object built from the private key.
        return Keypair.fromSecretKey(bs58.decode(privateKey))
      } catch (error) {
        console.error('Error creating wallet:', error)
        throw error
      }
    }

    async signTransaction(
      preparedTransaction: PrepareTransactionExtended,
    ): Promise<string> {
      try {
        const wallet = this.createWallet()
        // The serialized transaction from the prepared transaction (The response from the prepare endpoint).
        const { serializedTransaction } = preparedTransaction

        // Create a VersionedTransaction object from the serialized transaction.
        const vtx = VersionedTransaction.deserialize(
          Buffer.from(serializedTransaction!, 'base64'),
        )

        // Sign the transaction with the wallet.
        vtx.sign([wallet])

        // Serialize the signed transaction and return it as a base64 string.
        const signedAsBufferJson = Buffer.from(vtx.serialize()).toString('base64')

        return signedAsBufferJson
      } catch (error) {
        console.error('Error signing transaction:', error)
        throw new Error(
          `Failed to sign transaction: ${error instanceof Error ? error.message : 'Unknown error'}`,
        )
      }
    }

    getWalletAddress(): string {
      try {
        const wallet = this.createWallet()
        return wallet.publicKey.toBase58()
      } catch (error) {
        console.error('Error getting wallet address:', error)
        throw error
      }
    }
  }

  export const walletService = new WalletService()
  ```
</CodeGroup>

4. **Submit the Transaction**

The payer calls the [**submit endpoint**](https://docs.hel.io/reference/transaction/headless/submit), providing:

* the `signedTransaction` value
* the `transactionToken` from the `/prepare` response.

This submits the fully signed transaction for processing.

# Checkout Widget
Source: https://docs.hel.io/docs/checkout-widget

Embed crypto payments in your website or app with a few lines of code

Integrate the MoonPay Commerce Checkout Widget with just a few lines of code to accept USDC, 100+ digital currencies and card payments via a seamless on-ramp flow.

* Embed a `paylinkId` as a Checkout Widget in your application for a seamless payment experience. Explore the configurations below
* Embed a `depositId` as a Deposit Widget in your app. [Learn more about deposit widget configuration options](https://docs.hel.io/docs/deposits#3-serve-the-deposit-ui-in-your-app)

Test and customise your configurations with our easy-to-use widget builder

<Info>
  [Checkout Widget Builder](https://demo.hel.io/)
</Info>

# Get started

* Log into [MoonPay Commerce](https://app.hel.io/) to setup your `paylinkId` and generate the code snippet on the final step of our payment creation flow. Use [https://demo.hel.io/](https://demo.hel.io/) to customise your theme & config
* Our standard way to embed our checkout is with our JS/HTML embed - simply paste into your code builder as follows
* If you want to set the price in your widget programmatically, set the price to `dynamic` in the dashboard and pass the `amount`

# MoonPay Commerce Checkout (React)

If you have a React based app, then the easiest way to embed MoonPay Commerce Checkout is with our React component.

* [NPM Package](https://www.npmjs.com/package/@heliofi/checkout-react)

Install the dependency:

<CodeGroup>
  ```bash Shell theme={null}
  yarn add @heliofi/checkout-react
  # or npm install @heliofi/checkout-react
  # or pnpm add @heliofi/checkout-react
  ```
</CodeGroup>

Then in your React components import it in (simply grab the example code snippet for our React component on step 4 when creating your Pay Link).

<CodeGroup>
  ```bash JavaScript theme={null}
  import {HelioCheckout} from '@heliofi/checkout-react'

  const helioConfig = {
      paylinkId: "6571e7cd4a2bee8095ee84da",
      amount: "5.99",
  };

  function YourCheckoutComponent() {
    return <HelioCheckout config={helioConfig} />;
  }
  ```
</CodeGroup>

**Note:** if you are dynamically generating the config object, we recommend wrapping it in `useMemo()`

# Config Options

The configuration options object is the same for our Vanilla JS and React version.

## Common config options:

* One of the following must be set (but not both)
* `paylinkId`
  * **This is the ID for the Pay Link you would like to embed**
    * \*\*example: \*\*`paylinkId: "6571e7cd4a2bee1095ee84da"`
* `chargeToken`
  * [**A charge token (you can create charges via our API).**](/reference/charge/create#/)
    * **example:** `chargeToken: "05adc323-0450-4ef8-b127-18949b9ff485"`
* `network` (optional - default is `main`)
  * **values:** `main` or `test`
  * **example:** `network: "test"`
  * **This is only required if you generated a Pay Link on our dev/testnet site** `https://app.dev.hel.io/`
  * [See note below](/docs/checkout-widget#/our-network-options-for-testnet) how our `network` value works.
* `paymentType` (optional - default is `paylink`)
  * **values:** `paylink` or `paystream`
  * **example:** paymentType: "paystream"
  * **This is only required if you set up a recurring paystream embed.**
  * If your Pay Link is recurring, the code snippet on step 4 will already include `paymentType: "paystream"`
* `platform` only if you are embedding from presale.magiceden.io
  * [**If you are embedding our checkout for a Pay link created from moonpay.hel.io you should not set this value.**](https://moonpay.hel.io/)
  * **values:** `magic_eden`
  * **example:** platform: `magic_eden`

## Customising the look of the embed:

* `display` (optional - default is `inline`)
  * **values:** `button` `inline` or `new-tab`
  * **example:** `display: "button"` Use this to display a button that opens up a modal with our checkout flow
  * [**`example:display: "new-tab" Use this to display a button that opens up a unique, single use checkout page in a new tab. The "charge pages" are optimal for mobile payment flows, deep-linking, QR codes, embedded pay buttons on simple websites like Wix, or other custom payment flows. Learn more about Charges`**](https://docs.hel.io/docs/charges)
* `primaryPaymentMethod` (optional - default is `crypto`)
  * values: `crypto` or `fiat`
  * example: `primaryPaymentMethod: "fiat"`
  * **`If set tofiat, then 'pay with card' will be the default button option.`**
* `customTexts` (optional)
* **Use this to override some texts/copy within the embed.**
* Current options are as follows:

```text theme={null}
{
  customTexts: {
    mainButtonTitle: "Purchase via Helio",
    payButtonTitle: "Click to pay",
  }
}
```

* `theme` (optional)

Use this to **override theming options within the embed.**

* `themeMode` ((use this to switch between light or dark appearances):
* **values:** `light` or `dark`

**Example usage:**

```text theme={null}
{
    paylinkId: "6571e7cd4a2bee1095ee84da",
    theme: {
        themeMode: "dark", // or "light"
    }
}
```

* `primaryColor` (optional, required when `neutralColor` is defined)
  * Use this to customise main colours within the embed
* `neutralColor` (optional, required when `primaryColor` is defined)
  * Use this to customise neutral colours such as border and text colours within the embed

**Example usage:**

```text theme={null}
{
    paylinkId: "6571e7cd4a2bee1095ee84da",
    primaryColor: "#E60000",
    neutralColor: "#5A6578"
}
```

* `backgroundColor` (optional, use this to change the background color)
  * values: Provide a `hex code` (e.g., #FFFFFF for white or #000000 for black)

**Example usage:**

```text theme={null}
{
    paylinkId: "6571e7cd4a2bee1095ee84da",
    backgroundColor: "#4bbe7c"
}
```

* showPayWithCard (optional - default is `true`)
  * Use this to remove the 'Pay with card' button from the embed.
  * values: `true`or `false`

**Example usage:**

```text theme={null}
{
    paylinkId: "6571e7cd4a2bee1095ee84da",
    showPayWithCard: false
}
```

## Dynamic config options

If you have a dynamic payment (to programatically set the amount a) then you will need to use these options:

* Log in to MoonPay Commerce and select CREATE PAYMENT -> Dynamic pricing -> paylinkId
* `amount` (required for dynamic payments)
  * values: a string value
  * example: `amount: "5.99"`
  * This will be the amount **of the payment currency**
* Use step 2 of the Pay link creation process on [moonpay.hel.io](https://moonpay.hel.io/) to set the currencies you will receive in.

## Callback config options

Use our callbacks to run Javascript code when certain actions occur.

You can use these to trigger changes in your application.

* `onSuccess`
* `onError`
* `onPending`
* `onCancel`
* `onStartPayment`

**Example:**

```text theme={null}
{
  // ... (your other config options) ...
  onSuccess: event => console.log(event),
  onError: event => console.log(event),
  onPending: event => console.log(event),
  onCancel: () => console.log("Cancelled payment"),
  onStartPayment: () => console.log("Starting payment"),
}
```

In addition, we recommend using [our webhooks](/reference/webhook/overview#/) to verify transaction on your backend. You can find an end-to-end developer example here including the Checkout Widget and webhooks here:

<Info>
  ### [MoonPay Commerce Checkout Embed Widget](https://embed.hel.io/)
</Info>

## Advanced Config Options:

* `debug`(optional - default is `false`)
  * `true` or `false`
  * example: `debug: true`
  * if true then it will output some helpful debug information

### AdditionalJSON

* `additionalJSON` (optional)
  * values can be any valid JSON data.
  * example: `additionalJSON: {customerId: "customer1", product: "T-shirt"}`
  * Anything you pass in here will get stored when a customer makes a transaction.
  * You can retrieve this on transactions by listening for our [webhooks](/reference/webhook/overview#/), which include all relevant values

<Info>
  **IMPORTANT:** Phantom requires domain allowlisting for the checkout widget to avoid transaction safety warnings. Fill this [form](https://docs.google.com/forms/d/e/1FAIpQLSeoSDtQc9CEHG-dC2EUO6ZkDCaFQXq3M92M1csH4WrdCCW-QQ/viewform) for allowlisting.
</Info>

# Our Network Options for Testnet

When you generate a Pay Link on [app.dev.hel.io](app.dev.hel.io) (for test transactions), then you must set `network: "test"` in your config.

<Info>
  If you generate your Pay [moonpay.hel.io](https://moonpay.hel.io/) (mainnet) you do not need to set `network` config options!
</Info>

(You cannot set `network: "test"` for a Pay Link generated on [moonpay.hel.io](https://moonpay.hel.io/))

The testnets that we use for each blockchain are described below:

* **Solana:**
  * `main` = mainnet
  * `test` = devnet
* **Ethereum**
  * `main` = mainnet
  * `test`= Sepolia
* **Polygon**
  * `main` = mainnet
  * `test` = Mumbai
* **Bitcoin**
  * `main` = mainnet
  * `test` = testnet3
* **Base**
  * `main` = Mainnet
  * `test` = Sepolia

# Supported Currencies

View our [API reference](/reference/currency/list#/) to get a list of all currencies supported.

# Embedding the MoonPay Commerce Checkout Widget in Framer (Alpha)

<Warning>
  ### **Alpha Notice**

  This feature is currently in **alpha** and intended for testing and early feedback. It may be unstable, incomplete, or change without notice.
</Warning>

You can add the MoonPay Commerce checkout widget to any Framer project using a simple code snippet.

In **Framer**, open the **Assets** panel, go to **Code → New Code File -> New Component**, and paste the snippet below into the editor. Name your component **(e.g. MoonPay CommerceCheckout)**, then drag it onto the canvas like any other element. You can enter your **pay link ID** and other widget configuration options in the **right-hand properties panel**, the widget will load automatically.

<CodeGroup>
  ```bash TypeScript theme={null}
  // Framer metadata: defines how this component behaves in layout
  // - Width is fixed (manually set in Framer)
  // - Height adapts to content
  // - Intrinsic size fallback if unset
  // @framerSupportedLayoutWidth fixed
  // @framerSupportedLayoutHeight auto
  // @framerIntrinsicWidth 400
  // @framerIntrinsicHeight 600

  import { useEffect, useRef, useState } from "react"
  import { addPropertyControls, ControlType } from "framer"

  // Props accepted from the Framer UI (sidebar)
  interface Props {
      paylinkId: string // User-defined Paylink ID from MoonPay Commerce
  }

  // Declare a global `window.helioCheckout` interface to avoid TypeScript errors
  declare global {
      interface Window {
          helioCheckout: (element: HTMLElement, config: any) => void
      }
  }

  // Main React component exported to Framer
  export default function MoonPayCheckout({
      paylinkId = "66327978b90031d7202d38cd", // default demo Paylink
  }: Props) {
      // Used just to differentiate instances for debugging
      const [id] = useState(() => Math.random())
      console.log({ id })

      // Reference to the div where the MoonPay widget will mount
      const containerRef = useRef<HTMLDivElement>(null)

      // Local loading/error state
      const [isLoading, setIsLoading] = useState(true)
      const [error, setError] = useState<string | null>(null)

      // Effect hook: inject MoonPay’s script and initialize the widget
      useEffect(() => {
          // Guard against non-browser environments or missing ref
          if (!containerRef.current || typeof window === "undefined") return

          // Create and configure <script> tag to load MoonPay's embed script
          const script = document.createElement("script")
          script.type = "module"
          script.crossOrigin = "anonymous"
          script.src = "https://embed.hel.io/assets/index-v1.js"

          // Once script is loaded, initialize the checkout widget
          script.onload = () => {
              if (window.helioCheckout && containerRef.current) {
                  window.helioCheckout(containerRef.current, {
                      paylinkId, // The configured paylink from Framer
                      display: "button", // Display mode (can be "button", "new-tab" or "inline")
                      theme: {
                          themeMode: "dark", // Force dark theme
                      },
                  })
                  setIsLoading(false) // Done loading
              }
          }

          // Handle error if the script fails to load
          script.onerror = () => {
              setError("Failed to load MoonPay script")
              setIsLoading(false)
          }

          // Inject the script into the page
          document.head.appendChild(script)

          // Cleanup on component unmount
          return () => {
              if (containerRef.current) {
                  containerRef.current.innerHTML = ""
              }
          }
      }, [paylinkId]) // Re-run if paylinkId changes

      // Render error state if script failed
      if (error) {
          return (
              <div className="hel-flex hel-items-center hel-justify-center hel-h-full hel-p-4">
                  <div className="hel-text-red-500">{error}</div>
              </div>
          )
      }

      // Render the widget container and loading state
      return (
          <div className="hel-w-full hel-h-full hel-relative">
              {/* Show loading message until widget loads */}
              {isLoading && (
                  <div className="hel-absolute hel-inset-0 hel-flex hel-items-center hel-justify-center">
                      <div className="hel-text-gray-500">
                          Loading MoonPay Checkout...
                      </div>
                  </div>
              )}
              {/* Mount MoonPay widget here */}
              <div
                  ref={containerRef}
                  id="moonPayCheckoutContainer"
                  className="hel-w-full hel-h-full"
              />
          </div>
      )
  }

  // Expose Paylink ID to the Framer UI sidebar
  addPropertyControls(MoonPayCheckout, {
      paylinkId: {
          type: ControlType.String,
          title: "Paylink ID",
          defaultValue: "66327978b90031d7202d38cd", // Default/fallback Paylink
      },
  })
  ```
</CodeGroup>

# Stripe
Source: https://docs.hel.io/docs/stripe

MoonPay Commerce lets you manage on-chain payments through Stripe

You can use MoonPay Commerce alongside Stripe to manage on-chain payments for one-time payments and invoices.

## How It Works

Within Stripe, you can use a Restricted API key to mark invoices as paid when payments occur on-chain. This ensures that all on-chain payments are properly reflected in the Stripe dashboard, allowing you to view and manage your full payment history in one place.

This Restricted API Key allows us to:

* Link your Stripe account and enable Stripe functionality on MoonPay Commerce Pay Links
* Reference Stripe invoices and create charges using Invoice IDs
* Have completed crypto payments automatically reflected in the Stripe Dashboard

## How to Get Started

1. **Set up Stripe**

* Create a Stripe account, if you don’t already have one.
* Navigate to **Developers → API Keys** in the Stripe Dashboard and click **Create restricted key**.
* Select the option **“Providing this key to another website.”**
* Enter a name for the key (e.g., MoonPay Commerce) and click **Create key**.

2. **Set up the Integration in MoonPay Commerce**

* In the MoonPay Commerce Dashboard, go to **Settings → Integrations**.
* Enter the Stripe Restricted API Key you generated and assign it a name.

<img alt="" />

3. **Create a Stripe-Enabled Pay Link in MoonPay Commerce**

* In the **MoonPay Commerce Dashboard**, create a new **Pay Link**. Make sure the Pay Link is set up as a **one-time payment** (not a subscription) and configured as [**dynamic**](https://docs.hel.io/docs/for-developers#payment-integration-options).
* In **Step 2: Advanced**, enable Stripe functionality and select the Restricted Key you configured.

<img alt="" />

4. **Create an unpaid invoice (same currency as the MoonPay Commerce Pay Link) within the Stripe.**

* Within Stripe, create an unpaid invoice in the same currency as the MoonPay Commerce Pay Link. This can be done either via the Stripe API using this [endpoint](https://docs.stripe.com/api/invoices/object) or directly within the Dashboard.

<img alt="" />

5. **Create a charge using the Stripe Invoice ID, the Invoice ID can be retrieved from the Stripe Dashboard**

* Retrieve the Invoice ID from the Stripe Dashboard.

<img alt="" />

* Use the [Create a Charge endpoint](https://docs.hel.io/reference/charge/create) with the following request:

<CodeGroup>
  ```bash JSON theme={null}
  {
      "paymentRequestId": "689d87f67fe752dc0d274d0e", 
      "stripePaymentDetails": {
          "invoiceId": "in_1RvvbyRrrfLyKJ52a3DSMF5c"
      }
  } 
  ```
</CodeGroup>

6. **Track Payment in Stripe**

Once the customer completes the transaction, the invoice will be reflected as **'Paid'** in the Stripe Dashboard.

<img alt="" />

***

# Solana Pay - Shopify plugin
Source: https://docs.hel.io/docs/solana-pay-shopify-plugin

Accept digital payments on your Shopify store

Easily integrate Solana Pay into your Shopify store:

* Accept stablecoins (USDC, USDT, EURC), SOL, BTC, ETH, and thousands of digital assets
* Get real-time global payouts with low fees
* Eliminate disputes, payments are irreversible, removing chargebacks
* Engage customers with airdrops and token-gated store access
* Auto-convert crypto earnings to your bank or receive stablecoins, reducing market volatility exposure

<iframe title="YouTube video player" />

# Get Started

1. **Install the App** - Visit the [Shopify App Store](https://apps.shopify.com/solana-pay-helio) and click Install
2. **Log in to Shopify** – Access your Shopify [merchant dashboard]() and follow these steps:

* **Terms & Conditions** – Review and accept the Privacy Policy and Terms of Service
* **Business Information**– Complete the KYB process (real-time, up to 48 hours). If delayed, contact [solanapay@hel.io](mailto:solanapay@hel.io)
* **Wallet Setup** – Enter a unique Solana wallet address (must not be linked to another MoonPay Commerce account)

3. **Activate Solana Pay** – Click **Activate Now**, or go to **Payment Settings** in Shopify Admin, and select **Activate**

<iframe title="YouTube video player" />

# View payments

Access all crypto payments on the Payments page in the Merchant Portal. Each payment links to a Shopify order and shows its current status:

* **Rejected:** Payment was not completed
* **Paid:** Payment detected on the Solana blockchain
* **Completed:** Payment confirmed and acknowledged by Shopify, typically updating within seconds of payment confirmation

# Refunds

1. In Shopify Admin, go to the **Orders** page & initiate refund
2. Open **Solana Pay** and navigate to the **Refunds** page
3. Click **Approve** to process a refund or **Deny** to decline it
4. Connect any Solana wallet to confirm the transaction
5. The refund is processed in seconds, and the order status updates in Shopify

**Important:** if your transaction is on not on the Solana chain, please manually refund the customer by copying their wallet address and directly sending the refund amount from your wallet

<iframe title="YouTube video player" />

# Enabling multiple blockchains

After completing the initial app setup, you can enable additional blockchain networks - Bitcoin, Ethereum, Polygon and Base. Note that while our platform fees remain consistent across all chains, network gas fees will vary depending on the blockchain and its level of congestion.

**To enable multi-chain functionality, follow these steps:**

1. **Login to Shopify:**
2. **Edit Your Shopify Pay Link**

* In the MoonPay Commerce Dashboard, go to **Pay Links** → **Edit Shopify Paylink**

3. **Enable Additional Networks**

* In Step 2 of the Pay Link edit, check the box next to the blockchains you want to activate **(Ethereum, Bitcoin, etc.)**
* You’ll be prompted to link a wallet of the respective chain to receive payments

4. **Save Your Changes**

* Click **Next**, then **Save** to apply the new settings

<iframe title="YouTube video player" />

**Add an external Wallet to receive payouts**

* If you prefer to receive payouts in an external wallet, such as a BTC or ETH account on a centralised exchange, you can add an external wallet. Navigate to **Settings -> Manage Wallets**.
* Link your Ethereum, Polygon, or Bitcoin wallets depending on the chains you wish to enable.

Once you've completed these steps, multi-chain payments will be enabled, allowing you to accept transactions from multiple blockchain networks.

# Advanced options

Log in to the MoonPay Commerce dashboard from the [Merchant tab](https://merchant.solanapay.hel.io/merchant) to access these features:

## Payment tokens

Payments settle in USDC by default. Token swaps are auto-enabled, allowing customers to pay with any Solana token while you receive USDC

* To limit accepted tokens, go to **Pay Links -> Edit -> Step 2**, disable swaps, and select your preferred [pricing options](/docs/pricing-fees#/).

<iframe title="YouTube video player" />

## Wallet Management

* Link a wallet under **Settings -> Manage Wallets** for direct dashboard login via [moonpay.hel.io](https://moonpay.hel.io/dashboard)
* To change your Solana Pay wallet, go to **Pay Links -> Edit Shopify Pay link -> Step 2 -> Change payout wallet**

<iframe title="YouTube video player" />

## Helio API

* Use the [API](/reference/retrieve-your-api-keys-from-the-dashboard#/) for webhooks and integrations
* Access "ShopifyPaymentGid" via the API; ensure you’ve linked a wallet in **Settings**
* For more details on Shopify webhooks, click [here](/reference/webhook/shopify#/)

**Loyalty Features:**

* Offer discounts with [Solana NFTs](/docs/discounts#/nftcnft-discounts)
* Add [Discord memberships](/docs/discord-memberships#/)
* Set ["Access Controls"](/docs/gated-payments#/) with NFT gating or wallet allowlisting

<iframe title="YouTube video player" />

# Additional Information

**Wallets and Payouts:** Use any Solana wallet (e.g., Phantom, Solflare, Ledger, Coinbase). Change your payout wallet anytime from the MoonPay Commerce dashboard. For auto off-ramping USDC to your bank via Iron.xyz, contact Helio.

**Supported Currencies:** Hundreds of cryptocurrencies supported, with USDC as the default. Change your settlement currency via the MoonPay Commerce dashboard. Built-in swaps (via Jupiter) allow purchases in preferred tokens.

**Custody:** MoonPay Commerce doesn’t custody funds; all transactions are peer-to-peer on blockchain.

**Settlement & Refund Wallets:** Different wallets are allowed. Refunds require self-custody wallets (e.g., Phantom, Solflare); custodial accounts aren’t supported directly in Shopify UI.

**Support:** Email [solanapay@hel.io](mailto:solanapay@hel.io)

# Split Payments
Source: https://docs.hel.io/docs/split-payments

Receive payment across multiple wallet addresses

Split incoming payments in real-time across different, multiple wallets. This is useful if you want to receive money in another wallet for example a custodial wallet on an exchange, or a multi-sig wallet that you share with your team members.

It also allows you to share revenue in real-time with multiple recipients, for example in the case of creator royalties, fee splits or affiliate links. Funds are split in real-time and settle instantly to the relevant wallets.

# How to set up split payments?

<Frame>
  <img alt="" />
</Frame>

<Info>
  Split Payments are available for single payments on all supported chains. You can split payments up to 5 wallets
</Info>

# Important: Split Payments availability

Split payments can no longer be enabled on new Pay Links. If you have an existing Pay Link with split payments already configured, you can continue to edit those split settings. However, split payments cannot be added to a Pay Link that was created without them.

In summary:

* **Creating a new Pay Link:** Split payment options are not available.
* **Editing a Pay Link without split payments:** Split payment settings are not visible and cannot be enabled.
* **Editing a Pay Link with split payments:** You can continue to modify the existing split payment configuration.

# Gated Payments
Source: https://docs.hel.io/docs/gated-payments

Make your sales event exclusive with easy-to-use access controls

Easily "gate" access to your payments by using Raffle Winners, Discord roles, Wallet allowlist, NFT-gating, or an access code. Multiple access controls can be combined within a single Pay Link.

<Frame>
  <img alt="" />
</Frame>

# Discord Role Gating

Limit your sale to a specific Discord role by enabling **Access Control**, selecting **Discord role**, and entering the Server and Role ID(s). You can specify up to 10 roles per Pay Link and set minimum and maximum purchase quantities per unique Discord ID.

<img alt="" />

Customers must sign in with their Discord credentials and verify role membership to make a purchase.

<Info>
  You can also assign a new Discord role upon successful payment using the MoonPay Commerce bot
</Info>

# Wallet allowlist

Choose the Wallet allowlist option and upload a CSV file with two columns: **"publicKey"** (the public wallet address) and **"maxAllowedQuantity"** (the maximum purchase quantity for that wallet). Each wallet can have a different maximum.

<img alt="" />

**Please note:**

* **Duplicate entries:** Only the first occurrence will be used; duplicates are ignored.
* **CSV formatting:** Avoid trailing, empty, or malformed rows; these will fail validation. Check your CSV in a text editor before uploading.
* **Wallet addresses:** Maintain the original case (mixed letters/numbers). Do not convert to all lowercase or uppercase.
* **Dynamic updates:** Update the allowlist via API if needed.
* **BTC sales:** Allowlist either BTC or Ordinals wallet addresses.

**Only wallets on the allowlist can purchase up to their set maximum; others will be restricted.**

# NFT Gated Access

**NFT Gated Access** allows for exclusive access, discounts, and targeting high-value communities. To set up:

1. Go to **Access Control** -> **NFT** and enter the relevant token address.
2. Users will need to verify ownership of the NFT at checkout.

**Finding the Token Address:** Use a block explorer like Solscan or Polyscan to locate the collection. Copy the **Token Address** (Solana) or **Contract Address** (Ethereum/Polygon) from the top right and paste it into the MoonPay Commerce dashboard.

<img alt="" />

# Access Code

A simple, friendly way to share an exclusive sales with your community, keep the unwanted at bay and create FOMO. Share your Pay Link anywhere but guess what? You'll need the code to get access.

# Raffle Winners

Set up a raffle on your Pay Link to give a large audience an equal chance to join your main sales event. Buyers enter with their wallet and Discord (1 entry per Discord). Enable Discord gating to target a specific community if needed. Winners are randomly selected, notified via email, and allowlisted for the sale. The Pay Link auto-switches to the main sales event once the raffle ends. Download a list of entrants and winners from **Dashboard -> Pay Links -> Raffle download**.

<Frame>
  <img alt="" />
</Frame>

# Discounts
Source: https://docs.hel.io/docs/discounts

Enable discounts via codes or NFTs

# Codes

To set up discounts, go to MoonPay Commerce Dashboard → Create Payment → Advanced → Discounts to define up to 100 discount codes per Pay Link. Enter each discount level and code; users can apply the code at checkout.

<img alt="" />

# NFT Discounts

Enable discounts for holders of specific NFT collections as loyalty rewards. Enter the token address and set a discount level (up to 10 NFTs per payment).

Merchants on MoonPay Commerce or Solana Pay for Shopify can automatically offer discounts to Solana Mobile users with one click. If the user’s wallet holds an NFT from the specified collection, the discount is applied at checkout.

<Frame>
  <img alt="" />
</Frame>

<Info>
  We support NFT discounts on Solana, but not Ethereum. You can still use EVM addresses for gating.
</Info>

## How to find the token address?

Go to the blockchain explorer like [Solscan](https://solscan.io/) to search for the relevant NFT collection and click on any NFT. Note: the Token Address of **ANY** NFT in the collection works.

Copy the Token Address and paste it into the token address field in the MoonPay Commerce dashboard.

<img alt="" />

# SDK
Source: https://docs.hel.io/docs/helio-sdk

🖥️ Installation guide for our SDK

For a complete list of available methods, types, and configuration options, visit the official packages on NPM:

<Info>
  [Paylinks SDK](https://www.npmjs.com/package/@heliofi/sdk)
</Info>

<Info>
  [Deposits SDK](https://www.npmjs.com/package/@heliofi/deposit-react)
</Info>

<Info>
  Refer to the guide [here](https://docs.hel.io/reference/getting-started#1-create-your-account--get-api-keys) for instructions on generating your API keys.
</Info>

### Import

Import the SDK into your project using ES modules:

<CodeGroup>
  ```bash Package theme={null}
  /** 
   * npm i @heliofi/sdk
   **/

  import {HelioSDK} from '@heliofi/sdk';
  ```
</CodeGroup>

Once you've included the script or package, you're ready to initialise the SDK and start integrating with our suite of cryptocurrency payment solutions.

### Example Usage

Then, import and initialise the SDK in your project, and immediately begin using it — for example, to create a pay link:

<CodeGroup>
  ```bash Typescript theme={null}
  import HelioSDK from '@heliofi/sdk';

  const sdk = new HelioSDK({
    apiKey: 'your-public-api-key',
    secretKey: 'your-secret-key',
    network: 'mainnet', // or 'devnet' (optional, mainnet by default)
  });

  const paylink = await sdk.paylink.create(createPaylinkDto);
  ```
</CodeGroup>

Replace the placeholders with your actual API credentials.

# Webhooks
Source: https://docs.hel.io/docs/webhooks

Getting started with our webhooks

<Info>
  To get started with Webhooks, check out our [API Reference](https://docs.hel.io/reference/webhook/overview) for full details.
</Info>

**Webhooks**

MoonPay Commerce Webhooks allow your backend to listen for real-time payment events and programmatically verify transactions.

**Configuration**

You can create and manage webhooks via the API or the Dashboard (Developers → Webhooks). We support two event types:

* `depositId`: Events related to customer deposits.
* `paylinkId`: Events related to specific checkout links.

**Webhook Scope**

For both event types, you can configure the scope of the notifications:

* Global: Receive events for all IDs associated with your company account.
* Resource-Specific: Receive events only for a specifically defined `depositId` or `paylinkId`.

**Monitoring & Retries**

The Dashboard provides full visibility into your webhook health:

* Event Logs: View triggered events, delivery statuses, and timestamps.
* Retry Logic: We automatically attempt redelivery up to 12 times.
* Manual Replay: If the automatic retry limit is reached, you can manually trigger a replay from the event log.

<img alt="" />

# Devnet
Source: https://docs.hel.io/docs/test-helio-on-devnet

Useful for testing various Web3 use cases

To test MoonPay Commerce Links, Checkout Widget, API, or other workflows without real funds:

1. Log into MoonPay Commerce on Solana Devnet, Polygon, Base or Ethereum Sepolia at [moonpay.dev.hel.io](https://moonpay.dev.hel.io/).
2. Use a wallet like Phantom or MetaMask.
3. Connect your wallet to the relevant network under **Settings -> Developer Settings**.
4. Click **CREATE PAYMENT** to start.
5. Obtain test tokens (e.g., [SOL faucet](https://solfaucet.com/) , [USDC faucet](https://faucet.circle.com/), etc) for testing

# Autofill User Data
Source: https://docs.hel.io/docs/autofill-user-data

Pass and autofill user parameters directly to MoonPay Commerce checkout pages

Passing parameters helps developers auto-fill MoonPay Commerce checkout pages from other data sources like Discord, customer forms, etc. to offer a better user experience.

Simply pass through the parameters and values in the format and the Pay Link page will populate those fields with the values posted.

# Example Pay Link URL with Parameters

**Standard Pay Link:**

```text theme={null}
https://www.hel.io/x/zebulivelondonVIP
```

**Pay Link with Parameters:**

```text theme={null}
https://www.hel.io/x/zebulivelondonVIP?email=jane%40hel.io&fullName=Jane+Smith&twitterUsername=%40janesmith&streetNumber=1&street=Acacia+Avenue&deliveryAddress=Townsville&city=Bigtown&state=South&areaCode=W1+1AA&phoneNumber=07973999999&productValue=M&network=POLYGON
```

# Parameters and Values Available

| Parameter        | Value                | Description                                                                                        |
| ---------------- | -------------------- | -------------------------------------------------------------------------------------------------- |
| email=           | Email Address        | A valid email address is required                                                                  |
| twitterUsername= | Twitter Username     | Standard Twitter name required with @                                                              |
| fullName=        | Full Username        | Real name of a customer                                                                            |
| streetNumber=    | Street Number        | Street number of a property                                                                        |
| street=          | Street Name          | Street Name                                                                                        |
| deliveryAddress= | Optional Street Name | Optional Street Name                                                                               |
| city=            | City Name            | City Name                                                                                          |
| state=           | State Name           | State or Region Name                                                                               |
| areaCode=        | Area Code            | Area or Postal Code                                                                                |
| phoneNumber=     | Phone Number         | Phone Number in local format                                                                       |
| productValue=    | Phone Number         | Set using 'Additional Information' setting in pay link setup to capture custom data like shoe size |
| network=         | Customer             | Blockchain of choice                                                                               |

Adding the values will populate the Pay Link page as follows

<img alt="" />

# Google App Script
Source: https://docs.hel.io/docs/google-app-script

Add MoonPay Commerce transactions to your Google Sheets using OUR API

<Info>
  You need to generate an [API key](/reference/retrieve-your-api-keys-from-the-dashboard#/) in the [dashboard](https://app.hel.io/) for Google Sheets integration. See our API reference for instructions. Alternatively, you can manually export your Helio transactions as a .csv file from the dashboard.
</Info>

**Script version: v0.2.6**

Please test with a new Google Sheet when upgrading the script to avoid data duplication due to new columns.

# Get Started

* **Create a Google Sheet**
  * Open a new sheet.
  * Go to Extensions -> App Script.
* **Add the script**
  * In the text editor, pictured below, connect your Google account if prompted.

<Frame>
  <img alt="" />
</Frame>

* Copy and paste the provided script code, replacing the starter `myFunction`.

<CodeGroup>
  ```bash JavaScript theme={null}
  /*
  HELIO SHEETS INTEGRATION v0.2.6
  AUTHOR: [email protected]
  HOW TO USE:
  Add your...
  HELIO_API_KEY (Get this from the Helio Dash | Settings | API | Secret API Key)
  PUBLIC_KEY (Get this from the Helio Dash | Settings | API | Public API Key)
  Then select the main function at the top and press Run!
  HOW IT WORKS: This script gets your recent Helio transactions filtered aafter the 
  specified date, checks if they are not already on the sheet and then appends the
  data below the headers, sorting by most recently purchased.
  */
  // Add your values here

  const PUBLIC_KEY = "";
  const HELIO_API_KEY = "";
  const FILTER_DATE = new Date("2024-09-15T00:00:00Z"); // Set this to your desired start date
  const HEADERS = [
    'Time Purchased (UTC)',
    'Time stopped',
    'Total time charged',
    'Sender',
    'Product',
    'Quantity',
    'Paid',
    'Currency',
    'Payment Link',
    'Payment Link (Short)',
    'SolScan URL',
    'Transaction ID',
    'E-mail Address',
    'Twitter Username',
    'Discord Username',
    'Phone Number',
    'Name',
    'Street Number',
    'Street',
    'Delivery Address',
    'City',
    'Area Code',
    'State',
    'Country',
    'Additional Info',
  ];

  function main() {
    const helioTransactions = getRecentTransactions(HELIO_API_KEY, PUBLIC_KEY);
    if (helioTransactions != null) {
      console.log('RECEIVED: Transaction data');
      const filteredTransactions = filterTransactions(helioTransactions, FILTER_DATE);
      if (filteredTransactions.length > 0) {
        writeNewTransactions(filteredTransactions, HEADERS);
      } else {
        console.log('No new transactions to add after the specified date');
      }
    } else {
      throw new Error('ERROR: could not get helio transactions');
    }
  }

  function getRecentTransactions(API_KEY, PK) {
    try {
      const response = UrlFetchApp.fetch('https://api.hel.io/v1/export/payments?publicKey='+PK, {
        method: 'get',
        headers: {
          'Authorization': 'Bearer '+ API_KEY,
        }
      });
      if (response.getResponseCode() == 200) {
        return JSON.parse(response.getContentText());
      }
    } catch (e) {
      console.log(e);
    }
  }

  function filterTransactions(helioTransactions, filterDate) {
    var sheet = SpreadsheetApp.getActiveSheet();
    const existingTransactionIDs = getColumn(sheet, 12); 
    
    return helioTransactions.filter(transaction => {
      const transactionDate = new Date(transaction.time);
      return transactionDate >= filterDate && !existingTransactionIDs.includes(transaction.id);
    });
  }

  function writeNewTransactions(newTransactions, headers) {
    var sheet = SpreadsheetApp.getActiveSheet();
    
    // Ensure headers are present and correct
    const firstRow = sheet.getRange(1, 1, 1, headers.length);
    const firstRowValues = firstRow.getValues()[0];
    if (!arraysEqual(headers, firstRowValues)) {
      firstRow.setValues([headers]);
      firstRow.setFontWeight("bold");
    }
    
    // Prepare the data for batch insert
    const newData = newTransactions.map(item => [
      item.active ? `Live (${item.time})` : item.time,
      item.active || !item.cancelAt ? '' : item.cancelDate,
      item.timeCharged,
      item.from,
      item.paymentRequestName,
      item.quantity ?? 1,
      item.convertedAmount + " " + item.currency,
      item.currency,
      item.paymentRequestUrl,
      item.paymentRequestUrlWithSlug ?? '',
      item.solScanLink,
      item.id,
      item.email,
      item.twitterUsername,
      item.discordUsername,
      item.phoneNumber,
      item.fullName ?? '',
      item.streetNumber ? item.streetNumber.replace(',', ';') : '',
      item.street ? item.street.replace(',', ';') : '',
      item.deliveryAddress ? item.deliveryAddress.replace(',', ';') : '',
      item.city ? item.city.replace(',', ';') : '',
      item.areaCode ? item.areaCode.replace(',', ';') : '',
      item.state ? item.state.replace(',', ';') : '',
      item.country,
      item.value && item.name ? `${item.value.replace(',', ';')} (${item.name})` : ''
    ]);

    // Insert all new transactions at once
    if (newData.length > 0) {
      sheet.getRange(2, 1, newData.length, headers.length).insertCells(SpreadsheetApp.Dimension.ROWS);
      sheet.getRange(2, 1, newData.length, headers.length).setValues(newData);
      console.log(`ADDED ${newData.length} NEW TRANSACTIONS`);
    }
    
    SpreadsheetApp.flush();
  }

  function arraysEqual(a, b) {
    if (a === b) return true;
    if (a == null || b == null) return false;
    if (a.length !== b.length) return false;
    for (var i = 0; i < a.length; ++i) {
      if (a[i] !== b[i]) return false;
    }
    return true;
  }

  function getColumn(activeSheet, columnIndex) {
    return activeSheet.getRange(1, columnIndex)
      .getDataRegion(SpreadsheetApp.Dimension.ROWS)
      .getValues()
      .flat();
  }
  ```
</CodeGroup>

<Info>
  Developers can customise headers and columns.
</Info>

<img alt="" />

* **Save and Run**
  * Click the save icon or press `Ctrl+S`.
  * Select the `main` function from the dropdown next to `Debug` if you're running an old version.
  * Press `Run`. Approve any Google permissions if prompted.
* **Verify**
  * If successful, your transactions will appear in the Google Sheet.

<img alt="" />

<Info>
  **Optional:** Customise the sheet (e.g., hide columns, change header names), but avoid altering the order of columns.
</Info>

# Add Automation to Your Google Sheets

* **Open Triggers**
  * In the Google App Script tab, click the clock icon Triggers in the left menu.
* **Set Up a Trigger**
  * Click Add `Trigger`.
  * Configure the following:
    * **Function to Run:** Select Main.
    * **Deployment:** Select Head.
    * **Event Source:** Choose Time-driven.
    * **Type and Interval:** Select an internal (e.g., every 30 minutes or 1 hour).

<img alt="" />

<Info>
  For assistance, visit our [Discord](https://discord.gg/helio) support channel.
</Info>

# Getting Started
Source: https://docs.hel.io/reference/getting-started

Use the API to create payments and track transactions

# Pre-requisites

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

In order to perform actions using our API, you need to complete the following steps.

## 1. Create your Account & get API keys

* Go to our [dashboard](https://moonpay.hel.io/)   and log in.
* Under **Developer -> API**, check **Enable** to generate your Public and Secret API Keys.
* Save these securely, as the Secret API Key won't be retrievable later (you can regenerate both if needed).

![](https://files.readme.io/b18753d4ca4cf14167cb84b833e2cc8743fbfa89ed5a86cddc330b27ed97c468-Screenshot_2026-02-03_at_12.54.50.png)

# Prepare Request Payload for paylinkId

When creating a [Pay Link via API](https://docs.hel.io/reference/paylink/overview), you'll need to specify the recipient wallet, payment currency, and accepted recipient currencies — so it's important to gather this information beforehand. Here's how to do it.

```json JSON theme={null}
"recipients": [
    {
      "walletId": "YOUR_WALLET_ID",
      "currencyId": "6340313846e4f91b8abc519b"
    }
  ]
```

## 1. Retrieving your Wallet ID

You can retrieve your Wallet ID in one of the following ways:

### Option 1: Via the Dashboard

* Navigate to the [Helio Dashboard](https://app.hel.io/)
* Go to **Settings → Wallets**
* Click the three dots next to your wallet and select **Copy wallet ID**

<Frame>
  ![](https://files.readme.io/1778d12a287b3081287ef4a1ae534b0ae73a50b8cb808e5a30db7032da2ea444-Screenshot_2026-02-03_at_12.52.36.jpg)
</Frame>

<Info>
  **Note:** The Helio ID is different from your wallet's public key.
</Info>

### Option 2: Via the API

* Call the [Get wallets](https://docs.hel.io/reference/wallet/list) endpoint
* Use the `id` field from the wallet object returned in the response

## 2. Retrieving the Currency Id

To retrieve the `currencyId` use our Get Currency endpoint [here](/reference/currency/list).

# Get Wallets
Source: https://docs.hel.io/reference/wallet/list

GET /v1/wallet/all
Returns all wallets linked to a merchant, including both connected and payout wallets, across supported blockchain networks.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Get Pay Link Currencies
Source: https://docs.hel.io/reference/currency/list

GET /v1/currency/all
Returns a complete list of all supported currencies on Helio, including fiat and crypto. Use this to retrieve currency IDs for Pay Link creation.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Get Deposit Currencies
Source: https://docs.hel.io/reference/currency/list-deposit

GET /v1/currency/deposit
Returns a complete list of all supported deposit currencies on MoonPay Commerce, including fiat and crypto. Use this to retrieve currency IDs for deposit creation.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Overview
Source: https://docs.hel.io/reference/paylink/overview

Pay Link API creation request body and full options reference

When creating a Pay Link via API the following request body is required

```json theme={null}
{
  "template": "OTHER",
  "name": "Your paylink name here",
  "price": "1000000", /* price is int64 represented by the base units of each currency, e.g. "price": "1000000" = 1 USDC*/
  "pricingCurrency": "6340313846e4f91b8abc519b", /* currency ID to price it in - can be a fiat currency */
  "features": {}, /* this must be set, even if empty */
  "recipients": [
    {
      "walletId": "YOUR_WALLET_ID",
      "currencyId": "6340313846e4f91b8abc519b"
    }
  ]
}
```

* Configure multiple recipients and currencies if needed. The recipient currency can differ from the pricing currency. You can retrieve the `currencyId` from [this endpoint](/reference/currency/list), and see [here](https://docs.hel.io/reference/getting-started#1-retrieving-your-wallet-id) for how to retrieve your `walletId`.
  * For instance, you could price the link in EUR (e.g., €5) while accepting USDC or USDT as recipient currencies.

### Example Query

```shell theme={null}
curl --location 'https://api.hel.io/v1/paylink/create/api-key?apiKey=<YOUR_PUBLIC_API_KEY>' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_SECRET_API_KEY' \
--data '{
    "name": "Paylink Name Example",
    "description": "Paylink Description Example",
    "pricingCurrency": "6340313846e4f91b8abc519b",
    "currency": "SOL",
    "recipients": [
        {
            "currencyId": "6340313846e4f91b8abc519b",
            "walletId": "YOUR_WALLET_ID"
        }
    ],
  "price": "1",
  "features": {}
}'
```

<Info>
  **Note**: In this basic example, pricingCurrency and currencyId are the same, but they don't have to be. For example, you can price the Pay Link in USDC and receive SOL — Helio handles the conversions on your behalf.
</Info>

### Full Request Body Options for Pay Link Creation

For advanced use cases, here is the full list of possible request body options.

```json theme={null}
{
   name: string; /* set the pay link name */

   features: {
     requireEmail?: boolean; /* require buyer to submit an email */
     requireDiscordUsername?: boolean; /* require buyer to submit an email */
     requireDiscordLogin?: boolean; /* require buyer to login with discord */
     requireFullName?: boolean; /* require buyer to enter their full name */
     requireTwitterUsername?: boolean; /* require buyer to enter their X username */
     requireCountry?: boolean; /* require buyer to enter their country */
     requireDeliveryAddress?: boolean; /* require buyer to enter their X username */
     requirePhoneNumber?: boolean; /* require buyer to enter their X username */
     requireProductDetails?: boolean; /* require additioanal details from the buyer */
     requireMaxTransactions?: boolean; /* enable a limit on the number of transactions */
     requireNftGate?: boolean; /* require an NFT gate for access */
     requireDiscordAuth?: boolean; /* require buyer to enter their X username */
     requireAccessCode?: boolean; /* require buyer to enter access code to use paylink */
     requireFixedCurrency?: boolean; /* restrict transactions to a fixed currency */
     canSwapTokens?: boolean;  /* enable token swaps on your pay link */
     isHelioPlay?: boolean; /* enable Helio Play functionality */
     isTransparentWallet?: boolean;
     nftDropEnabled?: boolean; /* enable NFT drop functionality */
     allowAffiliate?: boolean; /* enable affiliate commissions */
     enableCountdown?: boolean; /* enable countdown on your pay link */
     isSubscription?: boolean; /* enable subscriptions on your pay link*/
     isEventEnabled?: boolean; /* enable event-related payments */
     canChangeQuantity?: boolean; /* enable users to change quantity on the pay link */
     requireQuantityLimits?: boolean; /* set quantity limits on purchases */
     canChangePrice?: boolean; /* enable users to set their own price */
     isEscrowed?: boolean; /* enable escrow functionality for transactions */
     shouldRedirectOnSuccess?: boolean; /* enable redirecting users after a successful transaction */
     hasRedirectQueryParams: boolean /* enable redirecting with query parameters */
     showDiscountCode?: boolean; /* display a discount code field at checkout */
     requireDiscordQuantityLimit?: boolean; /* enable a quantity limit per discord user */
     requireAllowlist?: boolean; /* enable an allowlist */
     requireAirdrop?: boolean; /* enable a cNFT airdrop */
  	 customThemeEnabled?: boolean; /*enable custom theming on your paylink */
   };

   price?: string; /* set the pay link price */

   pricingCurrency?: string; /* set the currency for the pay link */

   recipients?: { /* set your receipient wallets */
      currencyId: string;
      walletId: string;
   }[];

   description?: string; /* set your paylink description */

   template?: 'PRODUCT' | 'SUBSCRIPTION' | 'PRE_SALE' | 'SINGLE_NFT' | 'VIDEO' | 'DISCORD_MEMBERSHIP' | 'INVOICE' | 'EMBEDDED' | 'LINK_OR_FILE' | 'TRADING_VIEW' | 'EVENT' | 'OTHER' | 'LEGACY';

   normalizedPrice?: string;

   notifySenderByEmail?: boolean = false;  /* Enable email notifications to the buyer */

   notifyReceiverByEmail?: boolean = false; /* enable email notifications to the seller */

   addDiscordRole?: boolean = false; /* assign a discord role after purchase */

   discordRoleIds?: string[]; /* list of Discord role id's to assign */

   disabled?: boolean; /* disable the pay link */

   dynamic?: boolean; /* set the pay link as dynamic or static */

   content?: { /* set the content for your paylink */
     text?: string;
     mediaUrl?: string;
     mediaAttachmentId?: string;
   };

   maxTransactions?: number; /* set the maximum number of transactions allowed on the pay link*/


   product?: { { /* define the additional product details */
     name: string;
     description: string;
     type: 'TEXT' | 'SELECTOR';
   };

   nftCollectionAddress?: string; /* set the nft collection address */

   discordAuthDetails?: { /* configure discord authentication */
     serverId: string; /* discord server id */
     roleId: string; /* discord role id */
   }[];

   nftDrop?: { /* configure NFT drop settings */
     mintAddresses: string[] /* list of mint addresses */
   };

   accessCodeAuthProperties?: { { /* set access code authentication */
     accessCode: string;
   };

   fixedCurrency?: { /* set fixed currency payment details */
     currency: string;
     price: number;
   };

   tradingViewIndicators?: { /* set your trading view indicators */
     id: string;
     url: string;
     name: string;
   }[];

   affiliateDetails?: { /* set the affiliate percentage for your Pay Link */
     bps: number;
   };

   eventDetails?: { /* set event-specific details */
     datetime: Date;
     location?: string;
   };

   countdownDetails?: { /* set start and end time of your pay link */
     startDatetime: Date;
     endDatetime?: Date;
   };
   
   subscriptionDetails: { /* set the details of your subscription  */
    renewalReminders: 0, /* set how many renewal reminders will be sent  */
    gracePeriod: 0, /* set the grace period once the subscription expires   */
    annualDiscountBps: 0, /* "discount in basis points for an annual subscription." */
    interval: "MONTH" /* set the interval, "MONTH" or "ANNUAL" */
  };

   discountCodes?: { /* set discount codes for your pay link */
     percent: number;
     token: string;
     prId?: string;
     id?: string;
     tokenType: 'CODE' | 'NFT_COLLECTION';
   }[];

   limitSaleType?: 'TRANSACTION' | 'DISCORD_ID'; /* set sale limit type */

   minQuantity?: number; /* set the minimum quantity on your pay link */

   maxQuantity?: number; /* set the maximum quantity on your pay link */

   helioPlayProperties?: { /* set the maximum quantity on your pay link */
     durationSec?: number;
     previewAttachmentId?: string;
     media: {
       type: 'VIDEO';
       hosted: boolean;
     };
   };
   
   redirectUrl?: string; /* set a URL to redirect users to after a successful transaction on your pay link */
   redirectQueryParams?: { queryParamType: string }[]; /* set redirect query param */
   
   airdropDetailsId?: string; /* set an ID for the airdrop details */

	customTheme?: {
    primaryColor: "#FF0000",  /* primary colour */
    neutralColor: "#00FF00", /* neutral colour */
    textColorOnButton: "WHITE", /* button text color: "WHITE" or "BLACK" */
    themeMode: "LIGHT", /* theme mode: "LIGHT" or "DARK" */
    backgroundColor?: "#0000FF" /* background color of the page*/
  }
}
```

### Response Body Example

```json theme={null}
{
  "id": "656de2de971d6c8e978293bf",
  "template": "OTHER",
  "disabled": false,
  "inactive": false,
  "notifySenderByEmail": false,
  "notifyReceiverByEmail": false,
  "addDiscordRole": false,
  "helioPlayProperties": null,
  "features": {
    "canChangeQuantity": false,
    "canChangePrice": false,
    "requireQuantityLimits": false,
    "requireCountry": false,
    "requireEmail": false,
    "requireDeliveryAddress": false,
    "requireDiscordUsername": false,
    "requireDiscordLogin": false,
    "requireFullName": false,
    "requirePhoneNumber": false,
    "requireTwitterUsername": false,
    "requireProductDetails": false,
    "requireMaxTransactions": false,
    "requireNftGate": false,
    "requireDiscordAuth": false,
    "requireAccessCode": false,
    "requireFixedCurrency": false,
    "canSwapTokens": false,
    "isHelioPlay": false,
    "isTransparentWallet": false,
    "nftDropEnabled": false,
    "showDiscountCode": false,
    "isEscrowed": false,
    "requireDiscordQuantityLimit": false,
    "requireAllowlist": false,
    "allowAffiliate": false,
    "requireAirdrop": false,
    "isEventEnabled": false,
    "enableCountdown": false,
    "shouldRedirectOnSuccess": false
  },
  "name": "pay link name",
  "discordAuthDetails": [],
  "dynamic": false,
  "affiliateDetails": null,
  "price": "100000",
  "content": {},
  "creator": {
    "id": "63bfb6f92f9a086a381c4616",
    "email": "",
    "name": "",
    "isDisabled": false,
    "kycVerified": true,
    "helioVerified": true,
    "platformDetails": null
  },
  "company": {
    "id": "63bfb6f92f9a086a381c4618",
    "name": "",
    "email": "",
    "websiteUrl": "",
    "discordUsername": "",
    "address": "",
    "phoneNumber": "",
    "escrowFunds": false,
    "tradingViewDetails": "",
    "twitterUsername": "",
    "twitterConfirmed": true
  },
  "currency": {
    "id": "63430c8348c610068bcdc482",
    "name": "USD Coin",
    "decimals": 6,
    "order": 1,
    "mintAddress": "4zMMC9srt5Ri5X14GAgXhaHii3GnPAEERYPJgZJDncDU",
    "coinMarketCapId": 3408,
    "symbol": "USDC",
    "symbolPrefix": "$",
    "type": "DIGITAL",
    "iconUrl": "USDC.svg",
    "features": ["PAYMENT_PRICING", "PAYMENT_RECIPIENT"],
    "blockchain": {
      "id": "63430c8348c610068bcdc43c",
      "name": "SOL",
      "symbol": "SOL",
      "engine": {
        "id": "63b574b9d07b6f6f21c13eb2",
        "type": "SOL"
      }
    }
  },
  "wallet": {
    "id": "63bfb6f92f9a086a381c4612",
    "publicKey": "9PTAZwj9qeet6bCAai6aoTg1phfgJonBwKvy8btQJMxR",
    "btcProperties": null
  },
  "recipients": [
    {
      "currency": {
        "id": "63430c8348c610068bcdc482",
        "name": "USD Coin",
        "decimals": 6,
        "order": 1,
        "mintAddress": "4zMMC9srt5Ri5X14GAgXhaHii3GnPAEERYPJgZJDncDU",
        "coinMarketCapId": 3408,
        "symbol": "USDC",
        "symbolPrefix": "$",
        "type": "DIGITAL",
        "iconUrl": "USDC.svg",
        "features": ["PAYMENT_PRICING", "PAYMENT_RECIPIENT"],
        "blockchain": {
          "id": "63430c8348c610068bcdc43c",
          "name": "SOL",
          "symbol": "SOL",
          "engine": {
            "id": "63b574b9d07b6f6f21c13eb2",
            "type": "SOL"
          }
        }
      },
      "wallet": {
        "id": "63bfb6f92f9a086a381c4612",
        "publicKey": "9PTAZwj9qeet6bCAai6aoTg1phfgJonBwKvy8btQJMxR",
        "btcProperties": null,
        "blockchainEngine": {
          "id": "63b574b9d07b6f6f21c13eb2",
          "type": "SOL"
        }
      }
    }
  ],
  "volume": 0,
  "sales": "0",
  "product": null,
  "discountCodes": [],
  "discordRoleIds": [],
  "pricingCurrency": {
    "id": "63430c8348c610068bcdc482",
    "name": "USD Coin",
    "decimals": 6,
    "order": 1,
    "mintAddress": "4zMMC9srt5Ri5X14GAgXhaHii3GnPAEERYPJgZJDncDU",
    "coinMarketCapId": 3408,
    "symbol": "USDC",
    "symbolPrefix": "$",
    "type": "DIGITAL",
    "iconUrl": "USDC.svg",
    "features": ["PAYMENT_PRICING", "PAYMENT_RECIPIENT"],
    "blockchain": {
      "id": "63430c8348c610068bcdc43c",
      "name": "SOL",
      "symbol": "SOL",
      "engine": {
        "id": "63b574b9d07b6f6f21c13eb2",
        "type": "SOL"
      }
    }
  },
  "redirectUrl": ""
}
```

# Create a Pay Link
Source: https://docs.hel.io/reference/paylink/create

POST /v1/paylink/create/api-key
Create a new paylink using your API key with full control over pricing, currency, and payout configuration.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Update a Pay Link
Source: https://docs.hel.io/reference/paylink/update

PATCH /v1/paylink/{id}/api-key
Update the details of a paylink.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Disable a Pay Link
Source: https://docs.hel.io/reference/paylink/disable

PATCH /v1/paylink/{id}/disable
Disable an active paylink, preventing any further payments from being made through it.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Get a Pay Links Transactions by ID
Source: https://docs.hel.io/reference/paylink/list-transactions

GET /v1/paylink/{id}/transactions
Retrieve all transactions associated with a specific paylink ID.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Overview
Source: https://docs.hel.io/reference/charge/overview

Create single-use Pay Links and checkout sessions

**Charges** are an extension of Pay Links that let you generate unique, single-use checkout pages from the same `paylinkId`. They're ideal for mobile-first flows, QR codes, deep linking, embedded pay buttons, and custom e-commerce integrations.

**Using the API to create charges you can:**

* Dynamically set the price of each checkout using the `requestAmount` parameter.
* Pass through custom metadata with additionalJSON in the `customerDetails` object.
* Trigger a card-only payment flow by appending `?cardonly=true` to the charge URL.

The following sections show how to include extra fields in your request and how to configure specific flows like card-only payments.

## Using additionalJSON in Your Request:

You can use the additionalJSON field within the customerDetails object to include any extra information you'd like to pass along with your payment request.

**Example Request Body:**

```json theme={null}
{  
  "paymentRequestId": "66c49e24701f6930ee9c77dd",
  "requestAmount": "0.01",
  "prepareRequestBody": {
    "customerDetails": {
      "additionalJSON": "[]"
    }
  }
}
```

**Example Query:**

```curl theme={null}
curl --location 'https://api.hel.io/v1/charge/api-key?apiKey=<YOUR_PUBLIC_API_KEY>' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_SECRET_API_KEY' \
--data '{
    "paymentRequestId": "667974dbb38d45b726751902",
    "requestAmount": "0.2",
    "prepareRequestBody": {
    "customerDetails": {
      "additionalJSON": "[]" # or whatever json you want here.
    }
  }
}'
```

## Trigger Pay with Card via Charge

To trigger the Pay with Card flow directly from a charge page, simply append the query parameter `?cardonly=true` to the end of the charge URL.

This will automatically launch the card payment flow without requiring the user to connect a Web3 wallet, which is useful for streamlining checkout for non-crypto users, enabling faster payments, or setting card as the default in your payment flow.

Example:

```
https://app.hel.io/charge/0f577645-b680-4d0a-8678-6fec0713ff3d?cardonly=true
```

<Frame>
  <img />
</Frame>

# Create a Charge
Source: https://docs.hel.io/reference/charge/create

POST /v1/charge/api-key
Creates a one-time pay link (charge) that can be used to collect a single payment from a customer.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Get a Charge by ID
Source: https://docs.hel.io/reference/charge/retrieve

GET /v1/charge/{chargeId}
Retrieve a one-time charge using its unique identifier, chargeId (e.g., 28936112-bcf1-4240-a851-85fb087c282a). This ID can be found at the end of the URL when the charge is created. If the charge has been paid, transaction details will appear under the paylinkTx field in the response. If no transaction has occurred yet, the field will be returned as "paylinkTx": null.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Create a Deposit
Source: https://docs.hel.io/reference/deposits/create

POST /v1/deposits/create/api-key
Creates a new deposit. A deposit can be configured with optional payment methods (card payments, wallet connect, manual transfer) and notification settings. The request must include exactly one currencyId in the currencyIds array.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Get Deposits
Source: https://docs.hel.io/reference/deposits/search

GET /v1/deposits/search
Retrieve all deposits for the authenticated account. Supports optional filtering by deposit name using the name query parameter. Returns an array of matching deposits.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Update a Deposit
Source: https://docs.hel.io/reference/deposits/update

PATCH /v1/deposits/{depositId}/api-key
Updates a deposit by ID. Only provided fields are modified, allowing changes to name, description, payment options, disabled state, blockchain symbols, and more.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Get All Deposit Transactions
Source: https://docs.hel.io/reference/deposits/list-transactions

GET /v1/transactions/deposit/{depositId}/transactions
Fetch a complete list of transactions linked to a specific deposit, including payment details, status, amounts, and related metadata. Get transactions from the last 7 days by default or use from or to filter.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Get Deposit Transactions by Customer Token
Source: https://docs.hel.io/reference/deposits/list-customer-transactions

GET /v1/transactions/deposit/customer/{depositCustomerToken}/transactions
Get all transactions for a deposit by customer token

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Get a Deposit Transaction by Signature
Source: https://docs.hel.io/reference/deposits/retrieve-transaction-by-signature

GET /v1/transactions/deposit/signature/{signature}
Fetches a deposit transaction using its blockchain transaction signature. Returns the transaction details including deposit, deposit customer, and metadata.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Get a Deposit Customer (by customerId)
Source: https://docs.hel.io/reference/deposits/retrieve-customer

GET /v1/deposits/{depositId}/customer/{customerId}/api-key
Retrieves the customer associated with a specific deposit using the provided depositId and customerId.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Create a Customer for a Deposit
Source: https://docs.hel.io/reference/deposit-customers/create

POST /v1/deposit-customers/api-key
Creates a new customer linked to a specific deposit using the depositId

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Get a Deposit Customer (by Token)
Source: https://docs.hel.io/reference/deposit-customers/retrieve

GET /v1/deposit-customers/{depositCustomerToken}/api-key
Retrieves a customer linked to a specific deposit using the depositCustomerToken.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Update Deposit Customer
Source: https://docs.hel.io/reference/deposit-customers/update

PATCH /v1/deposit-customers/{depositCustomerToken}/api-key
Updates a customer associated with a specific deposit using the depositCustomerToken.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Record Deposit Wallet Activity
Source: https://docs.hel.io/reference/deposit-wallet/record-activity

POST /v1/deposit-wallet/token/{tokenId}/activity
Call this endpoint whenever you display a deposit wallet to a customer. This tells us that the wallet is actively being used, allowing us to temporarily increase balance polling and detect incoming payments more quickly. This improves the payment experience for your customers.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Overview
Source: https://docs.hel.io/reference/webhook/overview

Getting started with our webhooks

<Info>
  For an overview of our Webhooks, view our [Guide](https://docs.hel.io/docs/webhooks). For code samples, explore our [Recipes](https://docs.hel.io/recipes).
</Info>

<Info>
  Webhooks are linked to your MoonPay Commerce account and use a sharedSecret with a Bearer auth header to authenticate endpoints. You can [generate your API key](https://docs.hel.io/reference/retrieve-your-api-keys-from-the-dashboard) in the dashboard. Webhooks are supported for Pay Links on Solana, Ethereum, Base, Polygon, and BTC, as well as Subscriptions on Solana.
</Info>

# Pay Link Webhook Payload Example

Our webhooks include detailed information about the transaction and Pay Link — for regular Pay Links there is the `CREATED` event, and for subscriptions there are the `STARTED`, `RENEWED`, and `ENDED` events.

```json JSON theme={null}
{  // the PaylinkEventPayload object
  "transaction": "...",  // JSON string of the transactionObject below
  "event": "CREATED", // PaylinkEvents enum - matches the webhook event type when creating the webhook
  "transactionObject": {
    "id": "65e1df4d0ce08148bc333b62",  // transaction ID
    "paylinkId": "65dc9f9f1154beaac39976c8", // Paylink ID
		"fee": "1000", // Fee (base units)
    "quantity": 1,
    "createdAt": "2024-03-01T13:59:41.303Z",
    "paymentType": "PAYLINK", // or 'PAYSTREAM'
    "meta": { // the TransactionMeta object
      "id": "65e1df4d0ce08148bc333b60",
      "amount": "9900000", // amount in minimal units (lamport/Sats/Wei)
      "senderPK": "Er3RwfYqCETBTf5RktezXaNDT3zYgwBMftxBYbX8Zk1G", // customer's wallet
      "recipientPK": "Er3RwfYqCETBTf5RktezXaNDT3zYgwBMftxBYbX8Zk1G", // merchant's recipient wallet
      "customerDetails": { 
        "country": "United States",
        "deliveryAddress": "test-address",
        "email": "test@example.com",
        "fullName": "test-full-name",
        "phoneNumber": "+0123123123123",
        "discordUsername": "a11111118100",
        "discordUser": {
          "id": "1234567890", 
          "username": "test-discord-username"
        },
        "twitterUsername": "test-x-username",
        "state": "test-state",
        "street": "test-street",
        "streetNumber": "123",
        "areaCode": "90210",
        "city": "test-city"
        "additionalJSON": "\"{\\\"test\\\": 123}\"" // any additionalJSON will be JSON stringified
      },
      "productDetails": null,
      "transactionSignature": "5AYzruixQiGX8rm279cPLo7bdqaUPYMD8Z3QnBNVz2omZHaUsUKFZRmaV8W7sAHPEyExeHkjquy8mg6LHcNktg5c",
      "transactionStatus": "SUCCESS",
      "splitRevenue": false,
      "remainingAccounts": [],
      "totalAmount": "9900000",
      "affiliateAmount": "0", // Amount sent to affiliate who referred the transaction. This will normally be "0" unless referred by affiliate
      "affiliateCode": "somecode", // Affiliate code used - this will normally be undefined
      "affiliatePublicKey": "Er3RwfYqCETBTf5RktezXaNDT3zYgwBMftxBYbX8Zk1G"; // Public key (wallet address) for affiliate who referred this transaction. This will normally be undefined
      "tokenQuote": {
        "from": "SOL",
        "fromAmountDecimal": "0.01",
        "to": "SOL",
        "toAmountMinimal": "10000000"
      },
      "submitGeolocation": "FR", // ISO 3166-1 alpha-2 country code based on IP address which submitted the transaction to our server
      "currency": {
        "id": "63430c8348c610068bcdc474",
        "blockchain": null
      }
    }
  }
}
```

# Deposit Webhooks

We emit three webhook events for deposits:

* `DEPOSIT_TX_SUBMITTED` - when the transaction is broadcast to the network, via [swaps.xyz](http://swaps.xyz) when a bridge or swap is involved.
* `DEPOSIT_TX_CONFIRMED` - when the transaction is confirmed on the blockchain.
* `DEPOSIT_TX_ENRICHED` - when the transaction is enriched with additional data.

## `DEPOSIT_TX_SUBMITTED` Payload Example

```json JSON theme={null}
{
  "event": "DEPOSIT_TX_SUBMITTED", // Webhook event type
  "depositId": "dep_1234567890", // Unique deposit identifier
  "customerId": "cust_abc123", // Customer identifier
  "amount": "343000000", // Net destination amount at submission (finalised in CONFIRMED)
  "feesPaid": "7000000", // Fees charged, in smallest unit
  "gasCharge": "0", // Gas fee charged (if applicable), in smallest unit
  "grossAmount": "350000000", // Minimum expected destination amount at submission
  "currency": { // Destination currency (what the user will receive)
    "id": "currency_sol_id", // Internal currency ID
    "name": "Solana", // Currency name
    "decimals": 9, // Currency decimals
    "mintAddress": "11111111111111111111111111111111", // Token mint address (native SOL shown here)
    "coinMarketCapId": 5426, // CoinMarketCap ID
    "symbol": "SOL", // Currency symbol
    "blockchain": {
      "id": "blockchain_sol_id", // Internal blockchain ID
      "name": "SOL", // Blockchain name
      "symbol": "SOL" // Blockchain symbol
    }
  },
  "originalAmount": "343000000", // Original received
```

## `DEPOSIT_TX_CONFIRMED` Payload Example

```json JSON theme={null}
{
  "event": "DEPOSIT_TX_CONFIRMED", // Webhook event type

  "depositId": "dep_1234567890", // Unique deposit identifier
  "customerId": "cust_abc123", // Customer identifier (provided by merchant / integrator)

  "amount": "35328965", // Final settled destination amount (source of truth)
  "feesPaid": "706579", // Total fees charged, in smallest unit
  "gasCharge": "0", // Gas fee charged (if applicable), in smallest unit
  "grossAmount": "36035544", // Final destination amount before fees

  "currency": { // Destination currency (what the customer receives)
    "id": "currency_sol_id", // Internal currency ID
    "name": "Solana", // Currency name
    "decimals": 9, // Currency decimals
    "mintAddress": "11111111111111111111111111111111", // Token mint address (native SOL shown here)
    "coinMarketCapId": 5426, // CoinMarketCap ID
    "symbol": "SOL", // Currency symbol

    "blockchain": {
      "id": "blockchain_sol_id", // Internal blockchain ID
      "name": "SOL", // Blockchain name
      "symbol": "SOL" // Blockchain symbol
    }
  },

  "originalAmount": "4993316380000000", // Original received amount (source), in smallest unit of originalCurrency
  "originalAmountInUSD": "3072627", // USD value of originalAmount at time of processing (smallest USD unit, e.g. cents * 100)
  
  "originalCurrency": { // Source currency (what the user originally sent)
    "id": "currency_bnb_id", // Internal currency ID
    "name": "BNB", // Currency name
    "decimals": 18, // Currency decimals
    "mintAddress": "0x0000000000000000000000000000000000000000", // Token contract address (or native placeholder)
    "coinMarketCapId": 1839, // CoinMarketCap ID
    "symbol": "BNB", // Currency symbol

    "blockchain": {
      "id": "blockchain_bsc_id", // Internal blockchain ID
      "name": "BSC", // Blockchain name
      "symbol": "BSC" // Blockchain symbol
    }
  },

  "webhookDeliveryIdempotencyKey": "DEPOSIT_TX_CONFIRMED:tx_abc123", // Idempotency key for webhook delivery
  "txIdempotencyKey": "tx_abc123", // Idempotency key for the transaction
  "submittedTransactionIdempotencyKey": "submitted_tx_abc123", // Idempotency key for submitted transaction (if applicable)

  "transactionObject": { // Transaction details object
    "id": "txn_1234567890", // Internal transaction ID
    "fee": "706579", // Fee amount in smallest unit
    "createdAt": "2026-02-13T16:35:27.561Z", // Timestamp of transaction creation
    "paymentType": "DEPOSIT", // Payment type classification

    "meta": {
      "id": "tx_meta_abc123", // Internal transaction meta ID
      "amount": "35328965", // Deposited amount, in smallest unit
      "senderPK": "0xSenderWalletAddressHere", // Sender wallet address
      "recipientPK": "RecipientWalletAddressHere", // Recipient wallet address
      "transactionType": "DEPOSIT", // Transaction type

      "currency": { // Destination currency object (same as top-level currency)
        "id": "currency_sol_id",
        "name": "Solana",
        "decimals": 9,
        "mintAddress": "11111111111111111111111111111111",
        "coinMarketCapId": 5426,
        "symbol": "SOL",
        "blockchain": {
          "id": "blockchain_sol_id",
          "name": "SOL",
          "symbol": "SOL"
        }
      },

      "transactionSignature": "0xTransactionHashOrSignatureHere", // Blockchain tx hash/signature
      "customerDetails": null, // Optional customer metadata (can be null)
      "productDetails": {}, // Optional product metadata
      "transactionStatus": "SUCCESS", // Transaction status
      "totalAmount": "35328965" // Total processed amount, in smallest unit
    }
  },

  "transaction": "{\"id\":\"txn_1234567890\"...}" // Stringified version of transactionObject (legacy/compat)
}
```

<Warning>
  **Amount finality:** `DEPOSIT_TX_SUBMITTED.grossAmount` is the minimum expected destination amount. The final settled amount is provided in `DEPOSIT_TX_CONFIRMED.amount` and may be slightly higher.
</Warning>

## `DEPOSIT_TX_ENRICHED` Payload Example

This event includes an `incomingTransactions` array containing on-chain transaction details. This data can be used to reconcile deposits, track confirmation details, and build reliable transaction histories.

```json JSON theme={null}
{
  "event": "DEPOSIT_TX_ENRICHED", // Webhook event type
  "depositId": "69861e434e3b4725275f1e14", // Unique deposit identifier
  "customerId": "test", // Customer identifier

  "amount": "3919234", // Net deposited amount (after fees), in smallest currency unit
  "feesPaid": "78384", // Fees charged, in smallest currency unit
  "gasCharge": "0", // Gas fee charged (if applicable), in smallest currency unit
  "grossAmount": "3997618", // Total amount including fees, in smallest currency unit

  "currency": {
    "id": "6340313846e4f91b8abc519b", // Internal currency ID
    "name": "USD Coin", // Currency name
    "decimals": 6, // Currency decimals
    "mintAddress": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v", // Token mint address
    "coinMarketCapId": 3408, // CoinMarketCap ID
    "symbol": "USDC", // Currency symbol
    "blockchain": {
      "id": "6340313846e4f91b8abc515c", // Internal blockchain ID
      "name": "SOL", // Blockchain name
      "symbol": "SOL" // Blockchain symbol
    }
  },

  "originalAmount": "46185585", // Original received amount (before conversion), in smallest unit of originalCurrency
  "originalAmountInUSD": "3997651", // USD value of originalAmount at time of processing, in cents (or smallest USD unit)
  "originalCurrency": {
    "id": "6340313846e4f91b8abc5195", // Internal currency ID of original asset
    "name": "Solana", // Original asset name
    "decimals": 9, // Original asset decimals
    "mintAddress": "11111111111111111111111111111111", // Original asset mint address
    "coinMarketCapId": 5426, // CoinMarketCap ID
    "symbol": "SOL", // Original asset symbol
    "blockchain": {
      "id": "6340313846e4f91b8abc515c", // Blockchain ID
      "name": "SOL", // Blockchain name
      "symbol": "SOL" // Blockchain symbol
    }
  },

  "transactionObject": {
    "id": "69861ef6cec1fd89b559a8a7", // Internal transaction ID
    "fee": "78384", // Transaction fee, in smallest currency unit
    "createdAt": "2026-02-06T17:03:50.641Z", // Transaction creation timestamp (ISO 8601)
    "paymentType": "DEPOSIT", // Payment type classification
    "meta": {
      "id": "69861ef6cec1fd89b559a8a5", // Internal transaction meta ID
      "amount": "3919234", // Deposited amount, in smallest currency unit
      "senderPK": "Cq9f4fhen7ovueaa3Ug44RE2nEJSPhD41NV5HpLpjgGG", // Sender wallet address
      "recipientPK": "7YancRyNQyp9s6G7YNwx9H93UqswoKWqF9GuNJPufyvW", // Recipient wallet address
      "transactionType": "DEPOSIT", // Transaction type
      "currency": {
        "id": "6340313846e4f91b8abc519b", // Currency ID
        "name": "USD Coin", // Currency name
        "decimals": 6, // Currency decimals
        "mintAddress": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v", // Token mint address
        "coinMarketCapId": 3408, // CoinMarketCap ID
        "symbol": "USDC", // Currency symbol
        "blockchain": {
          "id": "6340313846e4f91b8abc515c", // Blockchain ID
          "name": "SOL", // Blockchain name
          "symbol": "SOL" // Blockchain symbol
        }
      },
      "transactionSignature": "2NPEMm7XEgz2Hcr3fZ4KdqE6bjxz887YF9vFssipXg1UY5tUtzR8cSbENjHY8ij7qLQMp4VCQqPK18vAwkedkRg1", // Blockchain transaction signature/hash
      "customerDetails": {
        "additionalJSON": "testing" // Customer metadata (custom field)
      },
      "productDetails": {}, // Product metadata (if applicable)
      "transactionStatus": "SUCCESS", // Transaction status
      "totalAmount": "3919234" // Total processed amount, in smallest currency unit
    }
  },

  "transaction": "{\"id\":\"69861ef6cec1fd89b559a8a7\"...}", // Stringified JSON version of transactionObject (legacy/compat)

  "webhookDeliveryIdempotencyKey": "DEPOSIT_TX_ENRICHED:69861ef6cec1fd89b559a8a5", // Idempotency key for webhook delivery
  "txIdempotencyKey": "69861ef6cec1fd89b559a8a5", // Idempotency key for the transaction

  "incomingTransactions": [
    {
      "hash": "4zig5GYQzkJwf2N36X4CuYejCasCcEgnbBmGxQWn32a6S3aJa4RT6cDHweDvr73BNVqKWHdfpNPaH9NK1AJXN57N", // On-chain transaction hash
      "from": "7YancRyNQyp9s6G7YNwx9H93UqswoKWqF9GuNJPufyvW", // Sender address
      "to": "Cq9f4fhen7ovueaa3Ug44RE2nEJSPhD41NV5HpLpjgGG", // Recipient address
      "value": "46185585", // Amount transferred, in smallest unit of originalCurrency
      "blockNumber": 398484220, // Block/slot number
      "timestamp": 1770397408, // Transaction timestamp (unix epoch seconds)
      "status": "success", // On-chain execution status
      "gasUsed": "5000" // Gas/compute units used (chain-specific)
    }
  ]
}
```

## Authenticating Webhooks with Bearer Token

A unique token generated at webhook creation is included with each webhook request as an Authorization: Bearer SHARED\_TOKEN header, verifying that the webhook is sent from us.

```json JSON theme={null}
{
    "id": "636cf9c095aeedb263968ee9",
    "paylink": "636a74162e72d4ad24ac9ce9",
    "company": "6343e77d91c393456aa56462",
    "targetUrl": "https://target-url.com/post-endpoint",
    "events": [
        "CREATED"
    ]
    "sharedToken": "PGpDZdZdxjdN+VgoxR/RHItMj0gq2BK5tEZtIisfyKe4M8l0B51qED/YqSSPwfAVtonvdXKhn+9j63b4krxGWNkO3hyPQiiu1SD2uttjEAdMeUO+3QoTNAwxuH1FzwyP"
}
```

**Note:** Retain this token, as it is required to authenticate and delete webhooks if needed.

# Retrieving Geolocation from the Webhook Payload

The `submitGeolocation` field in the webhook payload provides the ISO 3166-1 alpha-2 country code representing the location of the IP address that initiated the transaction. This field is useful for understanding the geographic source of transactions. See the code example below, taken from the webhook payload

```json JSON theme={null}
"submitGeolocation": "FR"
// ISO 3166-1 alpha-2 country code based on IP address which submitted the 
transaction to our server
```

# Create a Webhook
Source: https://docs.hel.io/reference/webhook/create

POST /v1/webhook/paylink/api-key
Create a global or pay link webhook using this endpoint. To create a global webhook, do not specify a paylinkId.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Create a Pay Link Webhook
Source: https://docs.hel.io/reference/webhook/paylink-transaction/create

POST /v1/webhook/paylink/transaction
Create a webhook to listen for transaction events on a specific pay link.

<Info>
  **NOTE:** When using Helio on mainnet, set your Base URL to [https://api.hel.io](https://api.hel.io) and generate your API keys from [moonpay.hel.io](https://app.hel.io/) . For testnet, use [https://api.dev.hel.io](https://api.dev.hel.io) and generate your API keys from [moonpay.dev.hel.io](https://app.dev.hel.io/).
</Info>

# Get Webhooks for a Pay Link
Source: https://docs.hel.io/reference/webhook/paylink-transaction/list

GET /v1/webhook/paylink/transaction
Retrieve all webhooks configured for a Pay Link.

<Info>
  **NOTE:** When using Helio on mainnet, set your Base URL to [https://api.hel.io](https://api.hel.io) and generate your API keys from [moonpay.hel.io](https://app.hel.io/) . For testnet, use [https://api.dev.hel.io](https://api.dev.hel.io) and generate your API keys from [moonpay.dev.hel.io](https://app.dev.hel.io/).
</Info>

# Get a Pay Link Webhook by ID
Source: https://docs.hel.io/reference/webhook/paylink-transaction/retrieve

GET /v1/webhook/paylink/transaction/{webhookId}
Fetch the details of a specific pay link webhook by its ID.

<Info>
  **NOTE:** When using Helio on mainnet, set your Base URL to [https://api.hel.io](https://api.hel.io) and generate your API keys from [moonpay.hel.io](https://app.hel.io/) . For testnet, use [https://api.dev.hel.io](https://api.dev.hel.io) and generate your API keys from [moonpay.dev.hel.io](https://app.dev.hel.io/).
</Info>

# Delete a Pay Link Webhook
Source: https://docs.hel.io/reference/webhook/paylink-transaction/delete

DELETE /v1/webhook/paylink/transaction/{webhookId}
Delete a Pay Link webhook by its ID to stop receiving transaction events.

<Info>
  **NOTE:** When using Helio on mainnet, set your Base URL to [https://api.hel.io](https://api.hel.io) and generate your API keys from [moonpay.hel.io](https://app.hel.io/) . For testnet, use [https://api.dev.hel.io](https://api.dev.hel.io) and generate your API keys from [moonpay.dev.hel.io](https://app.dev.hel.io/).
</Info>

# Create a Subscription Webhook
Source: https://docs.hel.io/reference/webhook/paylink-subscription/create

POST /v1/webhook/paylink/subscription
Create a webhook to listen for transaction events on a subscription pay link.

<Info>
  **NOTE:** When using Helio on mainnet, set your Base URL to [https://api.hel.io](https://api.hel.io) and generate your API keys from [moonpay.hel.io](https://app.hel.io/) . For testnet, use [https://api.dev.hel.io](https://api.dev.hel.io) and generate your API keys from [moonpay.dev.hel.io](https://app.dev.hel.io/).
</Info>

# Get Webhooks for a Subscription
Source: https://docs.hel.io/reference/webhook/paylink-subscription/list

GET /v1/webhook/paylink/subscription
Retrieve all webhooks configured on a subscription Pay Link.

<Info>
  **NOTE:** When using Helio on mainnet, set your Base URL to [https://api.hel.io](https://api.hel.io) and generate your API keys from [moonpay.hel.io](https://app.hel.io/) . For testnet, use [https://api.dev.hel.io](https://api.dev.hel.io) and generate your API keys from [moonpay.dev.hel.io](https://app.dev.hel.io/).
</Info>

# Get a Subscription Webhook by ID
Source: https://docs.hel.io/reference/webhook/paylink-subscription/retrieve

GET /v1/webhook/paylink/subscription/{webhookId}
Fetch the details of a specific subscription webhook by its ID.

<Info>
  **NOTE:** When using Helio on mainnet, set your Base URL to [https://api.hel.io](https://api.hel.io) and generate your API keys from [moonpay.hel.io](https://app.hel.io/) . For testnet, use [https://api.dev.hel.io](https://api.dev.hel.io) and generate your API keys from [moonpay.dev.hel.io](https://app.dev.hel.io/).
</Info>

# Delete a Subscription Webhook
Source: https://docs.hel.io/reference/webhook/paylink-subscription/delete

DELETE /v1/webhook/paylink/subscription/{webhookId}
Delete a subscription webhook by its ID to stop receiving subscription-related events.

<Info>
  **NOTE:** When using Helio on mainnet, set your Base URL to [https://api.hel.io](https://api.hel.io) and generate your API keys from [moonpay.hel.io](https://app.hel.io/) . For testnet, use [https://api.dev.hel.io](https://api.dev.hel.io) and generate your API keys from [moonpay.dev.hel.io](https://app.dev.hel.io/).
</Info>

# Create a Deposit Webhook
Source: https://docs.hel.io/reference/webhook/deposit/create

POST /v1/webhook/deposit/api-key
Create a webhook for a deposit.

<Info>
  **NOTE:** When using Helio on mainnet, set your Base URL to [https://api.hel.io](https://api.hel.io) and generate your API keys from [moonpay.hel.io](https://app.hel.io/) . For testnet, use [https://api.dev.hel.io](https://api.dev.hel.io) and generate your API keys from [moonpay.dev.hel.io](https://app.dev.hel.io/).
</Info>

# Shopify Webhooks
Source: https://docs.hel.io/reference/webhook/shopify

Set Up Webhooks for your Shopify orders

You can set up webhooks to receive notification alerts and data regarding payments made on your Shopify store via Solana Pay.

# Pre-Requisities

Before setting up the webhook, ensure you do the following:

1. Log in to the Shopify Merchant Dashboard.
2. Retrieve your API Keys.
3. Obtain your Shopify Pay Link ID – This is the ID found at the end of the URL of the Shopify Pay Link.

# Setting Up the Webhook

First use our [create webhook endpoint](https://docs.hel.io/reference/webhook/create) to configure the webhook for receiving payment notifications.

# Shopify Payment Webhook Payload

Upon successful payment, you will receive the following payload.

```json theme={null}
"event": "CREATED",
  "transactionObject": {
    "id": "67d0163484e9de99088b8c05",
    "paylinkId": "66b3ae45d561f776b94873f0",
    "fee": "200",
    "quantity": 1,
    "createdAt": "2025-03-11T10:53:40.016Z",
    "paymentType": "PAYLINK",
    "meta": {
      "id": "67d0163484e9de99088b8c03",
      "amount": "19800",
      "senderPK": "89ZFMYrbVFA8vwuw1wzPHQBHYCJsPuMpE9izfcKeb5Qp",
      "recipientPK": "Bd1EQQasAcpudCWYXZVL2tSjktJkCJVqPU2Nd6VNrEEV",
      "transactionType": "PAYLINK",
      "customerDetails": {},
      "productDetails": null,
      "additionalProductDetails": [],
      "transactionSignature": "3RXXiJxRjVE3ypdEzWvcNW2ASb3gc1C4Vc4U2KJJwcrzPjKtM5yep1Gmz4vDhutf229m3ApZtb9sgrMhLYMYDQYr",
      "transactionStatus": "SUCCESS",
      "splitRevenue": false,
      "remainingAccounts": [],
      "totalAmount": "19800",
      "affiliateAmount": "0",
      "tokenQuote": {
        "from": "USDC",
        "fromAmountDecimal": "0.02",
        "to": "USDC",
        "toAmountMinimal": "20000"
      },
      "shopifyPaymentDetails": {
        "shopifyPaymentGid": "gid://shopify/PaymentSession/rVVb9k5vukGQollX60oEUQi0L",
        "shopifyPaymentId": "rVVb9k5vukGQollX60oEUQi0L"
      },
      "submitGeolocation": "GB",
      "currency": {
        "id": "6340313846e4f91b8abc519b",
        "blockchain": null
      }
    }
  }
}
```

In the payload above, the `shopifyPaymentDetails` object contains the following identifiers, which are useful for referencing payments made on your Shopify store:

\* `shopifyPaymentGid` - A global unique identifier

\* `shopifyPaymentId` - A reference ID for the payment

# Get Transactions by Pay Link ID
Source: https://docs.hel.io/reference/transactions/list

GET /v1/transactions/{prId}/transactions
Retrieve all transactions associated with a specific paylink ID.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Get a Transaction by Signature
Source: https://docs.hel.io/reference/transactions/retrieve-by-signature

GET /v1/transactions/signature/{signature}
Retrieve the details of a transaction using its blockchain signature.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Get a Transaction by Shopify Payment ID
Source: https://docs.hel.io/reference/transactions/retrieve-by-shopify-payment

GET /v1/transactions/shopify/paymentid/{id}
Retrieve the details of a transaction using its Shopify payment ID.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Export All Transactions From Your Account
Source: https://docs.hel.io/reference/export/payments

GET /v1/export/payments
Get all transactions for your account, filtered by Pay Link ID, sender public key, or date range.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Prepare a Headless Payment
Source: https://docs.hel.io/reference/transaction/headless/prepare

POST /v1/transaction/headless/prepare
Prepares a Solana headless transaction. Returns a payload that the payer can sign and submit.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Submit a Headless Payment
Source: https://docs.hel.io/reference/transaction/headless/submit

POST /v1/transaction/headless/submit
Submits a Solana headless transaction.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Get All Subscriptions
Source: https://docs.hel.io/reference/subscriptions/list

GET /v1/subscriptions
Fetch all subscriptions associated with your Helio account.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Get a Subscription by ID
Source: https://docs.hel.io/reference/subscriptions/retrieve

GET /v1/subscriptions/{id}
Retrieve the details of a specific subscription by its ID.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Add to a Wallet Allowlist
Source: https://docs.hel.io/reference/allowlist/add

PATCH /v1/allowlist/add
Add a wallet address to your allowlist when restricting access to a paylink.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Merchant Account
Source: https://docs.hel.io/reference/platform/overview

Programmatically Create a Merchant Account on MoonPay Commerce

You can create a Merchant Account on MoonPay Commerce via API to generate payment links, accept crypto, and manage transactions. This is ideal for B2B platforms embedding crypto payments, enabling seamless user onboarding.

# Apply for Platform-Level API Access

This feature is not publicly available. To access it and receive your platform API keys, please email [hi@hel.io](mailto:hi@hel.io) to express your interest in a partnership.

# Partner Account
Source: https://docs.hel.io/reference/platform/partner-accounts

Make API calls on behalf of your connected merchants

Partner API Access allows platform partners to make API calls on behalf of their connected merchants. This is useful for platforms that integrate Helio and need to manage payments, pay links, and transactions for multiple merchant accounts.

**Partner API Access is available for approved platform partners only**. Contact the Helio team to request Platform API credentials.

## How It Works

Instead of each merchant generating their own API keys, platform partners receive a single set of **Platform API credentials** that can be used to access any merchant account linked to their platform.

| Authentication Type | Use Case                             | Credentials                             |
| :------------------ | :----------------------------------- | :-------------------------------------- |
| **Merchant API**    | Merchant accessing their own account | Merchant's API Key + Secret             |
| **Partner API**     | Partner accessing merchant accounts  | Platform API Key + Secret + Merchant ID |

## Authentication

### Required Headers & Parameters

When making requests as a partner you must provide:

| Parameter     | Location        | Description                                                     |
| ------------- | --------------- | --------------------------------------------------------------- |
| apiKey        | Query parameter | Your Platform API Key                                           |
| Authorization | Header          | Bearer token with your Platform API Secret                      |
| x-merchant-id | Header          | The Helio Company ID of the merchant you're acting on behalf of |

### Example Request

```curl theme={null}
curl --request POST \
  --url "https://api.hel.io/v1/paylink/create/api-key?apiKey=YOUR_PLATFORM_API_KEY" \
  --header "Authorization: Bearer YOUR_PLATFORM_API_SECRET" \
  --header "Content-Type: application/json" \
  --header "x-merchant-id: MERCHANT_COMPANY_ID" \
  --data '{
    "name": "Example Pay Link",
    "price": "1000000",
    "pricingCurrency": "6340313846e4f91b8abc519b",
    "template": "OTHER",
    "features": {
      "canChangeQuantity": false,
      "canChangePrice": false
    },
    "recipients": [
      {
        "walletId": "MERCHANT_WALLET_ID",
        "currencyId": "6340313846e4f91b8abc519b"
      }
    ]
  }'
```

## Getting the Merchant ID

The `x-merchant-id` header requires the merchant's **Company ID**. This is the internal identifier for the merchant's account in Helio.

You can find the Helio company ID upon creation of a merchant account using the [Create a Merchant Account](/reference/auth/sign-up) endpoint. This is the internal identifier for the merchant's account.

As a platform partner, you should store this ID when merchants connect their accounts to your platform.

## Supported Endpoints

Partner API Access works with all merchant-facing API endpoints, including:

* **Pay Links** - Create, update, disable pay links
* **Transactions** - Retrieve transaction history
* **Charges** - Create and manage charges
* **Deposits** - Create deposits and manage customers
* **Subscriptions** - View subscription details
* **Webhooks** - Manage webhook configurations

## Error Handling

### Common Error Responses

| HTTP Status | Error Message                                     | Cause                                                  |
| ----------- | ------------------------------------------------- | ------------------------------------------------------ |
| 401         | "Please provide platform apiKey and bearer token" | Missing apiKey query parameter or Authorization header |
| 401         | "Invalid platform API key"                        | Platform API key not found or disabled                 |
| 401         | "Invalid platform API secret"                     | Bearer token doesn't match the API key                 |
| 401         | "Merchant not found"                              | Invalid x-merchant-id or merchant doesn't exist        |
| 401         | "Not authorized to access this merchant"          | Merchant is not linked to your platform                |

### Platform Key Without Merchant ID

If you accidentally use a Platform API key without the `x-merchant-id header`, you'll recieve:

```json theme={null}
{
  "statusCode": 401,
  "message": "Platform API key detected. Please include 'x-merchant-id' header with the merchant ID"
}
```

## Access Levels

Platform API keys have an associated access level that determines which operations are permitted. The access level is configured when the Platform API key is issued.

| Access Level | Permissions                                       |
| :----------- | :------------------------------------------------ |
| READ\_ONLY   | Can only retrieve data (GET requests)             |
| STANDARD     | Can create and read pay links, transactions, etc. |
| ADMIN        | Full access including sensitive operations        |

## Best Practices

1. **Store Platform credentials securely** - Never expose your Platform API secret in client-side code
2. **Validate merchant IDs** - Ensure the merchant ID is valid before making API calls
3. **Handle errors gracefully** - Implement proper error handling for authorization failures
4. **Use HTTPS only** - All API requests must use HTTPS

# Getting Started

1. **Request Platform API access** - Contact the Helio team to become a platform partner
2. **Receive credentials** - You'll receive a Platform API Key and Secret
3. **Connect merchants** - Merchants link their Helio accounts to your platform (store their Company IDs)
4. **Make API calls** - Use the `x-merchant-id` header to act on behalf of merchants

**Ready to become a partner?** Contact us at [partners@hel.io](mailto:partners@hel.io) to request Platform API access.

# Creating a Merchant Account
Source: https://docs.hel.io/reference/auth/sign-up

POST /v1/auth/external/sign-up
Create a new Helio merchant account using an external authentication method.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# Signing In to a Merchant Account
Source: https://docs.hel.io/reference/auth/sign-in

POST /v1/auth/external/sign-in
Sign in to an existing Helio merchant account using an external authentication method.

<Info>
  **Note:** When using the production environment at [moonpay.hel.io](http://app.hel.io), set your API endpoint to `api.hel.io/v1` and generate API keys there. For the development environment, use `api.dev.hel.io/v1` and generate API keys from [moonpay.dev.hel.io](http://app.dev.hel.io).
</Info>

# FAQ
Source: https://docs.hel.io/docs/welcome-to-helio



# FAQs

## Company & Security

### What is MoonPay Commerce?

The leading crypto checkout & deposits platform for developers and merchants. Integrate in minutes and get paid instantly in stablecoins.

### Who is Behind MoonPay Commerce?

MoonPay Commerce, formerly known as Helio, was founded in 2022 by experienced entrepreneurs and a talented team specialising in crypto and fintech. We rebranded to MoonPay Commerce following MoonPay’s acquisition of Helio in 2025.

### Is MoonPay Commerce Audited?

Yes. MoonPay Commerce (formerly known as Helio) was audited by Ackee Blockchain under the Helio brand. We continue to uphold the same high security standards, maintaining a robust KYC/AML program and performing regular penetration tests and vulnerability assessments to ensure our infrastructure remains secure and compliant.

## Payments & Fees

### Why Choose Crypto Checkouts?

* Enable direct, buyer-to-merchant payments without intermediaries
* Benefit from low transaction fees
* Experience instant settlement of funds
* Attract and engage a 500m strong community of digital-savvy users who love using their crypto

### How Much Does MoonPay Commerce Cost?

Getting started with MoonPay Commerce is free, with fees applied on a per-transaction basis. For more details, check out our [pricing and fees information](/docs/pricing-fees#/).

### Does MoonPay Commerce Custody Funds?

No, MoonPay Commerce does not custody funds. As a technology provider—not an MSB/VASP or money transmitter—we facilitate fully decentralised (100% DeFi) payments on the blockchain. All transactions are peer-to-peer, allowing buyers to pay merchants directly. Funds are never held by Helio, and merchants receive payments instantly in their wallets.

### What Currencies Does MoonPay Commerce accept?

MoonPay Commerce supports payments in USDC, SOL, ETH, BTC, and hundreds of other digital currencies. If your token isn't listed in our drop-down menu, you can [pay a fee here](https://www.hel.io/add-token) to have it added.

## Products & Integrations

### What is a Crypto Wallet?

A crypto wallet is a self-custody tool that functions as a browser plug-in or mobile app. With self-custody, you hold your cryptocurrency directly using a public-private key pair, similar to storing cash in your own safe, rather than relying on an online account. It allows for easy, direct transactions with anyone around the world.

### What is the Solana Pay - Shopify Plugin?

MoonPay is the developer and operator of the official Solana Pay plugin for Shopify. [Learn more](/docs/solana-pay-shopify-plugin#/).

## Supported Blockchains & Compatibility

### Which Blockchains Does MoonPay Commerce Support?

We support all major blockchains including Solana, Bitcoin, Ethereum, Base, Polygon and many more.

### Is MoonPay Commerce Supported on Mobile Devices?

Yes, MoonPay Commerce is fully compatible with both iOS and Android. It also integrates seamlessly with mobile crypto wallets including deep-link support, and Wallet Connect.

## Refunds & Disputes

### How Can I Get a Refund? Can MoonPay Commerce Help?

For refunds, please contact the merchant directly, as all transactions made on the MoonPay Commerce platform are direct peer-to-peer payments. Once a payment is made, it cannot be reversed or reclaimed by MoonPay due to the blockchain's security and irreversible nature. Therefore, MoonPay is unable to resolve payment disputes.

# Fees
Source: https://docs.hel.io/docs/pricing-fees

Explore Moonpay Commerce pricing options & fees

# Fees

MoonPay Commerce is a self-serve platform, it's free to get started and we charge a fee per transaction.

| Fees            | HelioX | Standard Fee |
| --------------- | ------ | ------------ |
| Transaction fee | 1%     | 2%           |

<Info>
  Our standard [Terms of Service](https://docs.hel.io/docs/terms-of-service) apply. We offer custom pricing for high volume merchants. High-risk platforms are subject to a minimum rate of 2%
</Info>

| Optional features              | Fees  |
| ------------------------------ | ----- |
| Swaps                          | 0.25% |
| Auto-offramp (fiat settlement) | 0.50% |

# HelioX Pass

HelioX is the premium tier of our platform, originally part of Helio and now continuing seamlessly under MoonPay Commerce. It offers the lowest fees and top-tier features for power users. Subscribe by holding a HelioX Pass NFT in any wallet linked to your MoonPay Commerce account. You can purchase your NFT [here](https://magiceden.io/marketplace/helions).

# Security
Source: https://docs.hel.io/docs/security

Security is MoonPay Commerce's top priority, adhering to the highest standards for protocol and user safety

# User risks and MoonPay Commerce's safety measures

When engaging in Web3—like buying NFTs, DeFi investing, or using MoonPay Commerce—you encounter certain risks. MoonPay Commerce provides best practices on our blog to help you reduce these risks and aims to ensure you understand the technical aspects of using our platform.

# Merchant verification & user Safety

MoonPay Commerce includes KYC/B merchant verification and safety tools for trusted payments. Being a decentralised protocol, MoonPay Commerce allows direct, irreversible transactions from user to merchant wallets. Always verify merchant trustworthiness with MoonPay Commerce's safety features.

# Blockchain & Smart Contract Risks

MoonPay Commerce operates across Solana, EVM and Bitcoin. Regular audits by Ackee Blockchain for MoonPay Commerce smart contracts help secure our protocol.

<Info>
  [Blockchain Security Services | Ackee Blockchain](https://ackee.xyz/)
</Info>

# InfoSec Support

Contact [infosec@hel.io](mailto:infosec@hel.io) for security assistance.

# Verification
Source: https://docs.hel.io/docs/verification

Easy to use safety tools for merchants & users

MoonPay Commerce provides merchant verification for both creators and businesses.

**For Creators:**

1. Log in to the MoonPay Commerce dashboard.
2. Navigate to **Settings → Merchant Settings**.
3. Select **Creator** as the type.
4. Link your X (Twitter) account.
5. Complete verification through Sumsub.

**For Businesses:**

1. Go to **Settings → Merchant Settings**.
2. Select **Business**.
3. Fill in necessary fields.
4. Complete verification with **Persona**.

These verification steps help establish merchant credibility, enhancing user trust.

<img alt="Verification" />

# Report a suspicious link

Report suspicious links directly from the checkout page. Our security team monitors and blacklists risky links and wallets 24/7.

# Sanctioned countries & wallets

MoonPay Commerce blocks access from OFAC sanctioned countries and wallets using a mix of geo-IP, industry leading tools like Chainanalysis and heuristics.

# Pay Link authentication

MoonPay Commerce offers various [Access Controls](/docs/gated-payments#/) options including Discord SSO and gating. This helps merchants lock down payments to a targeted and intended customer audience.

# Payment disputes / refunds

For refunds, contact the merchant directly; they can issue [refunds](https://x.com/helio_pay/status/1641108468026290176?s=20) via the MoonPay Commerce dashboard. MoonPay Commerce is a **decentralised protocol**, meaning funds transfer directly from users to merchants, secured by the blockchain and these transactions are irreversible. Before purchasing on MoonPay Commerce links/widgets, verify the merchant’s trustworthiness using our safety features.

***

[Telegram Memberships](/docs/telegram-memberships)

[Gated Payments](/docs/gated-payments)

# Team Roles
Source: https://docs.hel.io/docs/team-roles

Invite collaborators to your MoonPay Commerce account and operate efficiently as a team

Currently there are 3 roles: **Admin,** **Collaborator** and **Account Owner**

# Roles

MoonPay Commerce offers three roles, with Admin and Collaborator as invitable user roles.

**Account owner:**

* **Role Assignment:** Automatically assigned to the account creator.
* **Permissions:** Full access to all MoonPay Commerce features

**Admin:**

* **Role Assignment:** Invited by company account owner
* **Permissions:** Full access to all MoonPay Commerce features, except the ability to delete connected wallets

**Collaborator:**

* **Role Assignment:** Invited by an admin
* **Permissions:**
  * View team transactions.
  * Create and edit Pay Links on behalf of the team.
  * Limited to using wallets linked by the Admin.
  * Cannot access settings, add or change payout wallets, configure split payments, or process refunds.

# Managing Team Members

To manage team roles and add collaborators:

* **View Team Members:** Go to **Settings -> Team Members**.
* **Invite Collaborators:**
  * Ask the collaborator to create a MoonPay Commerce account by signing up via email, see [here](https://docs.hel.io/docs/for-creators).
  * Go to **Settings → Team**, click **Invite**, then enter the team member’s **name**, **email address**, and **permissions**.

<img alt="" />

* **Join the Team:**
  * The collaborator can log in to [Helio](https://app.hel.io/) or refresh their dashboard to accept the invitation.

<img alt="" />

* They can toggle between the team account and their personal account via the team selector in the top left of the dashboard.

<img alt="" />

# Buyer Dashboard
Source: https://docs.hel.io/docs/buyer-dashboard

Browse orders, access all receipts & manage subscriptions

# Receipts

Login to [Helio Dashboard](https://app.hel.io/dashboard?userType=BUYER) and toggle between the merchant/buyer view at the top of the page to see a list of all your orders with receipts.

<img alt="" />

Easily access your transaction receipts, [manage subscriptions](/docs/subscriptions#/managing-and-tracking-subscriptions) and claim [Discord memberships](/docs/discord-memberships#/).

<img alt="" />

# Manage Accounts & Wallets

From the top right menu, toggle to **manage wallets**:

<img alt="" />

# Refunds

If you would like a refund, please contact the merchant directly. We've made it very easy for merchants to refund directly from the Helio dashboard.

# Pre-sales
Source: https://docs.hel.io/docs/pre-sales

Launch a Pre-sales campaign in minutes

MoonPay Commerce formerly Helio, is the leading, self-serve, Pre-Sales platform used by 1,000s of creators to pre-sell products or digital products/collectibles such as NFT & tokens using simple & fully customisable Pay Links.

Use Discord gating, wallet allowlists, countdowns, raffles or first-come-first serve to optimise your sales event.

<Info>
  You can also run your sales on [Magic Eden NFT Pre-Sales](https://presale.magiceden.io/), powered by MoonPay Commerce. The service is fully self-serve, offers the same functionality as MoonPay Commerce, and is fully branded as Magic Eden — helping you reach more buyers with the most recognisable brand in the NFT industry.
</Info>

# Quick Start

1. Log in to the [dashboard](https://app.hel.io/) and complete [verification](/docs/verification#/)
2. Settings -> Manage wallets to manage pay-outs and link additional wallets for team access.
3. Settings -> Integrations to configure the [Discord bot](/docs/discord-memberships#/) to assign Pre-Sales roles in your server
4. Dashboard -> Create payment to set up your Pay Link to start selling. Edit, duplicate & disable Pay Links from the Pay Links view
5. Transactions -> CSV export to get ready for the airdrops. Set up a [Google sheet](/docs/google-app-script#/) with real time transaction access for your team members

<iframe title="YouTube video player" />

# Features

* Sell with BTC, SOL, ETH, USDC and 100s of digital currencies, and even credit/debit cards.
* Capture user details including Wallet, Discord, Twitter and cross-chain wallets.
* Access controls: [Raffle Pre-Sale](/docs/gated-payments#/raffle-winners) or FCFS with [Discord gating, Allowlist, Access codes & NFT gating](/docs/gated-payments#/).
* Countdown to evoke FOMO and configure a max allocation per user & project.
* Enable [Affiliate links](/docs/affiliate-links#/) to reward influencers and supporters for helping you close sales.
* Enable [discounts](/docs/discounts#/) via codes or an NFT, process [refunds](/docs/buyer-dashboard#/refunds) with a single click from the dashboard.
* Pre-sell an [Ordinals NFT](https://x.com/helio_pay/status/1726948916229292473?s=20) in BTC OR in ETH/SOL & [auto-capture BTC address](https://docs.google.com/presentation/d/e/2PACX-1vQPpdCsR4fzE3YtdcLIIw9CEazGvAy1lXXrTadJ175Kz2ZstCkGGW8ogRQhgbclCw/pub?start=false\&loop=false\&delayms=3000\&slide=id.g2591bbd3222_0_0) for mint claim.

# Pre-Sales Support Service

Our team of product specialists are available to provide white-glove service & support.

* Personal welcome call, including a demo and guidance on pre-sales strategy.
* Introductions to specific DAOs and collaborations.
* Collaboration with Magic Eden. Run your pre-sale on ME branded pages, the most trusted brand in NFTs and a direct referral to Magic Eden Launchpad.

# Token Pre-Sales

We recommend you use the "Name your own price" option for token Pre-Sales and embed the [Checkout Widget](/docs/checkout-widget#/) to pre-sell the tokens from your own website.

## Getting Ready for Mint/Airdrop Day

Transaction details including wallet addresses, Discord ID, etc. are automatically registered by MoonPay Commerce and can be downloaded to CSV from the MoonPay Commerce dashboard or automated into a [Google Sheet](/docs/google-app-script#/).

You can share this sheet directly with your launchpad/ developer for the automated airdrop or free mint claim.

<Frame>
  <img alt="" />
</Frame>

# Affiliate Links
Source: https://docs.hel.io/docs/affiliate-links

Allow friends to share your links to earn rewards in real-time

Create your payment in the MoonPay Commerce dashboard and enable Affiliate links in Advanced options and set your revenue share between 0.1% and 99.9%.

<Info>
  **Note:** The Affiliate Links option only appears if **'Use token swaps' is disabled** and **a Solana recipient wallet is set as the exclusive payment method**.
</Info>

<img alt="" />

Share your Pay Link with your community, influencers or friends. Anyone with access to the Pay Link can connect their wallet and hit Share & Earn to generate her unique affiliate link. The revenue share is paid out in real-time to the affiliate wallet for each sale.

<img alt="" />

<Info>
  Affiliate links are available for Solana payments and coming to the other supported blockchains soon.
</Info>

# Discord Memberships
Source: https://docs.hel.io/docs/discord-memberships

Include access to your exclusive community with every sale

Use the MoonPay Commerce Discord bot to include & assign roles/memberships to your exclusive community with every Helio sale (i.e. receive payment -> assign role). Roles are also auto-removed when subscriptions expire if you use [subscriptions](/docs/subscriptions#/).

# Enable Developer Mode

Before proceeding, please enable developer mode for Discord. This will allow you to see the server, role and user IDs required to setup the Discord bot. See [this Discord article on how to achieve this](https://support.discord.com/hc/en-us/articles/206346498-Where-can-I-find-my-User-Server-Message-ID) .

# Channel & Role Setup

Log in to the [dashboard](https://app.hel.io/dashboard), select **"Settings" -> "Integrations"**.

Hit **"Authenticate"** to allow the MoonPay Commerce bot to be installed via Discord. This authentication will use your Discord administrator credentials in your default browser to approve the installation of the bot for the required server as follows:

<Frame>
  <img alt="" />
</Frame>

Head back to Settings in the dashboard and you will notice the Discord section has changed to allow you to enter the relevant IDs. Choose your Server ID and one or more Role IDs and hit "Save Settings".

<Frame>
  <img alt="" />
</Frame>

# Finalise Discord Setup

Return to **"Server Settings" -> "Roles"** and you should now see the **"MoonPay Commerce"** role appear:

<Frame>
  <img alt="" />
</Frame>

Select **"MoonPay Commerce"** to see the following. This is the bot role and should NOT be changed. Note that you can remove the bot in **"Server Settings" -> "Integrations"** if required.

<Frame>
  <img alt="" />
</Frame>

<Warning>
  You MUST move the MoonPay Commerce bot above the roles that you want to assign due to Discord's role hierarchy logic. Drag the MoonPay Commerce role up above the "MoonPay Commerce Access" group as follows.
</Warning>

<Frame>
  <img alt="" />
</Frame>

# Create a payment & assign the role members

* Click **CREATE PAYMENT** to set up your payment details and pricing options. Select a single payment for one-time access or a [subscription](/docs/subscriptions#/) access (the role will be removed at the end of the subscription period).
* Under **Advanced options -> Discord memberships**, load and select the roles you wish to assign. Users must sign in with Discord on the Pay Link. To make Discord optional, untick the **"require Discord login"** box, allowing it as an optional field.

<img alt="" />

# Membership Assigned Real-Time or Claimed Afterwards

Roles can be assigned in real-time or claimed later. Share the Pay Link anywhere. Buyers automatically receive the role if they’re in your server; otherwise, they can join and claim it later from the [MoonPay Commerce Buyer Dashboard](https://app.hel.io/dashboard?userType=BUYER). They'll receive email reminders to claim (untick "E-mail address" if you prefer not to collect or remind buyers). For subscriptions, claims remain valid until the subscription ends.

<img alt="" />

# Telegram Memberships
Source: https://docs.hel.io/docs/telegram-memberships

Include access to our Telegram groups with every purchase.

Gate Telegram access with the MoonPay Commerce Bot using one-time or subscription payments. Automate group entry/removal and link multiple groups to one pay link.

# Pre-requisites

1. **Convert your Group(s) into a Supergroup**

To convert your Telegram group to a supergroup, go to group settings and enable “Chat History for New Members” — this will trigger the upgrade. Alternatively, if available, you can tap “Convert to Supergroup.

<Frame>
  <img alt="" />
</Frame>

2. **Invite the Bot to Your Group and Make It an Admin**

To invite **HelioTelegramBot** to your Telegram group and make it an admin, open your group settings, tap **“Add Members”** to invite the bot, then go to **“Administrators”**, tap **“Add Admin”**, select the bot, and grant it the necessary permissions.

<Frame>
  <img alt="" />
</Frame>

3. **Retrieve the Chat ID of Each Group You’d Like to Grant Access To**

In each respective group, use the **/chat\_id** command to retrieve the chat ID. Make a note of this ID along with the group name, as both will be used in the subsequent setup steps.

<Info>
  **Note:** Your group ID should start with -100, indicating it’s a supergroup.
</Info>

<Frame>
  <img alt="" />
</Frame>

# Setup

1. **Add the Chat IDs and Group Names to the Integrations Section in Helio Settings.**

<Info>
  **Note:** You can grant access to a maximum of 15 groups
</Info>

<Frame>
  <img alt="" />
</Frame>

2. **Enable Telegram Memberships in the Advanced Options of Pay Link Creation.**

<Frame>
  <img alt="" />
</Frame>

# Telegram Group Access

At checkout, users will be prompted to enter their Telegram username and email address. This purchase includes exclusive access to a private Telegram group. Once the order is complete, an email will be sent with the invite link(s) to the group(s).

<Frame>
  <img alt="" />
</Frame>

# Subscriptions

Telegram memberships can be configured for subscriptions. Once a user’s subscription starts, they will be granted access to the group by the MoonPay Commerce Telegram Bot. Upon expiry, the bot will automatically remove them from the group.

# Sharing Screen Recordings With Inspect Mode Enabled
Source: https://docs.hel.io/docs/sharing-screen-recordings-with-inspect-mode-enabled

Learn how to share screen recordings to MoonPay Commerce support

To help the MoonPay Commerce support team diagnose and resolve your issue as quickly as possible, we may request screenshots or a video with your browser's Inspect Mode enabled. This process allows us to view the Network and Console tabs, which provide valuable debugging information. Below is a step-by-step guide for both PC and Mac users on how to enable Inspect Mode and capture the required information.

***

# For PC Users

## 1. Open Your Browser's Developer Tools

### Use one of the following shortcuts depending on your browser:

* Google Chrome/Edge: Press Ctrl + Shift + I
* Firefox: Press Ctrl + Shift + K

Alternatively:

1. Right-click anywhere on the page.
2. Select Inspect or Inspect Element from the menu.

## 2) Switch to the Required Tabs

In the Developer Tools panel:

* Click on the Network tab.
* Click on the Console tab (keep both visible if possible).

## 3. Reproduce the Issue

* Reload the page (press Ctrl + R) while keeping the Network tab open.
* Perform the actions that led to the issue.

## 4. Capture the Information

Screenshots:

1. Expand the Developer Tools panel to ensure all details are visible.
2. Use the PrtScn button or Windows + Shift + S to take a screenshot.
3. Save the screenshot in a convenient location.

Video:

1. Use a screen recording tool like OBS Studio, Loom, or the built-in Xbox Game Bar (Windows + G).
2. Record your screen while reproducing the issue, ensuring the Network and Console tabs are visible.
3. Save the video file.

***

# For Mac Users

## 1. Open Your Browser's Developer Tools

Use one of the following shortcuts depending on your browser:

* Google Chrome/Safari: Press Cmd + Option + I
* Firefox: Press Cmd + Option + K

Alternatively:

* Right-click anywhere on the page.
* Select Inspect or Inspect Element from the menu.

## 2. Switch to the Required Tabs

In the Developer Tools panel:

* Click on the Network tab.
* Click on the Console tab (keep both visible if possible).

## 3. Reproduce the Issue

1. Reload the page (press Cmd + R) while keeping the Network tab open.
2. Perform the actions that led to the issue.

## 4. Capture the Information

### Screenshots:

1. Expand the Developer Tools panel to ensure all details are visible.
2. Use Cmd + Shift + 4 to take a screenshot.
3. Save the screenshot in a convenient location.

### Video:

1. Use a screen recording tool like QuickTime Player (built into macOS) Use Cmd + Shift + 5 to take a screen recording, or a third-party app like Loom.
2. Record your screen while reproducing the issue, ensuring the Network and Console tabs are visible.
3. Save the video file.

***

# Sharing Your Files with MoonPay Commerce Support

1. Attach the screenshots and/or video to your Discord or Telegram support ticket.
2. Ensure any shared links have appropriate permissions so we can access them.

Providing this information will help us identify and resolve your issue much faster. If you have any questions, feel free to reach out to our support team for guidance.

# Terms of Service
Source: https://docs.hel.io/docs/terms-of-service

Effective October 1, 2025

**THESE TERMS AND CONDITIONS APPLY TO THE USE OF THE MOONPAY COMMERCE APP (FORMERLY HELIO), SOLANA PAY FOR SHOPIFY, AND OTHER WHITE-LABELLED APPLICATIONS**

**PLEASE READ THESE TERMS AND CONDITIONS CAREFULLY BEFORE USING THIS APP.**

**What's in these terms?**

These terms tell you the rules for using the MoonPay Commerce application which may be accessed at [https://hel.io](https://hel.io) or [https://moonpay.hel.io](https://moonpay.hel.io) (our App).

**Who we are and how to contact us**

MoonPay Commerce is an App operated by Helio Fintech Limited ("We" or the “Company”), a wholly owned subsidiary of MoonPay, Inc. We are registered in England and Wales under company number 13836904 and have our registered office at 16 Great Queen Street, Covent Garden, London, United Kingdom, WC2B 5AH. We are a limited company. To contact us, please email [commerce@moonpay.com](mailto:commerce@moonpay.com).

**By using our App you accept these terms**

By using our App, you confirm that you accept these terms of use and that you agree to comply with them.

These terms govern your use of the MoonPay Commerce (formely Helio) application (the “App”) and any associated or connected, or other services, features, content, or applications we offer through the App (collectively, the “Services”), which facilitates direct peer-to-peer transactions on decentralised blockchains (“Blockchain”).

If you do not agree to these terms, you must not use our App.

If the Company suspects or determines that you are using the App for any fraudulent purposes, illegal activities, or in a manner that violates these Terms and Conditions, the Company reserves the right, at its sole discretion, to terminate your access to the App, Solana Pay for Shopify, and any other related white-label applications, without prior notice.

We recommend that you print a copy of these terms for future reference.

**Risks**

Before using the Company's services, creating a crypto wallet, or purchasing digital assets, you must consider whether using those Services is suitable for you after carefully considering your financial circumstances. The value of digital assets such as cryptocurrency fluctuates and may become worthless. Cryptocurrency is not legal tender. A digital asset’s past value or performance is not an indicator of its future value or performance. By using the Services you agree that the Company is not responsible for any loss of a digital asset, or any losses arising from theft, loss, or mishandling, or diminution of value of any digital asset. Additionally, cryptocurrencies are not protected by the Financial Services Compensation Scheme (FSCS), the Federal Deposit Insurance Corporation (FDIC), the Securities Investor Protection Corporation (SIPC) or any other public or private insurer, including against cyber theft or theft by any other means. The nature of cryptocurrency may lead to an increased risk of fraud or cyber-attack and your cryptocurrency value may be irretrievably lost or stolen. Transfers or transactions in cryptocurrency are irrevocable and irreversible. Cryptocurrency assets are not regulated in many jurisdictions.

‍The Company is not an investment service and does not provide investment advice. No information on the App, including but not limited to information provided by the Company, constitutes investment advice. You must take independent professional investment advice before using the App. You agree that you will not use the contents of the Company's App or Services to make any investment decision.

The Company is not a digital asset market and does not make any representation or warranty as to the value of any digital asset. The Company may provide information regarding the price of digital assets. The Company does not make any representation or warranty as to the quality, accuracy, or completeness of that data. You must not rely on any pricing data provided on the App. You must independently verify any such information from a reputable source before relying on pricing information. Digital asset values are often volatile and may change instantaneously. The Company is not responsible or liable for any loss incurred by your using or transferring digital assets in connection with or based on the information you have received through using our Services.

**Services**

Our Services facilitate direct peer-to-peer transactions between merchants and buyers in USDC, USDT, BTC, SOL, ETH, ERC-20, SPL tokens and other cryptoassets. You may use our Services by logging in or linking your crypto wallet(s) to [https://hel.io/](https://hel.io/) or [https://moonpay.hel.io](https://moonpay.hel.io) to access the MoonPay Commerce dashboard, Pay Links, or various integration options.

By using the Company's App, you hereby grant the Company the right and licence to use your company's logo for marketing and promotional purposes. Such use may include but is not limited to, displaying your logo on The Company's webpage, in marketing materials, and advertising campaigns.

HelioX is the pro version of the App with the lowest fees and advanced features.

While the Company offers Services for businesses and individuals to accept direct, peer-to-peer transactions using the blockchain, it does not buy, sell, or take custody or possession of any cryptocurrency or digital asset, nor does it act as an agent or custodian for any user of the Services. Any transfer of digital assets is transacted via a Smart Contract and/or Embedded Wallets deployed by the Company to ensure that the merchant using our Services can ship digital content, goods, or services upon confirmation of the transaction through the relevant Blockchain network. Merchants receive digital assets directly in their designated wallet. We accept no liability to you or to any third party for any claims or damages that may arise in connection with any transaction that you engage in utilising the Services.

If you use the Services to send a transaction, you are a “Buyer”, and if you are using the Services to accept transactions, you are a “Merchant” and the terms of your agreement with each other are “Purchase Terms”. If you are either a Buyer or a Merchant, you agree that all Purchase Terms are determined by the Buyer and the Merchant. We are not a party to any Purchase Terms, which are solely between the Buyer and the Merchant, and not responsible for, and accepts no liability in respect of, ensuring compliance with such terms nor mediating or resolving any disputes concerning such Purchase Terms, including but not limited to any disputes arising out of or related to any intellectual property rights associated with digital content. The Buyer and Merchant are entirely responsible for communicating, agreeing to and enforcing Purchase Terms and for resolving any disputes arising from any breach of any Purchase Terms. Merchants must comply with and fulfil the Purchase Terms concerning any digital content, goods, or services that they sell.

By completing a transaction on the App, you as the Buyer acknowledge that the transaction is made with cryptocurrency and is a direct peer-to-peer transfer from you to the Merchant. Once a transaction is approved, the Company is unable to reverse the transaction or reclaim funds on your behalf. As a result, we are unable to resolve any disputes as the transactions are secured by the blockchain and are irreversible. By using the App, you as Buyer agree to these terms and conditions.

**Costs and Fees:** Transactions are subject to fees for utilising the Services are subject to fees (“Fees”). The Fees are listed [here](https://docs.hel.io/docs/pricing-fees).

To calculate the Fees, the following definitions apply:

“Revenue” means the gross amount received by Merchants when using our Services to accept Transactions.

“Gas fees” mean the fees that fund the network of computers that run the decentralised blockchain network.

“Transaction Fee” means the percentage of the Revenue generated from acceptance of transactions using our Services. The Transaction Fee may be, but is not required to be, the sales percentage for each transaction and may be changed from time to time.

By using the Services you agree to pay all applicable fees, and you authorise the Company automatically to charge you for any such fees or deduct such fees (including Transaction Fees) directly. Transactions received by Merchants do not include any taxes, and the Company shall have no responsibility for any such taxes by whomsoever levied. Each party shall be responsible for all taxes imposed on its income or property. In addition, interactions with the Blockchain may also result in transaction fees or Gas Fees imposed by the Blockchain, which shall also be your sole responsibility.

If you use our Services to accept transactions, you will receive Revenue less the Transaction Fee for each transaction effected by utilising the Services.

**Associated applications**

There are many associated applications available via the platform. Access to and use of these applications via the App is subject to these terms and conditions.

**Pay Link** is a hosted checkout page that merchants using our Services may create via the App dashboard. The purpose of the Pay Link is to make it easy for Merchants to make products and services available to Buyers and offer a simple interface to facilitate the peer-to-peer blockchain transaction between the parties. Merchants may use Pay Links to request customer information such as email addresses, integrate third-party digital platforms such as Discord, include digital content and memberships, and restrict or "gate" access based on allow lists, Discord roles and more. Pay Links and other App checkouts may be protected by reCAPTCHA and the Google [Privacy Policy](https://policies.google.com/privacy) and [Terms of Service](https://policies.google.com/terms) apply.

**Checkout Widget** makes it easy for Merchants to embed the App into a web store, app or platform to facilitate peer-to-peer blockchain transactions. The Checkout Widget consists of an embed script, react wrapper and various other UX components as described in our developer documents. It also enables Embedded Wallet functionality to allow Merchant and Buyers to create and fund this wallet with an onramp or digital asset transfer within the checkout widget.

**Swaps/Bridges**merchants may choose to enable automated swaps/bridges in the Checkout Widget to receive the digital assets of their choose. Swap are provided entirely by independent third-party providers (including, but not limited to, [Swaps.xyz](https://www.swaps.xyz/) and [Jupiter](https://jup.ag/). The Company does not operate, control, or maintain these services and accepts no responsibility or liability for any loss, damage, or issues arising from their use

**Embedded Wallet(s**) Disclaimer: Embedded Wallets are provided entirely by independent third-party providers (including, but not limited to, [Turnkey](https://www.turnkey.com/) and [Web3Auth](https://web3auth.io/). The Company does not operate, control, or maintain these services and accepts no responsibility or liability for any loss, damage, or issues arising from their use.

Embedded Wallets are self-custody, Smart Contract or ephemeral wallet services integrated into the App through third-party vendors. Merchants and Buyers may generate and use Embedded Wallets inside the Checkout and Deposit widgets, as well as the Dashboard.

By choosing to use an Embedded Wallet, you acknowledge and agree that your relationship regarding any Embedded Wallet is exclusively with the applicable third-party provider, and your use is subject to their terms of service. You agree that you are bound by such terms, which constitute a direct agreement between you and the third-party provider. The Company does not hold, manage, or have access to your assets, funds, or private keys and cannot assist in their recovery, replacement, or safeguarding. You are solely responsible for safeguarding your wallet credentials, passwords, private keys, and any related information, and any loss, theft, unauthorised access, malfunction, or other issues connected to your Embedded Wallet remain entirely your responsibility. The Company makes no representations, warranties, or guarantees, whether express or implied, regarding the suitability, reliability, availability, security, accuracy, or performance of Embedded Wallets or any third-party services. To the fullest extent permitted by law, the Company expressly disclaims all liability arising from or related to your use of any Embedded Wallet or the services of any third-party provider, including Turnkey and Web3Auth. You further agree to indemnify, defend, and hold harmless the Company and its affiliates, directors, officers, employees, and agents from and against any claims, liabilities, damages, losses, and expenses (including reasonable legal fees) arising out of or in connection with your use of any Embedded Wallet, your relationship with any third-party provider (including Turnkey), or your breach of such third-party provider’s terms of service.

**Auto off-ramp** is a service that allows merchants to automatically transfer crypto earnings directly to their bank account of choice through our partner, [Iron.xyz](https://iron.xyz/) . Please refer to Iron.xyz's terms and conditions [here](https://iron.xyz/customer-terms) . Users of Auto off-ramp acknowledge and agree that the use of this service is entirely at their own risk. Any loss, damage, unauthorised access, malfunction, or other issues related to Auto off-ramp and the user's digital assets and funds shall be borne exclusively by the user. The Company will never hold your assets, funds, or private keys and shall not be responsible or liable for the loss, recovery, or compromise of such funds or data. The Company makes no representations, warranties, or guarantees, whether expressed or implied, about the suitability, reliability, availability, accuracy, or completeness of Auto off-ramp. Users acknowledge that Auto off-ramp, offered in collaboration with a third-party software provider, may have inherent risks, including but not limited to technical malfunctions, unauthorised intrusions, and potential vulnerabilities. The Company shall not be liable for any issues arising from the use of the Auto off-ramp service. The Company reserves the right to update or modify the Auto off-ramp service at any time. By using Auto off-ramp, users acknowledge that they have read, understood, and agree to be bound by this provision and by Iron.xyz's terms and conditions.

**Developer Integrations**the Company provides developer tools, APIs, SDKs, and widgets (the “Developer Tools”) that enable merchants and developers to create, customize, and manage blockchain-based payment flows, including Pay Links, Checkout Widgets, Dynamic Links, Subscriptions, and programmatic transaction processing. By using the Developer Tools, you agree to comply with all applicable laws and the Company’s Terms of Service and technical documentation.

You are solely responsible for securing your API keys, webhook endpoints, and any customer or transaction data processed through your integration. The Company does not hold, manage, or access user funds or private keys and is not a party to any transaction created through your integration. All transfers occur directly between the Buyer and Merchant on the blockchain and are final and irreversible.

You acknowledge that your use of third-party services, including wallet providers, swaps, bridges, and off-ramp partners, is governed exclusively by their respective terms. The Company makes no representations or warranties regarding the reliability, availability, or security of such third-party services and disclaims all liability arising from their use.

Developers must ensure that all integrations are properly configured and compliant with applicable laws, including data protection and financial regulations.

**We may make changes to these terms**

We amend these terms from time to time. Every time you wish to use our App, please check these terms to ensure you understand the terms that apply at that time.

**We may make changes to our App**

We may update and change our App from time to time to reflect changes to our products, our users' needs and our business priorities.

**We may suspend or withdraw our App**

Our App is made available free of charge.

We do not guarantee that our App, or any content on it, will always be available or be uninterrupted. We may suspend, withdraw or restrict the availability of all or any part of our App for business and operational reasons. We will try to give you reasonable notice of any suspension or withdrawal.

You are also responsible for ensuring that all persons who access our App through your internet connection are aware of these terms of use and other applicable terms and conditions, and that they comply with them.

**We may transfer this agreement to someone else**

We may transfer our rights and obligations under these terms to another organisation. We will always tell you in writing if this happens and we will ensure that the transfer will not affect your rights under the contract.

**How you may use material on our App**

We are the owner or the licensee of all intellectual property rights in our App and in the material published on it. Those works are protected by copyright laws and treaties around the world. All such rights are reserved.

Some parts of the App are licensed under third-party open-source licences. As for other parts of the App, you may not copy or adapt any portion of our code or visual design elements (including logos) without express written permission from the Company. You may not: (1) access or tamper with non-public areas of the Services, our computer systems, or the systems of our technical providers; (2) access or search the Services by any means other than the currently available, published interfaces (e.g., APIs) that we provide; (3) forge any TCP/IP packet header or any part of the header information in any email or sharing, or in any way use the Services to send altered, deceptive, or false source-identifying information; or (4) interfere with or disrupt, the access of any user, host, or network, including sending a virus, overloading, flooding, spamming, mail-bombing the Services, or by scripting the creation of content or accounts in such a manner as to interfere with or create an undue burden on the Services

You may print off one copy and may download extracts, of any page(s) from our App for your personal use and you may draw the attention of others within your organisation to content posted on our App.

You must not modify the paper or digital copies of any materials you have printed off or downloaded in any way, and you must not use any illustrations, photographs, video or audio sequences or any graphics separately from any accompanying text.

Our status (and that of any identified contributors) as the authors of content on our App must always be acknowledged (except where the content is user-generated).

You must not use any part of the content on our App for commercial purposes without obtaining a licence to do so from us or our licensors.

If you print off, copy, download, share or repost any part of our App in breach of these terms of use, your right to use our App will cease immediately and you must, at our option, return or destroy any copies of the materials you have made.

**No text or data mining, or web scraping**

You shall not conduct, facilitate, authorise or permit any text or data mining or web scraping concerning our App or any services provided via, or about, our App. This includes using (or permitting, authorising or attempting the use of):

Any "robot", "bot", "spider", "scraper" or other automated device, program, tool, algorithm, code, process or methodology to access, obtain, copy, monitor or republish any portion of the App or any data, content, information or services accessed via the same.

Any automated analytical technique aimed at analysing text and data in digital form to generate information which includes but is not limited to patterns, trends and correlations.

The provisions in this clause should be treated as an express reservation of our rights in this regard, including for the purposes of Article 4(3) of the Digital Copyright Directive ((EU) 2019/790).

This clause shall not apply insofar as (but only to the extent that) we are unable to exclude or limit text or data mining or web scraping activity by contract under the laws which apply to us.

**Do not rely on information on this App**

The content on our App is provided for general information only. It is not intended to amount to advice on which you should rely. You must obtain professional or specialist advice before taking, or refraining from, any action based on the content on our App.

Although we make reasonable efforts to update the information on our App, we make no representations, warranties or guarantees, whether express or implied, that the content on our App is accurate, complete or up to date.

**We are not responsible for Apps we link to**

Where our App contains links to other Apps and resources provided by third parties, these links are provided for your information only. Such links should not be interpreted as approval by us of those linked web apps or information you may obtain from them.

We have no control over the contents of those Apps or resources.

**Our responsibility for loss or damage suffered by you**

We exclude all implied conditions, warranties, representations or other terms that may apply to our App or any content on it.

We will not be liable to you for any loss or damage, whether in contract, tort (including negligence), breach of statutory duty, or otherwise, even if foreseeable, arising under or in connection with:

* use of, or inability to use, our App; or
* use of or reliance on any content displayed on our App.

In particular, we will not be liable for:

* loss of profits, sales, business, or revenue;
* business interruption;
* loss of anticipated savings;
* loss of business opportunity, goodwill or reputation; or
* any indirect or consequential loss or damage.

**Which country's laws apply to any disputes?**

If you are a consumer, please note that these terms of use, their subject matter and their formation, are governed by English law. You and we both agree that the courts of England and Wales will have exclusive jurisdiction except that if you are a resident of Northern Ireland you may also bring proceedings in Northern Ireland, and if you are a resident of Scotland, you may also bring proceedings in Scotland.

If you are a business, these terms of use, their subject matter and their formation (and any non-contractual disputes or claims) are governed by English law. We both agree to the exclusive jurisdiction of the courts of England and Wales.

**Our trade and service marks**

You are not permitted to use without our approval, any trade or service marks of Helio Fintech Limited.

# Privacy Policy
Source: https://docs.hel.io/docs/privacy-policy

Effective Date: 28 January 2026

**MoonPay Commerce Global Privacy Notice for End Users**

This Privacy Notice explains how MoonPay Commerce, operated by Helio Fintech Limited, processes personal data when you interact with a merchant’s MoonPay Commerce Checkout Interfaces. In these scenarios, the merchant is the controller of your personal data and MoonPay Commerce acts solely as a processor on the merchant’s instructions. This Privacy Notice applies to End Users of Merchants that use MoonPay Commerce to facilitate transactions. It does not apply to business customers or Merchants. Business customers and merchants should consult MoonPay’s Global Privacy Policy available at: [https://www.moonpay.com/legal/privacy\_policy](https://www.moonpay.com/legal/privacy_policy).

**Who We Are**

MoonPay Commerce is operated by Helio Fintech Limited, a wholly owned subsidiary of MoonPay Inc. Helio Fintech Limited is registered in England and Wales (company number 13836904) with its registered office at 16 Great Queen Street, Covent Garden, London, United Kingdom, WC2B 5AH. For data protection inquiries, please contact MoonPay’s Data Protection Officer at [\[email protected\]](/cdn-cgi/l/email-protection#f2b6a2bdb2bf9d9d9ca2938bdc919d9f).

**Definitions**

The following terms are used in this Privacy Notice:

* **End User** means an individual who uses a Merchant’s Checkout Interfaces to purchase goods, services, or digital content from the Merchant.
* **Merchant** means the business customer that integrates MoonPay Commerce Checkout Interfaces and determines the purposes and means of processing End User personal data for the associated transactions.
* **Checkout Interfaces** means the MoonPay Commerce user interfaces that enable transactions, including the Checkout Widget embedded by a Merchant and hosted checkout pages such as Pay Links.
* **Services** means the MoonPay Commerce services that facilitate direct, peer‑to‑peer transactions on decentralized blockchains, as described in the MoonPay Commerce Terms of Service.
* **MoonPay Group** means Helio Fintech Limited, MoonPay Inc., and their affiliates.

**Scope and Roles**

This Privacy Notice applies when you interact with a Merchant’s Checkout Interfaces powered by MoonPay Commerce on the Merchant’s website, application, or other channel. In these circumstances, the Merchant acts as the data controller and MoonPay Commerce as the processor. The Merchant determines which personal data are collected from you and the purposes for which those data are used, including order fulfillment and customer support. MoonPay Commerce processes End User personal data only on the Merchant’s documented instructions and does not determine the purposes or essential means of processing End User data.

**Personal Data Processed on the Merchant’s Instructions**

The specific personal data that are processed depend on the Merchant’s configuration and integration. Typical categories that a Merchant may require MoonPay Commerce to process in order to facilitate a purchase include the following.

* Checkout data provided by you or automatically through the transaction, including wallet address, transaction amount and currency, and any other buyer or order details the Merchant requires, which may include name, email address, billing address, and shipping address.
* Transaction and blockchain data generated from the transaction, including transaction identifiers, timestamps, wallet addresses, and on‑chain confirmations required to verify payment and trigger fulfillment.
* Technical and usage data necessary to operate and secure the Checkout Interfaces, including IP address, device and browser information, product usage, and diagnostic logs.
* Support communications and related metadata associated with a Checkout session initiated with the Merchant. MoonPay Commerce does not require special categories of personal data for Checkout Interfaces and does not seek to collect such data.

**How MoonPay Commerce Uses Personal Data**

MoonPay Commerce uses End User personal data only on the Merchant’s documented instructions and only for purposes such as operating the Checkout Interfaces, confirming blockchain transactions, enabling order fulfillment, maintaining security and service integrity, fraud monitoring as requested by the Merchant, and providing support to the Merchant related to a Checkout session. MoonPay Commerce may generate de‑identified or aggregated operational metrics that do not identify individuals to support platform reliability and performance. MoonPay Commerce does not use End User personal data from merchant checkouts for MoonPay’s own independent marketing or profiling.

**Sharing and Disclosures**

MoonPay Commerce shares End User personal data only as necessary to provide the Services on the Merchant’s behalf or as required by law. Personal data processed by MoonPay Commerce may be shared as described below.

* With the Merchant that controls your personal data, including relevant order, transaction, and support details to enable fulfillment and customer service.
* With authorized sub‑processors that provide hosting, security, analytics, and customer support. These providers process personal data under written contracts that require confidentiality, security, and processing only on MoonPay Commerce’s instructions.
* With competent authorities when required to comply with applicable laws, valid legal requests, or to protect the rights, safety, and security of users, the Merchant, or the Services.
* On public blockchains. When you make a crypto payment, certain transaction data, including wallet addresses, amounts, timestamps, and transaction identifiers, are recorded on public blockchains that are not controlled by MoonPay Commerce nor the Merchant.

**International Data Transfers**

MoonPay Commerce is based in the United Kingdom and relies MoonPay Group infrastructure and subprocessors that may be located outside the UK. When personal data is transferred internationally, MoonPay Commerce implements appropriate safeguards, including the UK International Data Transfer Addendum, the corresponding EU Standard Contractual Clauses, or other legally recognized transfer mechanisms, together with technical and organizational measures such as encryption in transit and at rest where appropriate.

**How We Protect and Store Personal Data**

MoonPay Commerce maintains technical and organizational measures designed to protect personal data, including network and application security controls, encryption, access controls based on least privilege, audit logging, and workforce training. MoonPay Commerce regularly assesses and improves controls to align with industry standards.

**Retention**

As a processor, MoonPay Commerce retains End User personal data in accordance with the Merchant’s instructions and the applicable agreement with the Merchant. Retention supports operation of the Checkout Interfaces, order fulfillment, security, service integrity, and compliance with legal obligations and dispute resolution. When personal data is no longer required for these purposes, MoonPay Commerce deletes or anonymizes the data consistent with the Merchant’s instructions and MoonPay Commerce’s retention schedules. For specific data retention schedules applicable to your personal information please contact the Merchant for details regarding their policies.

**Cookies and Similar Technologies**

The Checkout Interfaces may use cookies, SDKs, and similar technologies to operate, secure, and measure the checkout experience, including to maintain session state and detect fraud. The specific technologies depend on the Merchant’s integration and your device or browser settings. For additional information about MoonPay’s use of cookies, see MoonPay’s Cookie Policy at: [https://www.moonpay.com/legal/cookie\_policy](https://www.moonpay.com/legal/cookie_policy).

**Your Privacy Rights and How to Exercise Them**

Because the Merchant is the controller of your checkout data, your rights under the UK GDPR or local data protection laws, including rights of access, rectification, erasure, restriction, portability, and objection, should be exercised directly with the Merchant. MoonPay Commerce will coordinate directly with the Merchant to provide any support that is required to fulfill the request as required by contract and applicable law. To exercise your rights, contact the Merchant that provided the Checkout Interfaces.

**Legal Bases**

The Merchant determines the lawful basis for processing your personal data and is responsible for providing you with the required transparency information under applicable law. MoonPay Commerce processes your personal data on the Merchant’s documented instructions under a data processing agreement that satisfies Article 28 of the UK GDPR.

**Children’s Data**

The Checkout Interfaces are not directed to individuals under the age of 18. If you believe that a person under the age of 18 has provided personal data in connection with a checkout, please contact the Merchant. MoonPay Commerce will assist the Merchant in taking appropriate steps.

**Complaints and Contact Information**

For questions about how your personal data are handled in connection with a checkout, or to exercise your data protection rights, please contact the Merchant as the data controller. You may also contact MoonPay’s Data Protection Officer at [\[email protected\]](/cdn-cgi/l/email-protection#7d190d123d101212130d1c04531e1210) for data protection inquiries specifically relating to MoonPay Commerce. You have the right to lodge a complaint with the UK Information Commissioner’s Office or your local data protection authority related to any data protection concerns.

**Sub‑Processors**

MoonPay Commerce maintains agreements with Merchants that include processor obligations required by applicable law which ensure equivalent obligations to authorized sub‑processors. MoonPay Commerce engages authorized sub-processors for essential service functions including cloud hosting and infrastructure, security and fraud monitoring, technical and product analytics, and customer support.

**Changes to This Privacy Notice**

MoonPay Commerce may update this Privacy Notice to reflect changes in the Services or applicable law. If changes materially affect how End User personal data are processed, MoonPay Commerce will update this notice as needed. The effective date appears at the top of this notice.

# NFT Purchase Terms & Conditions
Source: https://docs.hel.io/docs/nft-purchase-terms-conditions

Name Change Notification

As of the 21st of September, 2023, the non-fungible token (NFT) previously known as “Helion” (plural “Helions”) has been officially renamed to “HelioX Pass” (plural “HelioX Passes”). All references to “Helion” or “Helions” in this document and any associated materials or communications should be understood to refer to “HelioX Pass” or “HelioX Passes” respectively, from the date of this change onwards. This name change does not affect the rights, responsibilities, or obligations outlined in these Terms and Conditions.

***

These Terms constitute a legally binding agreement between Helio Fintech Ltd (“Helio”) and: (i) you as a participant in the Helions Sale (defined below); and (ii) any subsequent owner(s) of a Helion (defined below) (collectively and as applicable, “You” and “Your”). Each of You and Helio is a “Party”, and together the “Parties”. By purchasing Helions during the Sale Period (as defined below), you will be bound by these NFT Purchase Terms and Conditions (the “Terms”) and all terms incorporated by reference.

### 1. Definitions

(a) “Helion” (plural “Helions”) means a unique non-fungible token (an “NFT”) that, as of its genesis issuance, is linked to a display of Underlying Art and which represents pieces of programmable arts in the form of non-fungible digital assets that themselves may be created by reference to a smart contract on the Solana blockchain.

(b) “Helion Sale” means each sale hosted on the Marketplace Website during the Sale Period.

(c) “Marketplace Website” means Magic Eden

(d) “Primary Transaction” means a transaction in which a Helion is first sold.

(e) “Prohibited Transferee” means an individual (i) located in a country that is subject to a government embargo, or that has been designated by a Government as a terrorist-supporting country; or is (ii) listed on any government list of prohibited or restricted parties.

(f) “Sale Period” means the dates on which the Primary Transactions shall occur, beginning on September 22, 2022 and ending on September 22, 2022.

(g) “Secondary Transaction” means any transaction in which a Helion is sold by one owner to another or is otherwise transferred in any manner that is not a Primary Transaction.

(h) “Underlying Art” means the digital art provided by and owned by Helio and linked to the Helions. To avoid doubt, the Underlying Art is digital and does not include any items or representations with physical dimensions such as mass or volume.

### 2. Purpose and Use of Helions

Helions aim to provide holders with benefits related to the Helio platform ([www.hel.io](http://www.hel.io)). For example, Helions holders may be entitled to access HelioX (Helio’s pro version) and to participate in the benefits of Helions DAO. The details of these benefits will be determined by Helio at its discretion and will be communicated to holders of the Helions via the Helio website and in Discord. The Helions and any additional benefits related to it are not intended to be a digital currency, security, commodity, or any other financial instrument. If there is any inconsistency between the information on the Helio website and the information in the Terms of Service, the Terms of Service prevail/control.

### 3. Agreement to Terms

By participating in the Helions Sale, You acknowledge that You have carefully read and agree to the terms contained herein. The Terms govern Your participation in any Primary Transactions and Secondary Transactions. Helio’s failure to exercise or enforce any right or provision of these Terms will not operate as a waiver of such right or provision. Helio will not be liable for any delay or failure to perform any obligation under these Terms where the delay or failure results from any cause beyond its reasonable control. Purchasing Helions from Helio does not create any form of partnership, joint venture, or similar relationship between You and Helio. Except as otherwise provided herein, these Terms are intended solely for the benefit of You and Helio. They are not intended to confer third-party beneficiary rights upon any other person or entity. You agree and acknowledge that all agreements, notices, disclosures, and other communications Helio provide to You, including these Terms, will be provided in electronic form.

You further acknowledge that You have carefully read and have accepted the (i) Terms of Service of the NFT platform of Magic Eden.

Helio reserves the right, at its sole discretion, to modify, amend, or update these Terms at any time, including for legal, regulatory, technical, business, or operational reasons. Any such modifications will be effective immediately upon posting the revised Terms at [www.hel.io](http://www.hel.io), unless otherwise stated.

By continuing to hold, use, or transfer HelioX Passes (formerly Helions) after any amendments become effective, You agree to be bound by the revised Terms. If You do not agree to the amended Terms, Your sole remedy is to cease using and/or transferring Your HelioX Passes.

### 4. The Helion Sale and Secondary Transactions

(a) Purchaser Qualification: By purchasing Helions, You represent and warrant that: (i) You have read and understood these Terms; (ii) You have sufficient understanding of the functionality, usage, storage, transmission mechanisms and other material characteristics of cryptographic tokens, token storage mechanisms (such as token wallets), blockchain technology and blockchain-based software systems to understand these Terms and to appreciate the risks and implications of purchasing the Helions; (iii) You have obtained sufficient information about the Helions to make an informed decision to purchase the Helions; (iv) You understand that the Helions confer no rights of any form concerning Helio or its corporate affiliates, including, but not limited to, any voting, distribution, redemption, liquidation, proprietary (including all forms of intellectual property), or other financial or legal rights; (v) You are purchasing Helions for your own personal, non-commercial use. You are not purchasing Helions for any other uses or purposes, including, but not limited to, any investment, speculative or other financial purposes; (vi) Your purchase of Helions complies with applicable law and regulation in Your jurisdiction; (vii) You will comply with any applicable tax obligations in Your jurisdiction arising from Your purchase of Helions; (viii) If You are purchasing Helions on behalf of any entity, You are authorised to accept these Terms on such entity’s behalf and that such entity will be responsible for breach of these Terms by You or any other employee or agent of such entity (references to “You” in these Terms refer to You and such entity, jointly); and

(b) Purchases: During the Helions Sale, You can purchase Helions made available on the Marketplace Website. You will be required to connect Your Solana wallet to the Marketplace Website Platform to buy Helions. Your purchase of Helions from Helio during the Sale Period is final, and there are no refunds or cancellations except as may be required by applicable law or regulation. We reserve the right to refuse or cancel Helions purchase requests at any time at our sole discretion.

(c) Form of Payment: The Marketplace Website agrees to accept payment for the Primary Transaction purchase price in Solana cryptocurrency via the Marketplace Website through a Solana Wallet of choice, provided that the Marketplace Website may elect to accept other methods or forms of payment in its sole discretion. The U.S. dollar exchange rate for any other forms of payment shall be determined solely by Helio, the Marketplace Website, or an assignee or agent in accordance with reasonable and accepted market practices, and additional transaction fees may apply. Before placing Your order, correct exchange rate information will be shared.

(d) Fees: By buying or selling Helions on the Marketplace Website or any other platform, You agree to pay all applicable fees and, if applicable, You authorise the Marketplace Website to automatically deduct fees (including any transaction fees as applicable) directly from Your payments for the Primary Transaction or subsequent Secondary Transactions. Neither Helio nor the Marketplace Website have any insight into or control over these payments or transactions, nor does Helio or the Marketplace Website have the ability to reverse any transactions. Accordingly, Helio and the Marketplace Website will have no liability to You or any third party for any claims or damages that may arise from any transactions of the Helions that You engage in.

(e) Transfers: All Secondary Transactions are subject to the following terms: (i) the Helion transferee shall, by receiving an ownership interest in the Helion, be deemed to accept all of the terms found in these Terms; (ii) the Helion transferor shall provide notice to the transferee of the Terms, including a link or other method by which the terms of these Terms can be accessible by the transferee.

(f) Transfer Timing: Helio anticipates that delivery of Helions from the Marketplace Website to purchasers will occur within one week after the Sale Period concludes, and likely much faster, but reserves the right to delay delivery up to four weeks after the conclusion of the Sale Period. Although Helio does not anticipate any security issues arising from the sale of Helions, this timeframe is intended as a precautionary buffer period for Helio to resolve any such security issues.

(g) Taxes: The purchase price that You pay for Helions is exclusive of all applicable taxes. You are responsible for determining what, if any, taxes apply to Your purchase of Helions, including, for example, sales, use, value-added, and similar taxes. You are also responsible for withholding, collecting, reporting, and remitting the correct taxes to the appropriate tax authorities. Helio is not responsible for withholding, collecting, reporting, or remitting any sales, use, value-added, or similar tax arising from Your purchase of Helions.

(h) Your Information: Helio may determine, in its sole discretion, that it is necessary to obtain certain information about You to comply with applicable law or regulation in connection with selling Helions to You. You agree to provide Helio such information promptly upon request, and You acknowledge that Helio may refuse to sell Helions to You until You provide such requested information and Helio has determined that it is permissible to sell You Helions under applicable law or regulation. Helio reserves the right to publish transaction information of Helions NFT sales.

### 5. Ownership of Helions

As a purchaser of Helion, You own a cryptographic token representing the Underlying Artwork’s creative artwork as a piece of property, but You do not own the creative artwork itself. If You acquire a Helion, You acquire all personal property rights to that Helion, such as the right to freely sell, transfer, or otherwise dispose of that Helion. However, in exercising personal property rights over the Helion, You represent and warrant that You will not transfer a Helion in any Secondary Transaction to a transferee that is a Prohibited Transferee. Purchasers of Helions do not have any legal ownership, right, or title to any copyrights, trademarks, or other intellectual property rights to the Underlying Art, except the limited license granted by the Terms.

### 6. License of Underlying Art

Helio reserves all exclusive copyrights to artworks underlying NFTs on the Marketplace Website, including but not limited to the right to reproduce, prepare derivative works, display, perform, and distribute the artworks. Purchasers may not infringe on any of the exclusive rights of the copyright belonging exclusively to Helio. If You acquire a Helions, Helio hereby grants to You, for so long as You own the Helions (as recorded on the relevant blockchain), a non-exclusive, non-sublicensable, royalty-free license to use, copy, and display the Underlying Art linked with Your purchased Helions solely for the following purposes: (i) for Your own personal, non-commercial use, including to create one back-up copy of the Underlying Art and a single physical print out of the Underlying Art, each to be retained only for so long as You own the associated Helions; and (ii) efforts to sell or otherwise transfer the associated Helions consistent with the ownership of it (e.g., posting the Underlying Art on a sales listing on an NFT marketplace). The license in the prior sentence is non-transferable, except that it will automatically transfer in connection with the transfer of the Helions.

### 7. Reservation of Rights

The Underlying Art is licensed, not sold. All rights to the Underlying Art are not expressly provided for in the Terms and are hereby reserved by Helio. Helio owns and will retain all title, interest, ownership rights and intellectual property rights in and to the Underlying Art. Without limitation, You shall not, nor permit any third party to do or attempt to do any of the following without express prior written consent from Helio: (i) modify the Underlying Art; (ii) use the Underlying Art to advertise, market, or sell any product or service; (iii) use the Underlying Art in connection with media that depicts hatred, intolerance, violence, cruelty, or any other subject matter that reflects negatively on Helio; (iv) use the Underlying Art in any other form of media, except solely for Your own personal, non-commercial use for so long as You own the Helion; (v) sell, distribute for commercial gain (including, without limitation, giving away in the hopes of eventual commercial gain), or otherwise commercialize merchandise that includes, contains, or consists of the Underlying Art; (vi) attempt to register any trademark, copyright, or otherwise acquire additional intellectual property rights in or to the Underlying Art; or (vii) otherwise utilize the Underlying Art for Your or any third party’s commercial benefit.

### 8. Termination of License to Underlying Art

Your license to the Underlying Art shall automatically and immediately terminate without notice, and all rights shall revert to Helio if at any time: (i) You breach any portion of this Agreement; (ii) You engage in any unlawful activity related to the Helions (including transferring the Helions to a Prohibited Transferee); or (iii) at Helio’s sole determination and discretion, You disparage Helio, or their brands or products. Upon any termination, discontinuation, or cancellation of Your license to Underlying Art, Helio may disable Your access to the Underlying Art, and You must delete, remove, or otherwise destroy any backup or single digital or physical copy of the Underlying Art.

### 9. Warranty Disclaimers

To the fullest extent permitted by applicable law and except as otherwise specified in writing by Helio, (a) the Helions are sold on an “as is” and “as available” basis without warranties of any kind, and Helio expressly disclaim all implied warranties as to the Helions, including, without limitation, implied warranties of merchantability, fitness for a particular purpose, title and non-infringement; (b) Helio does not represent or warrant that the Helions are reliable, current or error-free, meet your requirements, or that defects in the Helions will be corrected; and (c) Helio cannot and does not represent or warrant that the Helions or the delivery mechanism for Helions are free of viruses or other harmful components.

### 10. Assumption of Risks

Please note the following risks in accessing, purchasing, selling, or using Helions: The price and liquidity of blockchain assets, including Helions, can be extremely volatile and may be subject to large fluctuations. Fluctuations in the price of other digital assets could materially and adversely affect Helions, which may also be subject to significant price volatility. Legislative and regulatory changes or governmental actions at local or international level may adversely affect the use, transfer, exchange, and value of Helions. Helions are not legal tender and are not backed by any government. Transactions of Helions may be irreversible, and, accordingly, losses due to fraudulent or accidental transactions may not be recoverable. Some Transactions of Helions shall be deemed to be made when recorded on a public ledger, which is not necessarily the date or time that you initiated the transaction. The value of Helions may be derived from the continued willingness of market participants to exchange fiat currency or digital assets for Helions, which may result in the potential for permanent and total loss of value of a particular Helion. You agree and understand that you are solely responsible for determining the nature, potential value, suitability, and appropriateness of these risks for yourself and that Helio do not give advice or recommendations regarding Helions, including the suitability and appropriateness of, and investment strategies for, Helions. You agree and understand that you access and use Helions at your own risk; however, this brief statement does not disclose all of the risks associated with Helions and other digital assets. You agree and understand that Helio will not be responsible for any communication failures, disruptions, errors, distortions or delays you may experience when using Helions, however caused. There are risks associated with purchasing and holding digital assets. Loss of the full amount of the purchase price is possible. Volatility is highly likely, and some of the protocols and platforms may fail entirely due to forking, flaws in the code, hacking or other malicious attacks.

### 11. Indemnification

To the fullest extent permitted by applicable law, You will indemnify, defend and hold harmless Helio and our respective past, present and future employees, officers, directors, contractors, consultants, equity holders, suppliers, vendors, service providers, parent companies, subsidiaries, affiliates, agents, representatives, predecessors, successors and assigns (the “Helio Parties”) from and against all claims, demands, actions, damages, losses, costs and expenses (including attorneys’ fees) that arise from or relate to: (i) Your purchase or use of Helions, (ii) Your responsibilities or obligations under these Terms, (iii) Your violation of these Terms, or (iv) Your violation of any rights of any other person or entity.

### 12. Limitation of Liability

To the fullest extent permitted by applicable law: (i) in no event will Helio or any of the Helio parties be liable for any indirect, special, incidental, consequential, or exemplary damages of any kind (including, but not limited to, where related to loss of revenue, income or profits, loss of use or data, or damages for business interruption) arising out of or in any way related to the sale or use of Helions or otherwise related to these Terms, regardless of the form of action, whether based in contract, tort (including, but not limited to, simple negligence, whether active, passive or imputed), or any other legal or equitable theory (even if the party has been advised of the possibility of such damages and regardless of whether such damages were foreseeable); and (ii) in no event will the aggregate liability of Helio, whether in contract, warranty, tort (including negligence, whether active, passive or imputed), or other theory, arising out of or relating to these Terms or the use of or inability to use Helions, exceed the amount you pay to us for the Helions.

### 13. Release

To the fullest extent permitted by applicable law, You release Helio from responsibility, liability, claims, demands and/or damages (actual and consequential) of every kind and nature, known and unknown (including, but not limited to, claims of negligence), arising out of or related to disputes between users and the acts or omissions of third parties.

### 14. Governing Law

These Terms are governed by United Kingdom law. You agree that any suit arising from these Terms must take place in a court located in the United Kingdom.

### 15. Dispute Resolution

(i) Informal Resolution of Disputes: You and Helio must first attempt to resolve any dispute, claim, or controversy arising out of or relating to these Terms or the breach, termination enforcement, interpretation, or validity thereof of the purchase of Helions (collectively, “Disputes”) informally. Accordingly, neither you nor Helio may start a formal arbitration proceeding for at least sixty (60) days after one party notifies the other party of a claim in writing. As part of this informal resolution process, you must deliver your written notices via hand or first-class mail to us at Helio Fintech Ltd., 16 Great Queen Street, WC2B 5AH, London/UK (ii) Mandatory Arbitration of Disputes: We each agree that any Dispute will be resolved solely by binding, individual arbitration and not in a class, representative or consolidated action or proceeding. You and Helio agree that The UK Arbitration Act (1996) governs the interpretation and enforcement of these Terms and that you and Helio are each waiving the right to a trial by jury or to participate in a class action. This arbitration provision shall survive termination of these Terms. (iii) Exceptions: As limited exceptions to the above: (i) we both may seek to resolve a Dispute in small claims court if it qualifies; and (ii) we each retain the right to seek injunctive or other equitable relief from a court to prevent (or enjoin) the infringement or misappropriation of our intellectual property rights. (iv) Conducting Arbitration and Arbitration Rules: The arbitration will be conducted by the London Court of International Arbitration (“LCIA”) under its Arbitration Rules (the “LCIA Arbitration Rules”) then in effect, except as modified by these Terms. The LCIA Arbitration Rules are available at [www.lcia.org](http://www.lcia.org). A party who wishes to start arbitration must submit a written Demand for Arbitration to LCIA and give notice to the other party as specified in the LCIA Rules. (v) Class Action Waiver: YOU AND HELIO AGREE THAT EACH MAY BRING CLAIMS AGAINST THE OTHER ONLY IN YOUR OR ITS INDIVIDUAL CAPACITY, AND NOT AS A PLAINTIFF OR CLASS MEMBER IN ANY PURPORTED CLASS OR REPRESENTATIVE PROCEEDING. Further, suppose the parties’ Dispute is resolved through arbitration. In that case, the arbitrator may not consolidate another person’s claims with your claims and may not otherwise preside over any form of a representative or class proceeding. If this specific provision is unenforceable, then the entirety of this Dispute Resolution section shall be null and void. ‍

### 16. General Terms

These Terms constitute the entire agreement between You and Helio relating to Your purchase of Helions from Helio. Our failure to exercise or enforce any right or provision of these Terms will not operate as a waiver of such right or provision. Helio will not be liable for any delay or failure to perform any obligation under these Terms where the delay or failure results from any cause beyond our reasonable control. Purchasing Helions from Helio does not create any form of partnership, joint venture or any other similar relationship between You and Helio. You agree and acknowledge all agreements, notices, disclosures, and other communications. Helio provides to You, including these Terms, will be provided in electronic form.

### 17. Contact Information

If You have any questions about these Terms, please contact Helio at [\[email protected\]](/cdn-cgi/l/email-protection#d5bdb0b9a595bdb0b9fbbcba)