PAYSTAR CORE DEDICATED
Make platform development follow your business priorities. Core Dedicated provides a separate product branch, dedicated team and infrastructure for your needs. Develop your version on working Core software with PayStar's payments and engineering expertise.
YOUR PRIORITIES
Give new markets, payment scenarios and internal processes a place in your development plan. You set business priorities; together, we agree the sequence, dependencies and completion criteria for specific changes.
When standard Core is not enough, plan changes in a separate branch. Review the routing, monitoring, transaction investigation and reconciliation you need, then agree the scope and its relationship with the wider platform.
Ongoing development needs defined engineering capacity. We agree the team composition, available capacity and how work is assigned. You can match priorities to resources and review the plan and budget when the workload changes.
Your version does not require infrastructure design from a blank page. Together, we define the components, hosting and operating responsibilities. Monitoring, backups and recovery belong in the agreed plan, with clear responsibilities for your team and PayStar.
Understand each stage's outcome and resource requirements before starting. Agree scope, budget and acceptance, discussing new requirements separately. Use this basis to choose the next improvement, change priorities or expand capacity.
If owning a platform in source code becomes a priority, preparation can form part of your Dedicated plan. Discuss documentation, knowledge transfer and team readiness early. Moving to Core Fork remains a separate decision, informed by experience of the working product.
SCOPE & RESPONSIBILITIES
Agree the product, team and infrastructure around your needs: capacity, development plan, ongoing service, updates and budget. Define each stage's outcome and verification criteria, so both sides share an understanding of completion.
Sets priorities, approves the budget and accepts delivered work. You select payment providers and contract with them directly.
Provides a dedicated team and develops your Core branch within the agreed scope. Infrastructure, operations and support responsibilities are defined in the project terms.
Process payments and settle funds under their own agreements. Dedicated does not transfer the PSP's responsibility for approvals or handling funds to PayStar.
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
Review your processes and scenarios. Experience with Core helps distinguish existing capabilities from required changes and supports an informed Dedicated decision.
Define the team, infrastructure, first stage and budget. Agree owners, dependencies, acceptance criteria and how priorities can change.
Plan improvements in successive stages. Agree testable scenarios and outcomes for each, and consider identified constraints before the next changes.
Continue developing with PayStar. If you want independence, discuss Core Fork separately: delivery scope, rights, knowledge transfer and your team's readiness.
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.
Standard and Enterprise offer different Core service and support levels. Dedicated adds a separate product branch, team and infrastructure for your development plan.
A dedicated PayStar team develops your version. You provide owners for priorities and acceptance; agree your technical specialists' involvement for the project.
Around agreed capacity, scope and dependencies. A dedicated team provides resources for your plan; agree stage timelines and capacity changes during planning.
No. Core Fork has separately agreed code, rights and handover terms. Continue Dedicated or prepare a transition informed by experience with the product.
Tell Dmitry what you want to change, what limits development and your team's intended role. Discuss Dedicated's scope and first stage.