Scope note
Worked Profile — USDC to Złoty
The concrete profile
A maker wants PLN in a compatible Polish bank account and posts an exact USDC quantity. This is the Architecture of Record's concrete worked profile, not a hardcoded FiatOfferV1 pair. The offer commits expected PLN in grosze, one of the admitted instant-rail templates, the recipient, offer lifetime, launch notary key, per-offer exposure cap, and fee policy. No protocol oracle decides whether the fixed pair is a good price.
The path
A taker consumes the Open offer to create Claimed. After preflight confirms the current direct MPC-TLS path, the taker sends PLN using the claim-derived memo. The observed amount must satisfy expected ≤ observed ≤ expected + Δ; the remaining payment fields must match their offer terms.
The launch notary signs a blinded payment commitment with ECDSA-secp256k1. FiatOfferV1 verifies that signature and opened payment fact inside a zero-knowledge action. Solve releases USDC to the taker and collector. If the epoch budget elapses first, Expire consumes the offer and returns USDC to the maker. There is no bond, reopened offer, or dispute path.
At launch, PayMoney uses one notary. If that notary works with a dishonest taker, they can fake payment evidence and take the crypto from one claimed offer. The offer cap limits the loss. There is no detection, penalty, or recovery path at launch.
What the example does not imply
It does not imply current bank support, a measured settlement time, a live fee, a guaranteed market price, trustlessness, or legal approval. Every concrete template and the deployment itself must pass the gates in Trust & risks.