01
Command
Bounded payload, authenticated tenant context, explicit idempotency, and a durable initial record.
Product
From intent to local payout, with one durable story.
YembiPay is the orchestration and evidence layer between partner instructions, policy controls, stablecoin settlement, and approved Caribbean payout rails.
Lifecycle
No stage claims success before its authority confirms it.
The same settlement identifier travels through validation, policy, execution, reconciliation, and evidence issuance. Recovery resumes from durable cursors instead of replaying value blindly.
02
Authorize
Policy evidence is versioned and attached before any external execution boundary.
03
Execute
Provider submission, chain confirmation, and local rail completion remain distinct states.
04
Reconcile
Observed external evidence is compared with canonical ledger and settlement state before terminalization.
Authority
Clients ask. The platform decides.
Browser, mobile, and SDK clients never become tenant or ledger authority. They submit commands and render confirmed state from the same v1 API.
- Tenant ownershipDerived from the authenticated API-key context.AUTHZ
- Money movementCommitted by API-owned transactions and durable outbox state.ACID
- RetriesReuse the same idempotency key for the same command only.SAFE
“Submitted” is not “settled.” “Settled” is not “paid out.” Evidence names the difference.
YembiPay operating principle
Evidence certificate
A portable outcome, not a decorative receipt.
The certificate binds the settlement, policy result, chain or provider observation, local-rail outcome, and audit references available for independent verification.
Deterministic identity
Stable identifiers connect one certificate to one organization-owned settlement.
Terminal prerequisites
No certificate side effect occurs before canonical terminal evidence is present.
Export and verify
Operators can download the artifact and use the public minimum-data verification path.
Map the product to your operating model.
We will document supported responsibilities, missing dependencies, recovery ownership, and rollout gates before integration.
