Platform

A Payment Platform Your Business Can Operate

The platform brings the customer-facing payment experience and the operator-facing controls into one coherent model. Exact modules follow your business, provider relationships, and security boundary.

Request a gateway plan

Customer layerMerchant layerGateway coreOperations

A customer journey that feels like your product

Configure brand expression, hosted payment surfaces, domains, payment selection, result states, and communication handoffs. Mandatory downstream authentication or provider steps remain transparent in scope.

Merchant operations under the same identity

Plan onboarding context, merchant access, transaction views, refunds, reports, and support actions around the teams that will operate the service.

A transaction model the team can reason about

Normalise requests, states, callbacks, provider responses, and routing decisions so payment behavior is visible instead of buried across individual integrations.

Finance and support after authorisation

Reconciliation, settlement context, refunds, disputes, audit trails, and operational reporting are treated as part of the gateway—not an afterthought.

Control is a design decision.

A larger feature list does not automatically create a better gateway. The operating model should expose the decisions your teams genuinely need and keep the rest disciplined.

Brand depth

Provider choice

Operator workflow

Illustrative scope controls, not performance values.

Platform scope to evaluate

These are the categories to resolve during discovery. They do not imply every module is included in every plan.

Branding: Checkout surfaces, merchant portal, domains, notifications, and interface tokens.
Payments: Methods, transaction states, refunds, recurring flows, and provider dependencies.
Routing: Rules, fallback behavior, availability logic, and operator overrides.
Operations: Merchant views, reporting, reconciliation, disputes, and support context.
Governance: Roles, approvals, logs, environments, and change control.

Next step

Apply this page to your actual payment model.

Send enough context to identify the right questions, dependencies, and commercial path.