Account capabilities
Know which capabilities a child account starts with at activation, and how a parent requests more for a fully managed child.
Who this section is for
Product and engineering teams at businesses building platforms that need a child account to do more than the default activation gives — for example, accept cards in addition to QR Ph, or use other PayMongo products that require explicit enablement — and want to know how to request them.
What it is
An account capability is a PayMongo product or feature scoped to a single account. This is the same capability model as Account capabilities under Account & Settings, applied to your linked accounts.
The difference is who can act. On your own account, you request capabilities yourself — from the Dashboard or through support, as the canonical page describes. Requesting capabilities on other accounts linked under your platform is a gated configuration, and is where the opt-in applies.
Key guide — capability and policy contract are differentCapability lives on the child account and determines which products the child can use. Policy contract (Coming soon) lives on the relationship and determines what the parent may do on that link. The parent's effective permissions on a link are the intersection of both. See Policy contracts for the full model.
What a child gets at activation
Only the default capabilities are provisioned at activation:
merchant— wallet plus QR Ph (P2M) as a payment-acceptance method.consumer— wallet only. The wallet supports QR Ph (P2P) transfers; no payment-acceptance method is provisioned.
See Quick start — Merchant vs consumer at a glance for the full activation picture.
Requesting more capabilities for a child
A parent requests additional capabilities for a fully managed child through the Capability Requests API, using its own secret key and the child's Account-ID. Any other linked child requests its own capabilities. See Requests on linked accounts. The capability catalog and per-capability requirements live in Account capabilities.
Frequently asked
Can a child request its own capabilities?
Yes, if the child's authorized representative has dashboard access — they can request capabilities the same way any PayMongo account does. If the child is fully managed, the parent can also request them through the Capability Requests API.
Are capabilities revocable?
Not on request, for now — capabilities on a child function the same as on any PayMongo account. Contact [email protected] if you have concerns or a specific outcome in mind.
Do capabilities expire?
There is no fixed expiry. PayMongo or the underlying payment provider can suspend or revoke a capability where risk, compliance, or scheme rules require it — the same treatment any PayMongo account receives. The governing provisions are in the Terms of Use.
Related pages
- Account capabilities — the canonical capability catalog, requirements, and activation flows.
- Auto-configuration — apply your agreed configuration (rates, fees, payouts, and more) to every child you create. It does not activate capabilities.
- Opt-in features — overview of all opt-in features.
- Linked transactions — operate on an activated child.
Updated about 1 month ago
