PAYSTAR DIRECT CONNECT
Connect PSPs once. Keep provider choice open.
One merchant-facing API for payment operations across connected PSPs, without replacing the direct commercial relationship between merchant and provider.
PayStar Direct Connect is the connectivity product between your payment stack and the PSPs you select. Your team implements one stable contract; PayStar maintains the provider adapters delivered by its own team and preserves the evidence needed to operate every pipeline.
[01] what direct connect provides
A stable contract across changing providers
One merchant-facing API
Use documented operations for deposits, payouts, status checks and balances instead of implementing a new merchant-side model for every PSP.
One access key per pipeline
Every pipeline receives its own key. Two deposit pipelines use different keys, and deposit and payout access never overlap.
Normalized and original context
Use consistent statuses and errors for automation while retaining the original PSP response for support, finance and audit.
Provider changes behind the contract
Add or replace an approved route without starting a new merchant integration project for the same supported operation.
[02] responsibility remains explicit
Connection does not blur ownership
Merchant
Selects and contracts with each PSP, approves the payment flow and controls commercial and routing policy.
PayStar
Provides the technical contract, connects approved PSP capabilities and keeps the payment lifecycle observable.
PSP
Processes and settles under its direct agreement with the merchant and remains responsible for its own channel.
[03] prepare your integration brief
What to bring to a PSP integration review
Use this checklist to define the connection your team needs. It helps separate the merchant integration from each provider's commercial approval and technical prerequisites.
Providers and operating context
List your selected PSPs, target markets, payment methods, currencies and expected volumes. Identify which provider agreements and onboarding decisions are complete. If you are still choosing providers, start with PayStar Discovery.
Operations and pipelines
Map the deposits, payouts, status checks and balances required from each PSP. Review the public API contract and confirm which operations each selected route supports. Plan separate access for every pipeline.
Payment lifecycle and evidence
Describe how your system records transaction identifiers, receives callbacks and handles pending or failed payments. Identify the normalized statuses and original provider responses your support and finance teams need.
Readiness and ownership
Name the engineering and operational contacts, confirm provider configuration and agree the test scenarios before launch. Use the developer integration guide to review authentication, callbacks and the move from test to production.
A connected adapter is one part of launch readiness. The PSP still approves the merchant and the route must be available for the agreed market, method and payment flow.
Choose how a new adapter is developed
Fast-track Integration is a separately accepted development order with PayStar, with an agreed scope, fixed development price and delivery window.
With Self-integration, a dedicated developer implements, tests and maintains the client-specific APM adapter. PayStar operates the agreed environment and its side of the exchange. We can help you find and prepare the developer.
[04] where it fits
The connection between selection and operations
PayStar Discovery helps qualify relevant PSP routes before engineering starts. Direct Connect implements the selected capabilities. PayStar Core adds routing, monitoring, investigation and reconciliation across the connected estate.
Planning a provider change? Read how to replace a PSP without rebuilding the merchant integration and review the responsibilities of the merchant, PSP and orchestrator before defining the handover.