Accept a payment
Start with a link or copied button for the smallest integration. For a custom application, the payment reference includes a typed SDK example: create checkout from your trusted order, display the existing secure card form, then confirm the exact recipient, amount and recorded credit before delivery. Keep the returned session against the order so closing a tab does not create a second payment. The Get paid guide explains setup without code; the implementation reference shows the complete developer lifecycle.
Start from the pinned version
This reference implementation uses Receiz v129 SDK, MCP and AI Skills. Read the corresponding schemas and primitive contracts before adding an action. A package version identifies source compatibility; it does not prove the selected live host has deployed every capability.
Go beyond checkout
Compose account payments, current Notes, asset ownership and original receipts through their existing Receiz contracts. The payment reference maps subscriptions, refunds, tax, shipping, discounts, inventory, fulfillment and payouts to the coordinated commerce surfaces, and identifies the scopes and host support each requires. MCP and AI Skills provide their supported agent workflows. Start with one operation and add capabilities without building a second payment ledger or granting an agent blanket financial authority.
Use the right surface
The SDK composes application operations. MCP and AI Skills expose their supported tools and workflows. They do not imply interchangeable permissions or license an agent to perform arbitrary financial actions. Keep the account identity, granted scope and action authorization explicit.
Retain exact sources
Keep original bytes, identity bindings, predecessor references and signed results. A projection is for presentation. It must not become a new authority simply because it is easier to read than the proof. Unknown or unsupported data fails within its declared boundary.
Recover the same operation
Persist the exact attempted action before consequential submission. After an uncertain response, query or resume that operation before considering another. Bind recipient, amount, quote, funding split and identity across recovery. Never clear unknown financial state to make a retry appear fresh.
Fast presentation, deliberate execution
Reuse held observations and deduplicated readers for immediate display. Synchronize in the background where supported. Avoid extra polling or fetching a second copy of already retained evidence. Consequential execution still validates current authority and state; latency goals cannot weaken those checks.
Test the boundary
Use reference fixtures for pure verification, adapter tests for source selection and execution, and real devices for physical custody claims. Publish negative results and deployment limits. The source archive, schemas and institution receiver provide concrete starting points for independent inspection.
Method, sources and assessment
This explanation describes the supported implementation. Exact protocol requirements come from the pinned Receiz contracts and original sources. A reference result does not qualify a production deployment or a physical device.