Why the gateway is only one part
Connecting an acceptance provider solves message exchange, not the whole operating model. Teams still need to control who can act, explain balances and fees, investigate payment states, manage merchants and reconcile provider records against an internal source of truth.
Core infrastructure layers
- Payment and payout transaction lifecycles
- Provider routing and fallback logic
- Ledger and reconciliation workflows
- Merchant, tariff and payment-method configuration
- Role-based back office with auditable actions
- KYC and AML integrations connected to operations
Deployment and control
A Dedicated Platform is deployed for the organisation and can sit within its environment and data perimeter. The EMI retains its provider contracts and operating policies while PulsePay supplies and maintains the platform software.
Scope before implementation
The decisive inputs are the regulated entity’s role, countries, payment and payout methods, provider contracts, ledger boundaries, merchant hierarchy and reporting obligations. These are mapped during technical discovery before the implementation plan is fixed.
Frequently asked questions
- Is PulsePay itself an EMI or financial institution?
- No. PulsePay Ltd provides payment technology and does not hold or settle client funds.
- Can the platform be deployed in the EMI’s environment?
- Yes. That is the operating model for Dedicated Platform, subject to the infrastructure and implementation scope agreed during discovery.