.
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.
WARNING
These are planned components. No GetPaid settlement rail or oracle integration is deployed, audited, or live.
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.