Skip to content
PEYELIDocumentationPARTNER FIELD GUIDE / 1.3

Search the field guide

Local search · no data sentEsc to close
Partner guide/Start here
THE FOUNDATION FOR A GOOD RELATIONSHIP2 min read

A clearer way to build together.

Connect the sale, the payment and the record. Explore how Peyeli brings merchant operations and a wallet experience together—and where your organization can contribute.

FOR ENTERPRISE TEAMS
A shared starting point. A useful next step for every team.

Business, engineering, security, operations and procurement.

Open the enterprise pack
ONE SYSTEM, EXPLICIT RESPONSIBILITIESConceptual architecture
▤BusinessMerchant operations
◫WalletConsumer experience
PEYELIIdentity · records · authority
⇄ProvidersApproved execution
≡SettlementEvidence & reconciliation
SOFTWARE ORGANIZES THE RECORDS.Agreements define financial authority.
See the foundations. Choose the next step.

Code, tests, deployment and approval are four separate facts.

View capability status →
Which partnership is worth a pilot?

Seven opportunities. Contributions, scope and results to measure.

Explore the business cases

Commerce deserves a connected record.

A sale should remain understandable after checkout. Peyeli connects merchant operations and a consumer wallet experience around everyday commerce in Haiti and relationships across HTG and USD. Business records, payment outcomes, receipts and reconciliation form the foundation for explaining what happened and what comes next.

Choose your evaluation path.

Start with the partner models to identify the relationship you want to evaluate. Use the architecture and payment lifecycle to understand authority. Then read capability status, access boundaries and the evaluation checklist before asking for a sandbox.

  • Commercial teams: partner models → capabilities → evaluation.
  • Engineering teams: architecture → payment lifecycle → integration contracts.
  • Security and operations: security → data boundaries → access → go-live gates.

Your evaluation starts here.

The current evaluation experience is based on synthetic data. Simulated balances are not redeemable funds. Real collection, remittance, account issuance, FX and card programs each require their own provider acceptance and approval.

These pages describe source-reviewed foundations and proposed partner relationships. They do not certify an active partnership, production deployment, regulatory approval or a self-service public API. Capability status separates those questions so that implementation is never confused with authorization.