Routing and reconciliation need one evidence chain

Routing decides where a payment goes. Reconciliation tests whether the recorded operational and financial evidence agrees afterward. Treating them as separate worlds creates blind spots.

Begin the record at route selection

Store the payment context, policy version, selected pipeline and provider identifier before the request leaves the orchestration layer. That route identity should remain attached to subsequent status changes, callbacks, refunds and related operations.

Preserve every attempt, not only success

Cascading can create several provider attempts for one customer action. Finance and operations need to know which attempt was submitted, completed, reversed or left unresolved. Collapsing the sequence into one final status can create false matches and missed exceptions.

Match reports to the same identifiers

Import or review PSP reports against the provider and merchant references recorded in the payment history. Compare amounts, currencies, fees, timestamps and status semantics. Keep expected settlement separate from the PSP contractual obligation and actual transfer.

Route exceptions to the right owner

A missing record may indicate integration mapping, report scope, timing or provider processing. Attach the evidence and next action to the exception, then assign it to merchant finance, PayStar technical operations or the PSP as appropriate.

Feed exceptions back into route operations

Repeated reconciliation differences can expose a status mapping gap, callback problem, provider report limitation or an operational rule that needs attention. Summarise patterns by pipeline and payment lifecycle, then send them to the team that can change the cause. Do not silently correct the financial view while leaving the route evidence inconsistent. The resolution should update both the exception and the relevant integration, monitoring or provider playbook so the next payment carries better evidence.

Reconciliation is stronger when the financial record can point back to the exact route decision and every provider event that followed.