Auto-configuration
Have every new child account activated with your standard capability set, without per-account requests.
Who this section is for
Product and engineering teams at businesses building platforms that create many child accounts that should all start with the same set of PayMongo capabilities — for example, every new merchant should get QR Ph plus a standard wallet on activation.
What it is
Auto-configuration applies a default capability set at the parent level. Every child created under your parent automatically receives that set when activated. Without auto-configuration, you request capabilities per child after the fact.
flowchart LR A[Parent defines defaults] --> B[Child created] B --> C[Child activated] C --> D[Defaults applied automatically]
Why it matters
- Consistency. Every child starts with the same capabilities, regardless of who created it.
- Operational simplicity. No per-child enablement requests for the baseline.
- Faster activation. Capabilities are ready the moment activation completes.
Current state
Available by email requestEmail [email protected] with:
- Your parent account ID (
org_…).- The capability set you want as the default for each child type (
merchantand / orconsumer).- Any exceptions (specific account types or IDs that should not receive the default).
PayMongo confirms the configuration and applies it. From that point on, every new child created under your parent receives the default set on activation.
Today, defaults are scoped to your parent account and apply uniformly to all children of a given type. Per-child overrides remain available via Account capabilities.
Roadmap
Coming soon
- Self-serve from the Dashboard. Define and edit default capability sets without contacting support.
- Multiple capability profiles. Attach different default sets to different child segments (for example, riders versus sellers).
- Programmatic management. Manage profiles via API for parents with their own admin tooling.
Frequently asked
Does auto-configuration change anything in my code?
No. The Accounts API flow stays the same. Auto-configuration changes what PayMongo provisions during activation, not how you call the API.
What if I need a different capability set for one child?
After activation, request the per-child change through Account capabilities. The default set still applies on activation; per-child overrides are layered on top.
Can I enable auto-configuration retroactively?
Auto-configuration applies to new children created after it is enabled. Existing children keep whatever capabilities they were activated with. Request changes for existing children through Account capabilities.
Related pages
- Account capabilities — per-child capability grants.
- Opt-in features — overview of all opt-in features.
- Quick start — the underlying onboarding flow.
Updated 16 days ago