Target execution network
Base is the intended settlement network. Remote chain submission is not admitted until custody, deployment identity, ownership, oracle, and release gates pass.
Developer Truth & Proof
Read on-chain evidence without confusing submission with outcome.
YembiPay publishes only reviewed network, token, contract, finality, and anchor facts. Unknown deployment identities remain visibly unavailable.
Current posture
Reviewed facts and deliberate empty states.
No wallet, signer, reserve balance, failover topology, or guessed contract address is exposed.
Gated
Token and settlement contracts
No production token or YembiPay contract address is published from an empty configuration value or documentation guess.
Local evidence certificates
Deterministic local artifacts can bind synthetic policy and execution evidence. They are explicitly unanchored.
Published certificate anchor
No reviewed production anchor identity or independently verified publication path is available.
Public verification
A backend boundary exists, but the website has no reviewed digest-only, minimum-data same-origin proxy. No authenticity conclusion is offered here.
Finality
Five states that must not collapse into one green badge.
A chain receipt proves only its own boundary. The recipient outcome and the financial books require separate authorities and evidence.
Intent admitted
Tenant, scope, recipient, quote, idempotency, policy, and wallet-health gates pass.
Chain submitted
A transaction identity exists; inclusion and finality are still unresolved.
Chain confirmed
Validated receipt and finality evidence prove the on-chain leg only.
Local payout completed
The authorized local rail reports recipient-funds availability under its own finality rules.
Reconciled
YembiPay, custodian or chain, and bank or rail records agree and all breaks are owned.
Evidence language
Verify only what the evidence can support.
A future verifier may report a match to a reviewed published anchor, no reviewed anchor found, or service unavailable. A failed lookup must never label a document fraudulent.
Public verifier remains gated.
Use organization-owned certificate downloads in the authenticated console. Public minimum-data verification will appear only after its proxy and anchor are reviewed.