Who owns what in payment orchestration?

Payment orchestration coordinates several parties, but coordination does not erase their separate commercial, technical and financial responsibilities.

The merchant owns business policy

The merchant defines the legal entity, target markets, customer experience, risk appetite and commercial provider relationships. It approves which routes may receive traffic and what priorities or limits apply. An orchestration platform can execute that policy, but should not quietly become its author.

PayStar owns the control layer

PayStar connects provider-specific interfaces to a stable merchant-facing contract, applies approved routing logic and preserves the technical history needed to explain what happened. This responsibility covers the orchestration layer itself: adapters, rule execution, observability and access to evidence.

The PSP owns its payment channel

Each PSP decides whether it can onboard the merchant, processes requests within its own systems and remains responsible for its contractual services. Where the PSP is responsible for settlement, that obligation stays with the PSP. A successful technical hand-off does not transfer that financial responsibility to PayStar.

Shared work needs explicit hand-offs

Incidents, reconciliation differences and route changes cross organisational boundaries. Define who detects the issue, who gathers evidence, who contacts the PSP, who approves a policy change and who confirms closure. The map should name both the owner and the next action.

Make the map operational

Put the responsibility map beside the workflows people already use. Connect every route state, sensitive action, incident type and reconciliation exception to one accountable role and one escalation path. Review it when a provider, merchant entity or payment operation changes. A diagram that lives only in an architecture deck will not help during an incident; the working version should be visible to support, payment operations, finance and engineering, with enough detail for each team to act consistently.

Good orchestration makes boundaries visible: it coordinates the work without pretending that every responsibility belongs to one platform.