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.
Two methods are available today. The matrix grows a column per method as new ones launch, without changing templates, intents, or payins.
Method matrix
| Capability | co_breb | co_pse |
|---|---|---|
| Rail | Bre-B, Colombia's instant-payment scheme | PSE, Colombia's system for paying online from a bank account |
| Payer pays to | A Bre-B key or QR code (payment token) | Their own bank's page, reached through pse_url (payment token) |
| Settlement currency | COP | COP |
Payer data (instrument) | Arrives with the payment; nothing collected upfront | Collected upfront: bank, identity, and contact, sent with the intent |
| Collect without intents | Yes: a template key or static QR | No: every payment goes through an intent |
expected_payers enforcement | Yes: validated against the payer document that arrives with the payment | Not supported: refused with payin_expected_payers_not_supported |
| Intent window | 30 minutes from ready_to_pay | 20 minutes from ready_to_pay; once the link is generated, the intent waits for PSE's outcome |
| Retry after a failed attempt | Yes: the intent re-arms while it lives | No: create a new intent |
| Per-transaction limit | Bre-B network cap (see Bre-B) | No method cap from Mono; the template's limits apply |
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. See Delivering to your funding account.
- Disbursement default: the program-wide
subaccount_disbursement_trigger(templates and intents can override it). - 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: instant payments to a key or QR code, in detail.
- PSE: payments approved at the payer's bank, in detail.
- Payment tokens: keys and QRs across methods.
- Flows: what to build with them.