Spend Controls block card transactions before they happen. This article explains what each rule covers, its limitations, and what cardholders see when a transaction is declined.
Budgetly default rules (always on)
High risk transactions
Active for every company — cannot be turned off.
Blocks transactions that Budgetly identifies as high risk, along with high-risk merchants and currencies. The specific categories and criteria are managed by Budgetly, reviewed regularly, and are not published.
Company rules (Premium and Enterprise)
These are off by default. Admins can enable them in Settings → Company → Preferences → Cards → Spend controls.
Note: Category rules rely on how the card network classifies each merchant, which Budgetly doesn’t control. A legitimate purchase is occasionally affected by a merchant’s classification. If that happens, contact your admin, who can disable the rule.
ATM withdrawals
Blocks cash withdrawals at ATMs for all company cards.
- Physical cards only — virtual cards cannot withdraw cash regardless of this setting.
- ATM withdrawals can also be blocked per user under Settings → Users → [User] → Preferences. The company-wide toggle and the per-user setting work independently.
Liquor stores
Blocks all purchases at liquor stores, bottle shops, and wine merchants.
Pubs and bars
Blocks all purchases at bars, pubs, and nightclubs.
International transactions
Blocks any transaction processed in a non-AUD currency.
Important: Some Australian merchants charge in a non-AUD currency (e.g. international travel bookings, overseas-based subscriptions billed in USD). These transactions are blocked by this rule even though the merchant is local.
Online transactions
Blocks all card-not-present purchases — online shopping, subscriptions, SaaS tools, and e-commerce.
- In-person transactions (tap, insert, swipe) are unaffected.
- This is a binary block — all online or none. It is not possible to allow some online merchants and block others in this release.
Digital wallet
Blocks payments made via Apple Pay and Google Pay. Also prevents cards from being added to mobile wallets.
- Cards already added to a mobile wallet before this rule is enabled are not removed, but payments via those wallets are blocked.
- When a user tries to add a card to Apple Pay or Google Pay while this rule is active, they see: “Digital wallet is disabled for your company.”
- Disabling the rule re-enables wallet payments and allows new provisioning immediately.
What cardholders see when a transaction is declined
When a spend control rule blocks a transaction, the cardholder receives:
- A push notification with the merchant name, amount, and the specific rule name (e.g. “Alcohol purchases are restricted by your company”).
- An email notification with the same details.
- A decline reason on the transaction detail page, showing the rule that triggered the decline — separate from budget-related declines.
What admins see in the Action Log
Every spend control decline creates a separate entry in the Action Log, showing the card, the cardholder, the merchant, the amount, and the rule that triggered the block. Every rule change is also logged, with the admin’s name, the rule that changed, and the time.
Action Log entries for spend control declines are distinct from budget-related decline entries, so finance teams can filter and report on policy enforcement separately.