Introduction
Understand what Fintech Infrastructure is, which building blocks it gives your business, and where to start assembling them.
Who this section is for
Business owners, C-level decision-makers, product leads, engineers, and compliance teams at businesses building their own platform on PayMongo — a marketplace, a delivery app, a SaaS product with embedded payments, a payroll or disbursement operation, or any product that runs financial services for its own users under its own brand.
Previously known as PlatformsFintech Infrastructure replaces the product previously named Platforms. The capabilities are the same and existing integrations continue to work; what changed is that they are no longer a separate, gated product. If you followed the v2 "Platforms" documentation, this section and its sub-sections are the successor.
What Fintech Infrastructure is
Fintech Infrastructure is PayMongo delivered as a composable stack. Each capability is a modular building block — independently usable and combinable — so you assemble only what your product needs instead of adopting a fixed suite. Your users see your brand; PayMongo runs the licensed financial rails underneath.
The stack covers five capability areas:
| Capability area | What it covers |
|---|---|
| Rails connectivity | InstaPay disbursements, PESONet payouts, and QR Ph transfers. |
| Payment connectivity | Card acceptance, e-wallets, direct online banking, buy-now-pay-later, and QR Ph acceptance. |
| Workflow and control | Limits, routing logic, exception handling, and event-based actions. |
| Risk and protection | Screening, monitoring, and policy controls and guardrails. |
| Identity and onboarding | Account creation, ecosystem onboarding, identity verification, and KYC and KYB frameworks. |
These capabilities are default features of every PayMongo product, available to any activated account — there is no separate contract or product gate to unlock them.
What you will find in this section
Each sub-section is a standalone product built from the stack. Compose them in any combination:
| Product | What it does |
|---|---|
| Onboarding-as-a-Service | Create, verify, and activate accounts for the users in your ecosystem. |
| Wallets-as-a-Service (Coming soon) | Provision wallets with full money movement — QR Ph sending and receiving, InstaPay, PESONet, and intra-disbursements. |
| Payments-as-a-Service (Coming soon) | Provision payment acceptance — online and offline — for your organization or your sub-accounts. |
| Verifications-as-a-Service (Coming soon) | Run identity verification on its own, without creating an account. |
| Compliance-as-a-Service (Coming soon) | Run screening, monitoring, and compliance checks as a standalone service. |
| Ledgers-as-a-Service | Keep programmable ledgers under your own account. |
| Workflows | Orchestrate money movement with event-driven logic — split payments and payouts, routing, and scheduled transfers. Live for all accounts by default. |
Products tagged (Coming soon) are part of the stack but do not have documentation yet; their sections publish as they ship. If you need more information, contact us via [email protected] to inquire.
Underneath all of them sits Linked Accounts — the model for how accounts connect in parent and child relationships. It is not a product in this section; it is the foundation every product here builds on. Its canonical home is Account & Settings → Linked accounts.
Before you begin
Fintech Infrastructure is available to every activated PayMongo account by default — no separate enablement step. Your acceptance of PayMongo's Terms of Use covers account linking and the capabilities in this section; see Part IV — Platform Capability / Account Linking Feature for the specific provisions.
Some features within individual products remain opt-in (for example, Partner Verification under Onboarding-as-a-Service). Each product's pages state what is default and what requires a request.
Where to start
If you are evaluating, start with Use cases to recognize whether your product fits, then read Key concepts for the model and vocabulary.
If you are ready to build, go straight to the product that matches your first milestone — most integrations start with Onboarding-as-a-Service to bring users into the ecosystem, then layer on wallets, payments, and workflows.
Updated 16 days ago