Management Portal
The user experience: dashboards, workspaces, configuration screens and operational actions.
PLATFORM ARCHITECTURE
One platform.
Clear responsibilities.
Three independently structured applications, connected through explicit interfaces. A coherent operating model without a monolithic dependency.
THE MERCHANTPAISA PLATFORM
01Management Portal
Visibility. Configuration. Operations.
Authorized management actions
02Management API
Identity. Permissions. Workflows.
Service-to-service integration
03Acquirer Solution
Processing. Routing. Financial control.
BanksProcessorsPayment networks
Public architecture · connectivity subject to agreed scope and approvals
CONNECTED BY DESIGN
Every layer has a job.
No layer does everything.
Management API
The management authority: authentication, authorization, tenant scope, validation and workflow coordination.
Acquirer Solution
The processing authority: payment lifecycle, provider routing, execution and financial state.
TWO FLOWS. DISTINCT PURPOSES.
Manage the business.
Process the payment.
MANAGEMENT FLOW
Management PortalManagement APIAcquirer
Management actions are authorized and coordinated before reaching processing services.
PAYMENT FLOW
Payment channelAcquirer / payment ingressConfigured provider
Payment ingress is defined by the solution. Payments do not have to pass through the Management API.
The diagrams show public responsibility boundaries, not private deployment topology. No internal hosts, credentials or privileged endpoints are disclosed.
ADAPT THE BUSINESS. KEEP THE BOUNDARIES.
Modular where it helps.
Controlled where it matters.
Scope the deployment around your organization, providers and operational model—not around a one-size-fits-all marketing diagram.
01
Independent applicationsSeparate build and deployment boundaries let the management experience and processing core evolve deliberately.
02
One financial authorityPortal views and API responses reflect authoritative processing outcomes; they do not invent success.
03
Explicit tenant controlsResource ownership and permissions belong in the management service, not only in browser filters.
04
A separate public websiteThis marketing site has no payment execution, database or internal service dependency.
LET’S BUILD TOGETHER
Build your next chapter
in payments.
Bring your acquiring model, your markets and your ambition. Let’s define the infrastructure behind them.