01
Side-by-side
| Decision point | Dedicated Platform | Managed Orchestration |
|---|---|---|
| Existing core | Replaces or becomes the core | Remains in place |
| Deployment | Client environment | PulsePay-operated infrastructure |
| Data perimeter | Client-controlled | Processed in the managed service |
| Provider coverage | Scoped to the deployment | Supported connector set, then extensions |
| Best for | Launch, migration or full control | Faster orchestration around a live stack |
02
Choose Dedicated Platform when
- You are launching or replacing the payment core
- The platform must run inside your own infrastructure boundary
- The project requires deeper payment, payout or ledger logic
- Provider coverage must be scoped around your own contracts
03
Choose Managed Orchestration when
- The current core still performs its job
- Provider resilience and routing are the immediate constraint
- You want to avoid a platform migration before improving operations
- The managed connector and data model fit the intended scope
04
The choice can evolve
Orchestration can be the first step while a team proves new routes or keeps a legacy core running. A dedicated deployment becomes relevant later if infrastructure ownership, data location or platform depth changes.
FAQ
Frequently asked questions
- Which option goes live faster?
- Managed Orchestration usually has a narrower initial scope, but the actual timeline for either model depends on provider access, integration readiness and required custom logic.
- Do both models keep provider contracts with the client?
- Yes. PulsePay provides technology; provider commercial relationships remain with the client.