Use an existing PayStar connection
Explore the available payment integrations and discuss the methods and providers needed for your business.
PAYSTAR / SELF-INTEGRATION
For alternative payment methods (APM)Build or buy?Worried about lock-in?
A ready payment platform. A dedicated developer. Integration development at your pace.
PayStar provides the platform and infrastructure. You set the priorities and budget for adapter development and keep the code created for your business.
You can start without a developer or experience managing an integration project. We can help you find a specialist, prepare them for the work and support the first integrations.
01 / YOUR CHOICE
A ready platform. A choice of ways to grow.
See how PayStar works before you decide. Explore the payment platform, routing and reporting, and review the availability commitments in our SLA.
Choose how to connect the next provider:
Ask PayStar to build an integration
Our specialists organise development, testing and preparation for launch within the agreed scope. Explore Fast-track Integration when you want PayStar to handle the development.
Work with a dedicated developer
A dedicated developer builds adapters in PayStar's infrastructure, following the priorities, milestones and budget you agree. We can help you find and prepare a specialist.
PayStar provides documentation for developing a secure adapter, a complete example adapter and two hours of developer training to help the specialist get started.
You can use these approaches together as your integration needs change.
02 / YOUR ASSETS
Keep the value of what you build.
The adapter code created for you by a dedicated developer belongs to you. PayStar will not use those client-specific developments for other clients.
PayStar provides the environment for development and operation, with source control, change history and technical logs. The work remains available when the person doing it changes.
- Repository, history and logs. While the service is provided and paid for, PayStar retains the adapter repository, change history and technical logs covering the last three years. The current code in use is retained regardless of when it was created.
- Archive after the service ends. After formal termination, PayStar keeps an archive of the repository, change history and deployment configuration for six months. Retention beyond that period is not guaranteed. The archive does not include a running environment; restoration and redeployment require a separate order. Payment and personal-data retention rules still apply. Confirm storage and handover terms before starting.
- Handover on your instruction. Ask PayStar to pass the developments to another developer so work can continue.
- A copy for your business. Request a backup copy of the source code and change history.
Each new integration adds to the work your business can maintain and develop with its chosen specialist.
03 / YOUR CONTROL
Set the priorities. Control the development.
Your integration roadmap does not have to wait for a place in PayStar's development queue.
PayStar supplies the platform, routing, reporting and adapter environment. You manage the development of the adapter: the work specific to your provider and business requirements.
With the dedicated developer, you decide which provider comes next, what to build first, the scope of each milestone and the budget. Review progress, change priorities or bring in a different specialist when the business needs it.
The developer implements and tests the payment logic. Launch still depends on provider documentation and access, compatibility checks and an agreed rollout.
Choose a familiar stack. The developer can use their preferred language and framework, provided the adapter runs in the supplied Docker environment and follows the documented interface and security requirements.
04 / YOUR SPECIALIST
A dedicated developer, with help at every step.
You do not need to arrive with a developer already in place.
The dedicated developer can be a trusted specialist you already work with, someone new whose skills we help assess, or a specialist we help you find. They can be an employee, an external contractor or a freelancer.
Find a specialist
We can help you find a developer for your team and define the integration work they need to deliver.
Prepare them for the work
The initial support includes two hours of developer training, with secure-adapter development documentation and a complete example adapter.
Training introduces the platform and adapter requirements. An exam helps assess the skills learned. Discuss the specialist’s preparation and assessment with PayStar.
Assess an existing developer
We can help assess a specialist's relevant skills, identify preparation needs and agree what the first adapter should demonstrate.
Support the first integrations
We can guide the developer through the interface, environment requirements and preparation of the first adapters for launch.
Agree the scope of assistance and the evidence for accepting each adapter before the work starts. Each live integration needs its own payment testing and acceptance.
05 / YOUR FOCUS
Start with one developer. We run the infrastructure.
One dedicated developer, including a freelancer, can get started without a separate infrastructure team.
The developer focuses on your integration: understanding the provider's API, implementing payment logic, testing outcomes and maintaining the adapter.
PayStar provides the working environment:
- Servers and isolation. An isolated Docker runtime operated on PayStar infrastructure.
- Builds and deployment. A repository and configured workflows for building and releasing adapters.
- Backups and change history. Source control and backups of the repository, deployment configuration and persistent storage included in the service.
- Technical logs and monitoring. Logs for investigating adapter behaviour, with infrastructure monitoring operated by PayStar.
The developer's time goes into the integration work your business needs. PayStar maintains the environment and its side of the protocol, and helps identify where a problem originates.
GETTING STARTED
A clear path to the first adapter
- Bring the business goal. Tell us which APM provider you need, the required payment flow and your priorities.
- Choose a dedicated developer. Bring a trusted specialist or ask us to help find, assess and prepare one. Agree the scope, milestones and acceptance criteria.
- Prepare the environment and access. PayStar provides the runtime, repository, workflows and interface documentation. Obtain the PSP's documentation, access and permission for the intended live flow.
- Build, test and launch. The developer implements the adapter. PayStar checks hosting and protocol compatibility; your team accepts the payment logic and agrees a controlled rollout.
THE DETAILS
Practical questions
What can we control independently?
You control adapter development, the choice of developer, priorities and the code created for your business. The adapters run in PayStar's environment and communicate through its protocol. Running them elsewhere requires a separate technical assessment and any necessary changes.
What does PayStar monitor and back up?
PayStar operates and monitors the supplied infrastructure. Backups cover the repository, deployment configuration and the persistent storage included in the service. Temporary files inside a container are outside that backup scope. The developer records useful technical events and checks the adapter's payment logic; infrastructure monitoring alone cannot confirm the meaning of a PSP response.
Who maintains the adapter after a PSP API change?
The dedicated developer maintains the adapter, its dependencies and its interpretation of PSP responses. PayStar maintains the environment and its part of the exchange. When an issue occurs, we help identify the boundary and provide available technical evidence. Additional help with client code can be arranged separately.
Can the developer access PSP credentials?
PayStar manages stored credentials and transmits them through the documented encrypted protocol. The adapter code can use them, so they are accessible to that code and its author. Choose a trusted developer and keep credentials out of logs.
How is the adapter checked before launch?
PayStar checks that the adapter runs in the environment and communicates through its protocol. Your team organises testing and acceptance of the PSP-specific payment logic. Compatibility checks are not a source-code audit or a guarantee of that logic. Use the client adapter interface documentation, agree acceptance evidence and start with a controlled live flow.
LET'S PLAN YOUR NEXT CONNECTION
Start with your next business priority.
Tell us which provider you want to connect and whether you already have a specialist in mind. We will show you the platform, discuss the environment and help you choose the next step.