End provider
An end provider is the payment provider that actually processes and settles the money when the merchant connects through an orchestrator or aggregator. The merchant sees the intermediary in its log, but the money and the statement come from the end provider. Reconciliation has to identify it for every payment.
How it works
An end provider sits behind a payment orchestrator. The merchant sends a payment to the orchestrator. The orchestrator routes it to one of several providers. Illustrative, synthetic example:
merchant log PAY-6D2F route: orchestrator provider: —
orchestrator PAY-6D2F routed_to: Provider G ref: G-88120
statement Provider G ref: G-88120 amount: 900 CUR-2
The merchant log names only the orchestrator. The end provider’s name and reference are inside the orchestrator’s message.
Why it matters
The end provider is the party that owes the money and issues the provider statement. Reconciliation against the orchestrator alone cannot confirm settlement. The end provider’s statement often carries its own reference, not the merchant’s ID. On one anonymised merchant day, 54.2% of statement lines did not carry the merchant’s ID at all. Without the end provider’s reference, those lines cannot be paired.
How to spot it
- Check whether your log has a single provider field for routed payments.
- Open one orchestrator message and find the routed provider and its reference.
- Match that reference against the end provider’s statement, not the orchestrator’s report.
Related terms
Payment orchestrator · Payment service provider · Provider statement · Merchant log · Reconora and orchestrators
Try it on one day of your data
One day of your data, reconciled, and the report stays with you whether or not you continue.
Updated