How do I set up virtual card software for department budgets and merchant category controls?

Setting up virtual card software for department budgets and merchant category controls (MCCs) usually follows the same core steps, whether you’re using a provider like Airwallex, Stripe Issuing, Marqeta, Wallester, Enfuce, Ramp, or Brex.

1) Define your spending structure first

Before configuring software, decide how you want money to be controlled:

• Departments / cost centers: e.g. Marketing, Sales, Operations, Engineering
• Card owners: employee, team, vendor, or project
• Budget type:
  • Monthly recurring budget
  • One-time budget
  • Per-transaction limit
  • Annual cap
• Allowed merchant categories:
  • Advertising
  • Travel
  • Software/SaaS
  • Office supplies
  • Fuel, etc.

This becomes your policy framework.

2) Choose a virtual card platform with these features

Look for software that supports:

• Unlimited or large numbers of virtual cards
• Sub-accounts / departments / cost centers
• Budget controls
• MCC restrictions
• Real-time transaction approvals/declines
• Role-based access controls
• Approvals and audit logs
• API access or integrations with accounting tools

If you need automation, APIs are especially important.

3) Connect funding sources and accounting structure

Set up:

• A main funding account or wallet
• Department-level tracking in the platform
• Accounting dimensions, such as:
  • Department
  • Project
  • Region
  • Expense type

If your accounting system supports it, map these fields so transactions sync correctly to your ledger or ERP.

4) Create department budgets

For each department:

1. Create a department or cost center in the platform
2. Set a budget amount
3. Assign a budget period:
   • Weekly
   • Monthly
   • Quarterly
   • Annual
4. Add rules:
   • Who can spend
   • Maximum spend per card
   • Maximum spend per transaction
   • Approval requirements for larger amounts

Example:

• Marketing budget: $20,000/month
• Individual card limit: $2,000/transaction
• Allowed MCCs: Advertising, Software, Travel
• Blocked MCCs: Gambling, Cash advances, Crypto, Entertainment

5) Configure merchant category controls

MCC controls let you allow or block spending at certain types of merchants.

Typical setup:

• Allow list: only specific categories can be used
• Block list: specific categories are prohibited
• Hybrid: allow most, but block sensitive categories

Common blocked MCCs:

• Cash advances
• Gambling
• Adult content
• Crypto exchanges
• Gift cards
• Entertainment
• Restaurants, if you want strict controls

Common allowed MCCs:

• SaaS/software
• Advertising
• Shipping/logistics
• Travel
• Office supplies

Note: MCCs are assigned by the merchant’s acquiring bank, so they are not always perfect. You may also want to use merchant-level rules or custom allow/deny lists in addition to MCCs.

6) Set spending rules by card type

Different cards may need different policies:

Employee cards

• Lower limits
• Specific MCCs only
• Receipt required
• Manager approval for exceptions

Team cards

• Shared budget for a department
• Higher limits
• More flexible MCCs

Vendor cards

• Single merchant only
• Fixed monthly amount
• Block all other merchants

Project cards

• Budget tied to project lifecycle
• Auto-expire when project ends

7) Add approvals and notifications

Useful controls include:

• Approval workflows for card issuance or limit increases
• Alerts when:
  • Budget hits 50%, 80%, 100%
  • A declined transaction occurs
  • A card is used at a restricted merchant
• Notifications to department owners or finance

8) Test policies before rollout

Do a pilot with one department first.

Test:

• A permitted merchant
• A blocked MCC
• A transaction above the limit
• A recurring subscription
• Card expiration or cancellation

Verify that the right transactions are approved/declined and that accounting data is captured properly.

9) Roll out with governance

Create a simple policy document covering:

• Who can request a card
• Who approves budgets
• Which MCCs are allowed/blocked
• Receipt and reconciliation requirements
• Lost/stolen card process
• Exception handling

10) Automate where possible

If your platform has APIs or webhooks, automate:

• Card creation from HR or procurement workflows
• Budget updates when a department is approved
• MCC rule assignment by card type
• Syncing transactions to accounting software
• Monthly budget resets

Example setup

Here’s a practical example:

Marketing department

• Budget: $15,000/month
• Virtual cards:
  • Ads card: only Advertising MCC
  • Tools card: SaaS and software MCCs
  • Events card: Travel + Office supplies
• Blocked MCCs: Gambling, cash advances, crypto, adult content
• Transaction limit: $3,000
• Receipt required for all transactions over $75

Key implementation tips

• Use separate cards per use case instead of one card for everything
• Prefer tight MCC allow-lists for sensitive budgets
• Combine MCC controls with merchant-level restrictions
• Build alerts and logs for auditability
• Ensure finance/admin can freeze or revoke cards instantly

If you want, I can also give you:

1. a step-by-step setup checklist,
2. a sample policy template, or
3. a comparison of virtual card platforms for this use case.