Receiz/Payments/Account Settlement

Payments

Embed checkout and note-claim settlement into any website.

Receiz Payments is the public account-settlement embed surface. Add one snippet and accept hosted card checkout plus note claims without running your own payment backend.

Receiz is a deterministic verification-and-settlement platform: original bytes are authoritative for verification, replayable ledger math is authoritative for settlement, and every trust claim is mapped to code and evidence artifacts.

Settlement authority is append-only ledger replay over persisted integer value fields and deterministic rate math.

Institutional core: one deterministic custody unit across ledger posting, replay, and offline note settlement. Approachable edge: USD-first account UX with explicit field-level SLU compatibility for integrators.

Institutional Core

Payments and offline notes settle through one deterministic custody model so posted value can be replayed, audited, and attested without ambiguity.

Approachable Edge

Merchants and creators use simple USD-facing embeds, while settlement integrity stays machine-verifiable through canonical tuple fields and ledger proofs.

Open Embed BuilderAccount Settlement WalletDevelopersTransfer Runbook

Any Website

Drop one snippet into static HTML, Webflow, Squarespace, Notion sites, and custom frameworks.

Card Checkout

Launch hosted checkout sessions with no card-data handling in your own frontend or backend.

Note Claims

Accept uploaded payment notes and settle value directly to the target Receiz account.

Account Settlement

Every successful checkout and claim settles into your `/wallet` account with deterministic ledger continuity.

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.
  • 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 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.

Open Embed BuilderConnect GuideAccount Settlement
Public embed contract active