Methods
The payment methods you can collect with, side by side.
A payment method is the rail a payin travels on, plus everything the rail implies: what the payer pays to, which currencies it settles, its limits, and how much Mono knows about the payer. Templates declare the methods they accept in available_methods; every payin records the one that actually delivered it in method.
One method is available today. The matrix grows a column per method as new ones launch — without changing templates, intents, or payins.
Method matrix
| Capability | co_breb |
|---|---|
| Rail | Bre-B — Colombia's instant-payment scheme |
| Payer pays to | A Bre-B key or QR code (payment token) |
| Settlement currency | COP |
Payer data (instrument) | Arrives with the payment — nothing collected upfront |
expected_payers enforcement | Yes — validated against the payer document that arrives with the payment |
| Intent window | 30 minutes from ready_to_pay |
| Retry after a failed attempt | Yes — the intent re-arms while it lives |
| Per-transaction limit | Bre-B network cap — see Bre-B |
Program configuration
Enabling payins is a program-level setup you align with Mono — there is no self-service switch. When you request it, expect to define, per method:
- Methods and currencies — which methods your program collects with, and in which currencies.
- Funding account — the bank account where the real money lands, which also decides the settlement mode: automatic sweeps for a Mono-allied account, manual dashboard settlement for an external bank.
- Disbursement default — the program-wide
subaccount_disbursement_trigger(templates and intents can override it). - Fees — the fixed and percentage fees you charge your subaccounts, per method.
- Pruning grace periods — how long templates survive expiration or inactivity before being discarded.
- Merchant identity — the default merchant name shown to payers, and for Bre-B, the QR merchant data (category code, city, postal code) and key-naming rules.
Next steps
- Bre-B — the method available today, in detail.
- Payment tokens — keys and QRs across methods.
- Flows — what to build with them.