Programs
Group your accounts under one configuration — currencies, enabled features or services, methods, and the funding account they settle with.
A program groups accounts that operate under the same configuration: which currencies they can hold, which features or services are enabled for them (payins, payouts, transfers between subaccounts, cards), which payment methods each one can use, and which funding account they settle with. Every account belongs to a program, so the program is the level at which you shape how a whole set of accounts behaves.
Think of a program as a product line inside your organization. A wallet in COP for retail users, a USD treasury for corporate clients and a premium plan with different pricing can each be a program of their own — with their own rules and fees — under a single Mono integration.
Programs are set up with Mono when you onboard, or when you need a new one — there is no self-service endpoint to create or edit them. What you do configure yourself, per program, is pricing: see Fee policies.
What a program defines
| Setting | What it decides |
|---|---|
| Currencies | The currencies the program's accounts can hold. Each account has exactly one currency, chosen from this list. |
| Enabled features or services | Which Core features or services the accounts can use: payins, payouts, transfers between subaccounts (with or without currency conversion) and cards. |
| Methods | Within each feature or service, the payment methods available — which payout rails, which payin methods — and their settings. |
| Funding account | The real bank account the program settles with: where the money collected by payins is delivered and where the money of payouts comes from. |
| Default | One of your programs is the default one: accounts created without a program go there. |
Programs and accounts
When you create a ledger account you can pass its program_id (a pro_ identifier). If you leave it empty, the account joins your default program. The account inherits everything the program defines: it cannot hold a currency the program does not support, nor use a feature or service the program has not enabled.
Account holders are not tied to a single program — the same holder can have accounts in different programs.
Why split your operation into programs
Use several programs whenever two groups of accounts should behave differently:
- By currency — a COP program and a USD program, each settling with its own funding account.
- By product or plan — a free plan and a premium plan with different fees.
- By client or segment — a program per enterprise client, or per region, to keep their configuration and pricing apart.
Programs are also one of the levels at which fee policies apply: a policy targeting a program prices every account in it, unless a more specific policy — for an account holder or for a single account — overrides it. See who a policy applies to.
Where programs show up in the API
program_idwhen creating a ledger account — pick the program, or omit it for the default one.target_type: programandtarget_idon a fee policy, to price every account of a program at once.- Your tenant configuration, which lists the currencies your programs support.
Next steps
- Fees — what you charge your users, and what Mono charges you.
- Fee policies — pricing at the global, program, account holder or account level.
- Ledger — the accounts a program groups.