Settlement Contract
Payments and offline notes settle through one deterministic custody model so posted value can be replayed, audited, and attested without ambiguity.
Receiz/Payments/Account Settlement
Payments
Take payment without breaking the record.
Where payment starts does not break the record, the proof trail, or the payout history.
Card checkout and note-backed payment resolve replayably on one settlement contract.
Integration Surface
Merchants and creators use USD-facing embeds, while settlement integrity stays machine-verifiable through canonical tuple fields and ledger proofs.
What it closes
What ordinary payment stacks split apart
Front door to settlement
Live Twin, profile, or embed can move directly into settlement without handing the thread off to a disconnected payment product.
Deposit and invoice motion
Deposits, payment requests, and note-backed confirmations stay attached to the same branded surface that qualified the work.
Paid releases and note lanes
Drops, commissions, paid access, and uploaded payment notes keep authorship, proof, and settlement continuity intact.
Ops-grade reconciliation
Wallet state, public ledger history, note lanes, and automation can all resolve from the same settlement contract instead of stitched reports.
Same system
Payment stays on the same record, contract, and proof trail as verification, identity, automation, and developer routes.
Get paid from wherever demand starts
Your profile, Live Twin, or site can take payment without sending people into a disconnected checkout flow.
Keep online and offline payment on one trail
Card checkout and uploaded payment notes land inside the same payment trail instead of splitting processor flow from offline proof.
Land payment in the right account
Successful payment settles into the target Receiz account with a replayable balance trail instead of disappearing into processor state.
Keep proof after the payment
Payment history, uploaded notes, and public wallet evidence stay clear for operators, automation, and later scrutiny.
Quick Embed Builder
Enter a username, copy the snippet, and verify the live widget render without leaving this page.
Public mode active. Enter any valid Receiz username.
Use `a-z`, `0-9`, and `_` only (3-24 chars).
<div class="receiz-pay-embed" data-username="your_receiz_username"></div> <script src="https://receiz.com/receiz-pay-embed.js" async></script>
Preview is collapsed. Click copy to open live sample.
Guardrails
- Set one canonical Receiz username per widget instance to keep settlement routing deterministic.
- Card checkout runs on Receiz infrastructure; successful payments settle into the target Receiz account.
- Treat embed endpoints as public-facing surfaces and monitor usage/rate behavior in production.
- Use `/wallet` and `/api/wallet/ledger/public` for settlement visibility and reconciliation.
- Use delegated Connect routes when you need user-authenticated and scope-governed payment operations.
Public Endpoint Contract
POSTNo AuthBoth
/api/payments/embed/checkout
Create embedded or hosted checkout sessions that settle directly to a target Receiz username wallet.
POSTNo AuthBoth
/api/payments/embed/note-claim
Accept uploaded note artifacts (or note tokens) and claim value directly into a target Receiz username wallet.
Checkout Session Example
curl -X POST https://receiz.com/api/payments/embed/checkout \
-H "content-type: application/json" \
-d '{"username":"your_receiz_username","amountUsd":"39.00"}'Note Claim Example
curl -X POST https://receiz.com/api/payments/embed/note-claim \ -F "username=your_receiz_username" \ -F "file=@payment-note.receiz"
Launch Path
Move from embed to production operations.
Start with no-auth website embeds. When your flow needs delegated user actions, layered permission scopes, or system-to-system controls, graduate to Receiz Connect endpoints.
Public embed contract active