> For the complete documentation index, see [llms.txt](https://whitepaper.getpaid.family/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.getpaid.family/multi-chain-and-multi-rail/multi-rail.md).

# Multi-Rail

Describes proposed settlement rails for creators receiving routed fees in USDG, stock tokens, native assets, or optional external payout paths.

GetPaid’s proposed design supports multiple settlement rails for routed creator fees. It avoids forcing every creator into one payout asset or path.

```
Trading Fee
    ↓
GetPaid
    ↓
Choose Settlement Rail
├── USDG
├── Stock Token
├── ETH / BNB / SOL
└── Optional external payout paths
```

### Proposed rails

| Rail          | Intended role              | Proposed approach                                                                                 |
| ------------- | -------------------------- | ------------------------------------------------------------------------------------------------- |
| USDG          | Core payout rail           | Native on Robinhood Chain, with instant-settlement and gasless-transfer concepts through EIP-3009 |
| Stock tokens  | Asset-native payout        | Direct transfer without conversion                                                                |
| ETH, BNB, SOL | Native asset payout        | Transfer in the relevant native asset                                                             |
| X Money       | Optional bonus payout rail | Conditional on API availability                                                                   |
| Bank offramp  | External fallback          | Conversion or payout through MoonPay or Banxa                                                     |

X Money is not a core dependency. It is US-only, and no public X Money API is available.

### Why multiple rails

Creators and ecosystems may prefer different assets or payout paths. The proposed architecture is designed to accommodate those preferences while keeping fee routing separate from settlement selection.

{% hint style="warning" %}
All rails are proposed. GetPaid remains pre-testnet, with no deployed, audited, or live payout rails.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

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

```
GET https://whitepaper.getpaid.family/multi-chain-and-multi-rail/multi-rail.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

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