Partner models2 min read
Find your place in the network.
Find the opportunity that fits your organization: collections, settlement, remittance, card programs or connected software.
The relationship determines the scope.
Peyeli owns the software experience and its operational records. A financial provider’s responsibilities depend on the approved agreement: collection, custody, settlement, remittance or issuance. A technical connection does not transfer those responsibilities automatically.
| Partner model | What we evaluate | What needs agreement |
|---|---|---|
| Collections / FSP | Merchant requests, authenticated results, lookup and settlement. | Merchant delegation, assets, fees, refunds and settlement authority. |
| Bank / settlement | Statements, deposit matching, exceptions and evidence. | Account ownership, data rights, formats and resolution responsibilities. |
| Remittance | Hosted customer journey, identity handoff and status authority. | Corridors, platforms, disclosures, compliance and payout methods. |
| Card issuer / sponsor | Program, funding, authorization, clearing and refunds. | Eligible regions, cardholder requirements, funding and program controls. |
| Accounting / software | Consented record exchange, mapping and recovery. | Objects, read/write permissions, retention and disconnect behavior. |
Turn the opportunity into a working relationship.
An evaluation needs an authorized technical specification and test access. We also need to establish who can act for each merchant, which customer types and countries are eligible, what proves an outcome, and who handles disputes or settlement differences.
- Identify the contracting entity, program and environment.
- Confirm lookup, duplicate handling, reversals and settlement evidence.
- Agree on incident contacts, test limits and acceptance criteria.