Who this section is for

Business owners and product leads deciding whether Fintech Infrastructure fits what they are building. Find the shape that looks like your product; each maps to the building blocks you would assemble.

One frame that covers every shape

Across every shape below, the end user experiences your brand — your app, your checkout, your payout schedule. PayMongo runs underneath as the licensed infrastructure: accounts, wallets, payment rails, and compliance. How deeply white-labeled the experience is depends on the configuration you pick inside each building block, not on which shape you are.

The shapes

Marketplaces and multi-vendor commerce

You sell on behalf of many sellers and split each payment between the seller and your platform fee. Onboard sellers as accounts in your ecosystem, accept payments, and split settlement programmatically.

Assembles: Onboarding-as-a-Service, payment acceptance, and split payments under Workflows.

Travel, booking, and multi-party splits

One customer payment fans out to three or more recipients — the operator, the property or airline, an insurer, your fee. The split shape goes beyond two parties, in a single flow.

Assembles: Onboarding-as-a-Service, payment acceptance, and multi-recipient split payouts under Workflows.

SaaS with embedded payments

Your software runs your customers' businesses, and payments should live inside it — invoicing, POS, booking, or billing under your product's brand. Each customer gets their own account and accepts payments as themselves.

Assembles: Onboarding-as-a-Service, payment acceptance per customer, and Wallets-as-a-Service (Coming soon) where customers hold balance.

Logistics and delivery

Riders and couriers collect payments and receive earnings. Provision each rider a wallet they control — hold balance, transfer to an e-wallet, or withdraw to a bank — and disburse earnings on your schedule.

Assembles: Onboarding-as-a-Service, Wallets-as-a-Service (Coming soon), and scheduled disbursements under Workflows.

Employee management, payroll, and benefits disbursement

You move money to people in your own organization or client organizations — salaries, allowances, incentives, benefits. Accounts here are typically fully managed by you, and recipients control the wallet that receives the funds.

Assembles: Onboarding-as-a-Service (consumer accounts), Wallets-as-a-Service (Coming soon), and disbursement rails (InstaPay, PESONet).

Payment providers and aggregators

You are yourself a financial service — aggregating merchants, or extending banking or e-money services — and need licensed rails, onboarding, and compliance you can build on rather than rebuild.

Assembles: the full stack, composed to your model — Onboarding-as-a-Service, Ledgers-as-a-Service, Workflows, plus Verifications-as-a-Service and Wallets-as-a-Service (both Coming soon).

Referral and partner-driven models

You bring businesses to PayMongo but don't operate their accounts — they run themselves; you keep visibility, and possibly a revenue share. The relationship matters more than the operation.

Assembles: account linking via Account & Settings → Linked accounts, with visibility scoped per relationship.

Next steps

Found your shape? Read Key concepts for the model and vocabulary the whole section uses, then open the first product your shape assembles.