Payment infrastructure,
answered.
Deployment, providers, transaction flows, operations and commercial terms. Start with the question your team is trying to settle.
Platform and deployment.
What is PulsePay?
PulsePay is a B2B payment technology platform covering acceptance, routing, payouts, reconciliation, merchant operations and the controls around them. It can run as a Dedicated Platform or as Managed Orchestration.
Who is PulsePay built for?
Payment service providers, electronic money institutions, payfac and fintech teams that operate payment flows across providers and need control over how those flows run. See the PSP guide and the EMI guide.
Where does PulsePay run?
Dedicated Platform runs in the client’s environment and data perimeter. Managed Orchestration is operated on PulsePay infrastructure around an existing payment stack.
Do we have to replace our current payment platform?
No. Managed Orchestration can add routing, connectivity and operational visibility around an existing core. A Dedicated Platform is the route when the core itself needs replacing or deeper control.
What is the difference between Dedicated Platform and Managed Orchestration?
Dedicated Platform is a complete deployment in your environment. Managed Orchestration is an operated layer around your existing stack, with a supported connector set. Compare the models in detail.
Can we migrate from a rented white-label platform?
Yes, but migration should be planned by payment flow, provider connection, merchant data and operational process. Read the migration guide.
Providers and payment flows.
Who signs and owns the contracts with payment providers?
Your business keeps the provider commercial relationships. PulsePay supplies the technology that connects and operates those flows.
How many provider integrations are available?
The current connector set and the operations supported by each integration are confirmed during discovery. A logo count does not confirm the methods, regions, refunds, payouts or reports required for your flow. See the integration approach.
Can PulsePay build a connector for a new provider?
Yes, subject to API access, the provider’s cooperation, technical feasibility and an agreed implementation scope.
How do routing and cascading work?
Routing applies configured rules to choose a provider. Cascading can retry an eligible failed payment on another route according to the defined conditions and controls. Read the routing guide.
Can we build staged, conditional or multi-party flows?
These flows can be modelled within an agreed implementation scope. The required providers, transaction states, fund movement and reconciliation have to be mapped together. Explore complex payment flows.
Can we keep our existing providers and add a second one?
Yes, subject to connector coverage and provider access. The project includes more than the API connection: routing behaviour, failure handling, webhooks, reports and reconciliation all need to line up.
Operations and compliance.
Does PulsePay hold or settle client funds?
No. Funds move through the financial institutions and payment providers connected to the flow. PulsePay is the technology layer.
What payment states can operators see?
The platform tracks the lifecycle and operational events around a payment, including creation, authorization, capture and settlement where supported by the connected provider.
Does PulsePay support payouts?
The platform includes a payout engine for individual, batch and mass payout workflows. Exact operations and provider coverage are scoped for each deployment. Explore the payout engine.
How does reconciliation work?
Payment, payout, fee and provider records are matched against a common operating context so finance teams can investigate exceptions. Explore ledger and reconciliation.
How are merchant access and team permissions managed?
Merchant configuration and operational access sit within the platform’s back office. Roles and actions are controlled through RBAC and audit history. Explore the back office.
Is PulsePay a licensed financial institution?
No. PulsePay provides payment technology and does not replace your licences, compliance obligations or regulated financial partners.
Pricing and implementation.
What does Dedicated Platform cost?
The published deployment starting point is €25,000. Final scope depends on modules, providers, migration, custom flows and acceptance requirements. See published pricing.
Does PulsePay take a percentage of processed volume?
No. The Dedicated Platform model does not charge a percentage of payment volume. Other fixed or usage-based items are defined in the commercial proposal.
How is Managed Orchestration priced?
It is scoped separately around the supported connectors, traffic model and operational work. The agreed proposal defines setup and ongoing charges.
What information is needed for a useful proposal?
Bring target geographies and currencies, payment methods, contracted or shortlisted providers, merchant model, expected flow and launch date. This lets the team separate base deployment, integrations and custom work.
How does a project go live?
The team maps the operating model, configures the platform, connects providers, tests each transaction path and agrees acceptance before live traffic. Read the launch guide.
How do we discuss a specific payment flow?
Share the current stack, provider relationships and the flow that is blocked. Contact PulsePay to map the practical route.