PAYSTAR CORE FORK
Build your payment platform on PayStar's working code. Core Fork helps shorten the path to your own version and reduce design risks. Your team runs infrastructure, sets priorities and releases changes. Before buying, evaluate the product, proposed code package and your team's readiness to operate it.
YOUR PRIORITIES
Start with an existing foundation when your platform becomes a strategic priority. Review its architecture and payment workflows, then identify the changes your business needs. Focus your team's effort on those differences.
Choose which features to build, who develops them and when changes go live. Establish your own release process within the agreed rights, with priorities set by your product and engineering teams.
Plan hosting, access controls, monitoring and backups around your requirements. Review technical dependencies and the expertise needed before handover, so your team understands what it will deploy and maintain.
Test important scenarios, discuss the architecture and review the proposed code package. Trying Core or Dedicated first is an option: experience with the product can help you assess how well it fits your processes.
Consider the handover alongside staffing, infrastructure and ongoing maintenance costs. Review external services, component licences, integrations and future updates separately to build a budget around a clear scope.
Define how your team will demonstrate readiness: build a version, deploy it, run an agreed payment scenario and restore the system. Discuss documentation, operating runbooks and knowledge transfer before completing the purchase.
SCOPE & RESPONSIBILITIES
Start with the proposed code inventory, usage rights, external dependencies and acceptance criteria. Agree the handover scope, documentation, team preparation and ongoing support. This gives you a concrete engineering project to assess.
Runs your version, infrastructure, access controls, backups, monitoring and releases. Sets payment rules, selects PSPs and takes responsibility for operation after handover.
Agrees the code package and rights, and helps plan technical review and handover. Documentation, training, launch assistance and subsequent support are scoped before work begins.
Confirm method availability and their commercial terms. Your business contracts directly with PSPs; transferring the platform does not itself transfer provider contracts, approvals or obligations.
You select and contract with PSPs directly. PayStar provides the agreed technical services; PSPs process payments and settle funds under their own agreements.
GETTING STARTED
Discuss your workflows, markets, team and infrastructure requirements. Identify which parts of the product matter most to your purchasing decision.
Agree how to assess the product and conduct technical due diligence. Consider using Core or Dedicated to evaluate operational workflows first.
Agree the code inventory, rights, dependencies, documentation and acceptance criteria. Assign responsibilities between both teams, with stages and a budget.
Complete acceptance against agreed build, deployment and operating scenarios. Assign ownership of future changes and determine the support needed after handover.
Each product can be discussed separately. You do not need to buy every step.
| Option | Best fit | Who develops it |
|---|---|---|
| Core | Payment routing and daily operations | PayStar |
| Core Dedicated | A dedicated product, team and infrastructure for your priorities | A dedicated PayStar team |
| Core Fork | Your infrastructure built on existing, working code | Your team |
Start with the result you need. Agree the details before committing to the work.
That is an optional evaluation path. The right approach depends on your team's familiarity with the product and the scenarios you want to test.
Choose Dedicated for your own priorities and product version with a PayStar team. Consider Fork when your team is ready to take responsibility for code, infrastructure and further development.
We discuss the exact version, usage and modification rights, and third-party component terms before purchase. Bring any distribution or onward-transfer requirements into that discussion.
Consulting, fixes and updates can be discussed separately. Define what your team will maintain, where you need PayStar's assistance and how that assistance will be provided.
Tell Dmitry about your product, team and desired independence. Discuss your goals, proposed scope and what to verify before buying.