Skip to main content
Budgets help you separate funds and enforce spend control by creating dedicated “pots” of money. You typically use budgets when you want:
  • controlled spend for a specific purpose (travel, ads, payroll, teams)
  • multiple cards drawing from a shared balance
  • a clear funding and reconciliation model for operations

​
How budgets relate to cards

Budget cards are cards linked to a budget. When the cardholder spends, the spend is controlled by the budget. Start here if you haven’t yet:
Budget cards use a budget balance. Users don’t top up or withdraw funds from a budget card directly — you fund the budget, and spend debits the budget.

​
The core flow (high level)

1

1) Pick a budget model for your product

Budgets are constrained by card program (BIN):
  • one budget per BIN
  • one BIN per budget
Because of that, you typically model the BFinance budget as a single program-level pool.If your product needs “budgets per user/team/purpose”, model those as internal sub-ledgers in your own system, and enforce them in your authorization decision logic.
2

2) Fund the budget

You top up the budget so it has balance available for spend.
3

3) Issue budget cards linked to the budget

Issue a Budget card and link it to the budget (using the budget identifier).
4

4) Track budget activity

Use budget transactions and webhooks to power activity feeds and reconciliation.
For exact request parameters and response shapes, use the API reference.