Payin flows
Which payin flow to use for each business case.
A flow is a complete, end-to-end payin use case. Where Concepts answers "what is a template, an intent, a payin?", flows answer "how do I let users recharge their wallet, collect from many payers, or reconcile payments one by one?".
Choosing a flow
The decision comes down to two questions: who is paying, and do you need to know which payment is which before the money arrives?
| Your case | Flow |
|---|---|
| End users load their own wallet balance, repeatedly, with a permanent key. | Top-up |
| Many payers pay to one shared key or static QR: donations, in-store, campaigns. | Collect with a template |
| Each payment must be pre-identified: checkout, invoices, one QR per purchase. | Collect with intents |
| Customers pay from their bank account at checkout, approving at their bank. | Collect with PSE |
| Understand how the collected money reaches your bank account. | Settlement |
Top-up
Recharge a subaccount with a permanent Bre-B key.
Collect with a template
One static key or QR, many payers, webhook-driven reconciliation.
Collect with intents
One intent per payment: dynamic QR, retries, exact reconciliation.
Collect with PSE
One intent per payment, paid from the customer's bank account through PSE.
Settlement
From approved payment to money in your funding account.
Next steps
- Concepts: the entities these flows compose.
- Webhooks: the events that drive each flow.
- Payins API reference: the endpoints behind them.