ILLUSTRATION / S-2048
Example evidence record
- Policy decision
- example only
- Chain evidence
- not submitted
- Local rail
- not submitted
- Certificate
- not issued
No customer funds representedUSDC → JMD
Controlled settlement architecture
Build the evidence before moving value.
YembiPay is hardening stablecoin settlement, policy checks, Caribbean rail integration, and immutable evidence as one system. Remote value movement and every payout corridor remain unavailable until their explicit launch gates pass.
Tenant-scoped authorityIdempotent commandsAuditable outcomes
Illustrative
Operating model
One settlement record across every boundary.
The API remains the authority while policy, chain, rail, and evidence services contribute bounded decisions to the same durable lifecycle.
01
Validate intent
Authenticate the organization, enforce scope, validate recipient and corridor data, and reserve one idempotency key.
Read the command contract
02
Screen before value moves
Apply sanctions, AML, ownership, and corridor policy before an external value-moving instruction is accepted.
Review control design
03
Settle across rails
When launch gates pass, coordinate chain confirmation and an approved local payout adapter without pretending submission equals completion.
Inspect corridor readiness
04
Issue evidence
Attach immutable certificate and audit references only after canonical terminal evidence exists.
See the evidence model
Execution trail
A readable state machine, not a black box.
Each transition names its authority and leaves enough evidence for operations, compliance, and recovery.
Intent accepted
Organization, scope, amount, recipient, and idempotency are validated.
Policy authorized
Sanctions and compliance evidence bind to the settlement version.
External execution observed
Chain and local-rail evidence are verified, not inferred from a submission receipt.
Certificate issued
The terminal record can be verified independently and exported.
Choose your path
Built for operators, integrators, and assurance teams.
Every route answers a different implementation question and leads to a working destination.
01
Operations
Understand recipient, treasury, settlement, exception, and certificate workflows.
Explore product
02
Developers
Start with scoped X-API-Key authentication, idempotency, webhooks, SDK artifacts, and errors.
Open developer hub
03
Compliance
Inspect tenant isolation, screening, evidence, audit, and data-minimization boundaries.
Review compliance
Bring a corridor, integration, or control question.
Tell us the origin, destination, rail, volume model, and assurance requirements. We will respond with the current supported path, not a simulated promise.
