How to set up corporate cards
Corporate cards solve the reimbursement headache, but only if spend controls are built in from the start - not bolted on after the first surprise charge.
Why cards without controls fail
Issuing a card to every employee without limits or category rules just moves the reconciliation problem from receipts to statements - someone still has to figure out after the fact whether every charge was legitimate. Controls set at issuance prevent most of that cleanup instead of creating it downstream.
Where teams get it wrong
- Issuing physical cards with no per-transaction or monthly limit at all.
- Setting one limit for every employee regardless of role or spend history.
- No category restrictions, so a travel card can also buy software subscriptions.
- Relying on expense report review after the fact instead of controls at the point of purchase.
- No real-time visibility into pending charges, so a problem is discovered weeks later.
The Corporate Card Setup Framework
- 1Choose your issuing approach - virtual cards for most spend, physical cards where needed.
- 2Set per-cardholder limits based on role and spend history, not a single default.
- 3Restrict categories per card to the spend that role actually needs.
- 4Turn on real-time transaction verdicts so risky or out-of-policy charges are flagged as they happen.
- 5Route receipt capture and coding automatically so cardholders are not filing separate expense reports.
- 6Review card limits and categories quarterly as roles and spend patterns change.
How Fintra sets up cards with controls built in
| Step | What Fintra does |
|---|---|
| Choose issuing | Corporate cards issue through a provider registry - Stripe Issuing, Marqeta, Lithic, or Highnote plug in. |
| Set limits | Spend controls set per-cardholder monthly and per-transaction limits at issuance. |
| Restrict categories | Category restrictions bound each card to the spend types its role actually needs. |
| Real-time verdicts | Card webhooks feed SentriAI-powered real-time trust verdicts on anomaly and velocity as charges happen. |
| Automate coding | Expense management captures receipts and drafts GL coding automatically, no separate expense report. |
| Review | Spend controls and category rules are reviewable and adjustable as roles change. |
Card issuing itself runs on a real provider rail through the registry - pluggable, with a safe sandbox stub until credentials are configured - so teams can build and test the full control setup before connecting a live issuing account.
Your corporate card checklist
Set these up before issuing your first card
- Decide which roles get virtual cards versus physical cards.
- Set a per-cardholder monthly limit based on role, not a flat default.
- Restrict spend categories to what each role actually needs.
- Turn on real-time transaction verdicts before issuing live cards.
- Connect receipt capture so cardholders are not filing separate reports.
- Define an escalation path for declined or flagged transactions.
- Review limits and categories every quarter as roles change.
Frequently asked questions
What is the difference between virtual and physical corporate cards?
Virtual cards exist only as card numbers issued for a specific purpose - a subscription, a vendor, a project - and are easy to limit, pause, or cancel individually. Physical cards are needed for in-person spend like travel or client meals. Most teams issue virtual cards broadly and physical cards only to roles that genuinely need them.
How should spend limits be set for corporate cards?
By role and historical spend pattern, not a single default limit for the whole company. A sales rep with regular travel needs a different monthly limit and category set than someone issued a card only for a single software subscription. Setting the limit at issuance prevents most policy violations instead of catching them after the statement arrives.
What does real-time transaction verdict mean for corporate cards?
It means each transaction is evaluated as it happens - for anomaly, velocity, and policy fit - rather than reviewed after the statement closes. A charge outside a cardholder’s category restrictions or limit can be declined at the point of sale, which prevents the problem instead of requiring cleanup weeks later.
Is corporate card issuing a real banking product or just tracking?
It runs on a real card-issuing rail through a provider registry - options like Stripe Issuing, Marqeta, Lithic, or Highnote plug in - with a safe sandbox stub available until live credentials are configured. It is a real issuing capability, not a simulation, though the company issuing the cards is not itself a bank; the underlying issuing bank sits behind the provider.
Stay in the loop
One practical finance briefing a week - new guides, checklists, and benchmarks.
Issue cards with controls built in
Fintra sets limits and categories at issuance and flags risky charges in real time. Free to start, no card required.
Talk to us