01
Payment gateway
The gateway commonly supplies checkout or API connectivity, securely transmits payment data and routes technical messages. It may not underwrite the merchant or settle funds.
Payment infrastructure roles
Payment gateway vs PSP vs acquirer: know who does what.
Payment companies often combine several roles under one brand, which makes provider comparisons confusing. The useful question is not the label alone, but who supplies connectivity, underwriting, regulated payment services, settlement and operational support for the merchant’s route.
Send a private payment brief
Practical guidance
The roles behind a payment route
One company may perform several roles, while another route may combine multiple specialists under separate contracts.
02
Payment service provider
A PSP packages payment acceptance or related services for merchants and may combine gateway, acquiring access, local methods, risk tools, reporting and support.
03
Acquirer
The acquirer contracts for card acceptance, underwrites the merchant for that acquiring relationship and participates in clearing and settlement under card-scheme rules.
04
Processor and orchestration layer
A processor handles transaction messages and records; an orchestration platform may connect several providers, route transactions and centralise integration without replacing provider approval.
05
Alternative payment provider
Open Banking, A2A, wallets, vouchers and payout specialists may support non-card flows with their own eligibility, settlement and integration model.
06
Merchant responsibilities
The merchant still owns accurate onboarding information, lawful market access, customer terms, operational controls, reconciliation and compliance with its provider agreements.
Decision checkpoints
Questions to ask before choosing the stack
Resolve contractual and operating responsibility before comparing interface features or headline coverage.
D1
Who underwrites the merchant?
Identify the entity making the compliance and risk decision and whether separate approval is required for each route or method.
D2
Who holds and settles funds?
Document the regulated party, settlement account, currencies, timing, reserves and what happens to funds during refunds or disputes.
D3
Who owns the integration?
Confirm APIs, tokens, webhooks, reporting, support boundaries and whether the merchant can migrate or add a backup provider.
D4
Who handles incidents?
Set escalation paths for failed payments, delayed settlements, reconciliation gaps, fraud events and provider-side changes.
Decision checklist
Map the provider roles
Specific, current information improves the quality of every provider conversation.
Contracting and regulated entities
Merchant underwriting owner
Gateway and API operator
Acquirer or payment rail
Settlement and reserve owner
Risk, fraud and dispute tools
Reporting and reconciliation
Support and incident escalation
Questions
What businesses usually ask
Is a PSP the same as a payment gateway?
Not necessarily. A gateway commonly provides technical connectivity, while a PSP may bundle connectivity with payment services, methods, underwriting access, reporting and support.
Is a PSP always an acquirer?
No. Some PSPs are acquirers, while others connect merchants to one or more acquiring or payment partners. The contract and funds flow should identify the actual roles.
Can a merchant use a gateway with several PSPs?
Potentially. The gateway or orchestration layer must support the providers, token and data model, routing logic and operational reconciliation required by the merchant.
Who decides whether a merchant is approved?
The provider or acquiring entity responsible for the route makes the compliance and underwriting decision. A gateway or intermediary cannot guarantee that approval.
How does OfferPSP help choose between these models?
We structure the entity, GEO, method, currency, flow, integration and settlement requirements, then assess which provider roles and routes are relevant for a controlled introduction.
Continue with the service
Related guides and matching briefs
Use the guide
Turn the checklist into a provider-ready payment brief.
Share the company, target GEOs, vertical, methods, volume and current constraint. We will assess the next useful step without publishing your provider search.