Who this section is for

All audiences — business owners, C-level leaders, product, engineering, and compliance. Read this page once and every sub-section of Fintech Infrastructure will use vocabulary you already have.

Infrastructure, not a product suite

Fintech Infrastructure treats PayMongo's capabilities as building blocks: each is a standalone product, and any activated account can compose them. You don't adopt a suite — you assemble onboarding, wallets, payment acceptance, verification, ledgers, and workflows in whatever combination your product needs, and skip the rest.

Two properties make the model work:

Default availability. The building blocks are features of every PayMongo account, not a gated product tier. What used to require a separate "Platform" arrangement is now covered by the standard Terms of Use.
Composability. Blocks combine but don't all depend on each other. Some require accounts in your ecosystem (Wallets-as-a-Service (Coming soon) provisions wallets on accounts, which usually means Onboarding-as-a-Service first). Others stand alone (Verifications-as-a-Service (Coming soon) runs identity verification without creating an account; Ledgers-as-a-Service runs on your own account).

Linked Accounts — the foundation

Every product in this section that touches more than one account builds on Linked Accounts: the model for how a business connects to and manages other accounts on PayMongo — whether you run a marketplace, operate sub-merchants, or manage multiple entities under one group.

📘
Key guide
Linked Accounts is canonically documented at Account & Settings → Linked accounts — the relationship model, the Invite flow, and lifecycle live there. This page gives you only the three properties the rest of Fintech Infrastructure assumes.

The model in three lines:

Any onboarded and activated account can link as a parent or a child to any other account.
Accounts can hold multiple parent and child relationships at the same time — multi-association (Coming soon).
Each link is governed by policies that both accounts agree to (Coming soon).

Parent and child are roles within a relationship, not global identities. In one relationship your account acts as the parent; in another it can be the child.

🚀
Coming soon — early Q3 2026
Multi-association and per-relationship policy contracts ship in early Q3 2026. Until then, accounts hold a single parent relationship. See Policy contracts for the full forward-looking model.

One disambiguation worth keeping straight everywhere in this section: a capability lives on an account and defines which products it can use; a policy lives on a relationship and defines what the parent may do on that specific link.

White-labeled by design

Across Fintech Infrastructure, your end users experience your brand while PayMongo operates the licensed rails underneath. How complete the white-labeling is depends on configuration — for example, whether child accounts get their own PayMongo Dashboard access — not on which products you compose. Each product's pages state the configurations and their trade-offs.

Glossary

Term	Definition
Fintech Infrastructure	PayMongo's composable stack — modular financial capabilities any activated account assembles by default. Previously named Platforms.
Building block	PayMongo's products and services work like building blocks: modular, interoperable, and easy to combine into a solution for any problem.
Linked Accounts	The foundational model for parent and child account relationships. Canonical home: Account & Settings → Linked accounts. Also called account relationships.
Parent account	The role an account plays as the managing side of a relationship — typically your platform.
Child account	The role an account plays as the managed side of a relationship — a seller, rider, customer, or entity in your ecosystem.
Multi-association	An account holding many parent and child relationships at once, each its own record. (Coming soon)
Policy contract	The per-relationship agreement scoping what the parent may do on that link. (Coming soon) See Policy contracts.
Capability	A product an individual account is enabled to use. Lives on the account; distinct from a policy.
Workflows	The orchestration engine for event-driven money movement — splits, routing, and scheduled transfers. See Workflows.
White-labeled	Your users experience your brand while PayMongo runs the infrastructure underneath.

Next steps

Use cases — find the shape that matches your product.
Onboarding-as-a-Service — where most integrations start.
Linked accounts — the full relationship model.