Developer Truth & Proof
Capability state comes from reviewed evidence, not route presence. Today the catalog contains local-sandbox, gated, and unavailable services; no live corridor is claimed.
Truth model
A passing local test, configured adapter, API health response, or smart-contract source file cannot silently become a production claim.
Reviewed 2026-08-26
Each public record includes its environment, evidence level, review date, and the concrete condition required to advance. Internal ownership and repository details stay private.
Service catalog
Filter by domain or current evidence-backed state. Search stays in the browser.
25 capabilities
Developer / public / locally tested
A curated contract containing only reviewed partner-facing operations.
Evidence: The filtered OpenAPI and Postman artifacts are generated and tested locally.
Next gate: Publish the exact generated artifacts and verify the hosted release.
Reviewed:
Developer / local sandbox / locally tested
Typed client source for the reviewed partner contract.
Evidence: Node and Python client sources and CI jobs exist in the repository.
Next gate: Prove package-registry ownership, publish signed versions, and freeze the supported contract.
Reviewed:
Recipients / local sandbox / locally tested
Tenant-scoped recipient reads and lifecycle management for local integration work.
Evidence: Authenticated tenant-scoped recipient routes and tests are present.
Next gate: Complete provider-backed beneficiary validation and prove hosted tenant isolation.
Reviewed:
Recipients / local sandbox / documented
Create a tenant-owned beneficiary record for a supported payout method.
Evidence: Recipient creation is intentionally excluded from the reviewed partner contract while its tenant-safe request design is finalized.
Next gate: Remove the redundant organization field from the creation request and regenerate the reviewed partner contract.
Reviewed:
Identity / remote sandbox / documented
Identity and business-verification workflow boundaries for recipients and partners.
Evidence: Signed provider boundaries and local verification states exist, but production activation and complete evidence reconciliation are unproven.
Next gate: Contract the provider, approve the program, and prove ongoing requirements and RFI operations.
Reviewed:
Quotes / local sandbox / locally tested
Synthetic fee, rate, and recipient-amount estimates with a bounded quote lifetime.
Evidence: Fresh-rate validation and exact 30-second quote evidence are covered locally.
Next gate: Bind every quoted fee and FX leg to an executable licensed provider and live corridor.
Reviewed:
Payins / local sandbox / locally tested
Machine-readable input-adapter posture for local integration planning.
Evidence: The endpoint reports configured adapter capabilities without asserting provider readiness.
Next gate: Add provider-authority, funding-finality, return, and hosted-readiness evidence per method.
Reviewed:
Payins / remote sandbox / locally tested
Provider adapter boundaries for collecting a settlement input.
Evidence: Provider-call adapters exist, but an admitted end-to-end remote settlement cannot be formed.
Next gate: Prove acquiring or bank authority, collection finality, returns, reconciliation, and one admitted corridor.
Reviewed:
Payouts / local sandbox / locally tested
A deterministic no-value settlement state machine for local development.
Evidence: The route is admitted only in the local sandbox and fails closed remotely.
Next gate: Complete durable pre-collection, licensed payout execution, liquidity, reconciliation, and production release gates.
Reviewed:
Payouts / local sandbox / locally tested
Poll and inspect the state of a tenant-owned local-sandbox settlement.
Evidence: Tenant-scoped read routes and state rendering are tested locally.
Next gate: Prove hosted object ownership, provider references, local-rail finality, and reconciliation states.
Reviewed:
Payouts / local sandbox / locally tested
Local configuration describing modeled countries, currencies, fees, and rails.
Evidence: The route returns modeled corridor configuration; it does not prove current local-rail availability.
Next gate: Replace static configuration with provider-authoritative eligibility, requirements, limits, cutoffs, holidays, price, ETA, and health.
Reviewed:
Payouts / production / documented
Credit JMD to a verified Jamaican beneficiary through an authorized local rail.
Evidence: Output-rail implementations are simulations and reject remote use.
Next gate: Contract an authorized Jamaica partner, fund liquidity, complete rail certification, and prove payout plus reconciliation.
Reviewed:
Balances / production / documented
Partner-facing available, pending, reserved, and blocked balances.
Evidence: Current treasury views are internal local simulation and the ledger is an operational projection, not an audited financial book.
Next gate: Implement the canonical double-entry subledger, safeguarding model, provider balance feeds, and daily reconciliation.
Reviewed:
Compliance / local sandbox / locally tested
Fail-closed sanctions, issuer-address-list, AML, and risk evidence for local simulations.
Evidence: Deterministic evidence and fail-closed remote screening behavior are tested locally.
Next gate: Approve versioned policies, complete ownership coverage, productize RFIs and filings, and independently test the program.
Reviewed:
Evidence / local sandbox / locally tested
Deterministic per-settlement evidence artifacts for local simulations.
Evidence: Deterministic PDF and private-replica checks are covered locally; local artifacts are unanchored.
Next gate: Deploy a reviewed anchor, publish minimum-data verification, and obtain independent assurance of the evidence process.
Reviewed:
Evidence / public / documented
Check a digest against reviewed published settlement evidence without revealing private transaction data.
Evidence: A backend verification boundary exists, but the public site has no reviewed minimum-data same-origin contract.
Next gate: Specify, secure, and test a digest-only public proxy and publish a reviewed anchor.
Reviewed:
Events / remote sandbox / locally tested
Tenant-scoped endpoints for settlement and system event delivery.
Evidence: Signed delivery and lifecycle reads are locally tested; subscription creation is intentionally excluded from the reviewed partner contract.
Next gate: Publish the tenant-safe creation contract and prove the hosted delivery lifecycle.
Reviewed:
Events / local sandbox / locally tested
Inspect tenant-scoped webhook attempts and delivery outcomes.
Evidence: The authenticated tenant-scoped delivery-history route exists and is covered locally.
Next gate: Approve the retention policy and prove the redacted response contract in a hosted environment.
Reviewed:
Reports / local sandbox / locally tested
Traceable partner usage and transaction-level commercial records.
Evidence: Usage snapshots and draft-invoice records exist locally, but delivery, pricing authority, and hosted proof are incomplete.
Next gate: Approve pricing, bind usage to booked transactions, add adjustments and credit notes, and prove hosted access controls.
Reviewed:
Reconciliation / production / documented
Match the YembiPay subledger, custodian or chain, and bank or local rail with an owned break queue.
Evidence: Operational evidence schemas exist, but live observer feeds, financial books, and provider-bound reconciliation are unproven.
Next gate: Implement the double-entry subledger, provider feeds, daily close, exception ownership, and independent accuracy proof.
Reviewed:
Exceptions / production / documented
Partner-visible exception lifecycles with ownership, finality, evidence, and financial treatment.
Evidence: Individual adapter events exist, but no complete product lifecycle or governed case queue is available.
Next gate: Build canonical states, cases, reserves, ledger postings, reconciliation, communications, and appeal/escalation rules.
Reviewed:
Batch / production / documented
Invoice, bill, or batch settlement orchestration for partner workflows.
Evidence: Legacy direct-transfer and batch write routes are retired; no admitted payables workflow exists.
Next gate: Validate anchor demand after one live corridor, then design an idempotent approval and exception model.
Reviewed:
Onchain / production / locally tested
Submit a screened settlement to a reviewed YembiPay contract on Base.
Evidence: Smart-contract controls and local tests exist; deployment identities and remote admission are empty by construction.
Next gate: Complete custody and token design, deploy and verify contracts, bind owner/oracle configuration, and pass the real-money release gates.
Reviewed:
Onchain / production / documented
Publish a reviewed evidence digest with a verifiable chain reference.
Evidence: Anchoring code is gated and local certificates do not claim a public anchor.
Next gate: Deploy the reviewed anchor contract, publish identities, prove ownership and finality, and expose minimum-data verification.
Reviewed:
Developer / production / documented
Evidence-based partner approval across authority, compliance, funds, books, security, resilience, integration, and support.
Evidence: The readiness dimensions are specified, but no named approval workflow or production corridor authority exists.
Next gate: Assign approval owners, define required evidence, complete partner contracts, and certify one end-to-end corridor.
Reviewed:
Clear a filter or search by service, environment, evidence, or next gate.