01
Compare operating ownership, not licence price
| Option | Best fit | Primary trade-off |
|---|---|---|
| Internal build | Core technology is the differentiator | Longest path and permanent engineering ownership |
| Shared white-label | Fast validation with limited control needs | Vendor and operating-model constraints |
| Dedicated platform | Control and speed are both required | Upfront deployment and integration scope |
| Managed orchestration | The existing core stays in place | A separate orchestration operating layer |
02
The hidden internal-build backlog
- Provider certification and connector maintenance
- Transaction state, retry and idempotency handling
- Merchant configuration, tariffs and access control
- Payouts, ledger records and reconciliation
- Monitoring, support tooling and audit history
03
Questions that make the decision clearer
Ask whether the business benefits when engineers spend time on payment plumbing, how many providers and methods are needed at launch, where data must live, what must be unique, and who owns the system at 02:00 when a provider changes behaviour.
04
PulsePay’s position
Dedicated Platform is the buy-and-own-operational-control option: the software is deployed for your organisation without a percentage charge on payment volume. Managed Orchestration is the extend option when replacing the current core would be unnecessary.
FAQ
Frequently asked questions
- Is a dedicated platform the same as white-label PSP?
- No. A dedicated deployment gives the client its own platform environment and operating configuration while provider contracts remain directly controlled by the client.
- Can custom payment logic still be added?
- Yes. Custom scope can be added around the platform rather than rebuilding the common payment core first.