> 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/technical-architecture/settlement-and-oracle.md).

# Settlement & Oracle

Covers proposed settlement rails for native assets, stablecoins, stock tokens, and offramps, with Chainlink-based stock-token price context.

GetPaid proposes multiple payout assets and a separate stock-token pricing layer. Settlement concerns how payouts move. The oracle concerns stock-token price context.

{% hint style="warning" %}
These are planned components. No GetPaid settlement rail or oracle integration is deployed, audited, or live.
{% endhint %}

### Settlement

The proposed settlement design supports several payout rails rather than one universal asset.

| Rail            | Proposed approach                                                                                |
| --------------- | ------------------------------------------------------------------------------------------------ |
| USDG            | Native on Robinhood Chain, intended for instant settlement and gasless transfer through EIP-3009 |
| Stock tokens    | Direct transfer with no conversion                                                               |
| ETH / BNB / SOL | Native transfer                                                                                  |
| X Money         | Optional bonus rail, conditional on API availability                                             |
| Bank            | External offramp fallback through MoonPay or Banxa                                               |

X Money is US-only, and no public API is available. It is therefore not a core dependency of the proposed design.

Custody, conversion logic, redemption systems, issuer architecture, compliance systems, banking integration, and payment-processor architecture remain subject to final specification.

### Oracle

The proposed design uses a Chainlink-based stock-token pricing layer. It is intended to provide price context for stock-token payouts.

| Component      | Proposed design                   |
| -------------- | --------------------------------- |
| Pricing source | Chainlink stock-token price feeds |
| Example assets | NVDA, AAPL, HOOD                  |
| USDG reference | Presented as $1                   |
| Intended use   | Stock-token payout context        |

Chainlink pricing and payout settlement are separate concerns. Pricing provides token value context. Settlement describes the planned transfer rail.

Aggregation, heartbeats, deviation thresholds, fallback oracles, validation, keeper architecture, update frequency, on-chain interfaces, and circuit breakers will be further specified as the resolution layer moves toward implementation.


---

# 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/technical-architecture/settlement-and-oracle.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.