Merchant Lock
Restrict to specific vendors: "AWS only" or "Hilton only."
Issuing · Coming soon
Your team shares one corporate card. Finance finds out about overages at month end
A licensed partner issues a virtual Visa or Mastercard per employee, vendor, or campaign. Gruv provisions them, sets per-card budgets and merchant locks, and surfaces every transaction as it happens.
Partner-issuedSpending controlsStatus oversight
Virtual Card
Marketing · Q4
4321 · 9180 · 0027 · 6642
Expires
12/27
CVV
•••
Issuer
Gruv
Spend Controlsv2 · enforced
Merchant category
Software · SaaS only
Per-transaction
$2,500 max
Expires
In 14 days · auto
Spent
$4,820
Remaining
$5,180
Where shared cards create blind spots.
Shared Physical Cards
Without on-demand issuance, five people share one corporate card. Procurement slows. Reimbursements stack up.
No Per-User Controls
Shared cards have no per-user limits, no merchant restrictions, and no transaction-level budget enforcement.
Manual Expense Matching
Matching receipts to statements drains hours from finance every month-end. And someone always loses a receipt.
Spend Appears After the Fact
Budget owners find out about overages when the statement closes. By then it is too late.
FX Conversion Surprises
International purchases on domestic cards trigger dynamic conversion fees and unfavorable rates.
Reconciliation Overhead
Allocating shared card transactions across departments and projects is manual work every month.
Gruv Solution
Issue virtual cards in minutes
Create a card per employee, vendor, or ad campaign. Set budgets, merchant locks, and expiry dates. See every transaction live.
Fast Issuance
A licensed partner issues virtual Visa or Mastercard numbers; provision them via API or dashboard. Cards are ready in minutes.
Per-Card Budgets
Set spending limits by amount, frequency, merchant category, or date range. Declines happen at the point of sale, not after.
Live Transaction Feed
See every auth, decline, and settlement as it happens. Webhooks and dashboard, real time.
Competitive FX
International purchases settle at competitive rates. No dynamic conversion fee surprises.
Card-to-Project Mapping
Each card maps to a team, project, or vendor. Month-end close gets simpler.
Merchant Locks
Lock a card to specific vendors or merchant categories. "AWS only" or "travel only."
Capabilities
Card Controls
Budget Caps
Hard daily, weekly, or monthly spend limits. Declines happen at the register.
Auto-Expiry
Cards self-expire after a date you set. Perfect for one-off trips.
Apple Pay and Google Pay
Push virtual cards to Apple Pay or Google Pay. Tap to pay in seconds.
How it works
Issuing Flow
Before vs after Gruv
Virtual cards as a payout method
Most card programs target spend management. Gruv adds partner-issued cards as a payout destination, alongside bank transfer, wallet, and crypto.
Dimension
Without Gruv
With Gruv
Issuance trigger
An admin creates cards in a separate spend management tool.
Cards issue as part of the payout flow when the corridor calls for it.
Limits and validity
Cards inherit a blanket policy from the spend program.
Per-payout limits, expiration, and merchant category carry on each card.
Reconciliation
Card spend reports reconciled separately from payout intent.
Each card ties back to the originating payout. One audit line.
Failure handling
Declined card transactions surface days later in reports.
Declines feed back into the payout workflow for fallback or reissue.
More in Payouts
Related capabilities on the same workflow
Data Ingestion
Pull payment data from QuickBooks, NetSuite, or affiliate platforms into Gruv via API, CSV, or email.
Automation
Set payout rules once in Gruv. Scheduling, approval routing, retries, and reconciliation run without manual steps.
Payee Experience
Give payees a branded portal to manage banking details, W-9s, W-8BENs, and payment history with Gruv.
Frequently Asked Questions
How many virtual cards can we issue?+
Limits depend on program configuration. Most setups support issuing cards per vendor, subscription, project, or employee.
Can employees add virtual cards to Apple Pay?+
Wallet provisioning depends on region and program. Confirm Apple Pay and Google Pay availability during evaluation.
How quickly can we issue a new card?+
Minutes. Once your program is enabled, cards provision via API or dashboard with controls applied at creation.
What does Gruv AI do across these features?+
Gruv AI automates payout routing, compliance gates, exception triage, and the Ask Gruv AI workspace. Every feature shares the same AI layer, so rules, holds, and reconciliation stay consistent.
Can I start with one feature and add more later?+
Yes. Gruv is modular. Start with one workflow and expand to additional modules as your needs grow.
How do I connect Gruv to our existing systems?+
Connect through APIs and webhooks, or start with file imports and exports for a fast evaluation. Email ingestion works for lightweight backfills.
What determines coverage, methods, and timelines?+
Coverage, methods, and timelines vary by market and are subject to compliance and policy checks. Confirm your target corridors and payout methods during evaluation.
Is this tax or legal advice?+
No. Tax and compliance features vary by jurisdiction and customer configuration. This content is for informational purposes and is not tax or legal advice.
See Gruv in action
A licensed partner issues a virtual Visa or Mastercard per employee, vendor, or campaign. Gruv provisions them, sets per-card budgets and merchant locks, and surfaces every transaction as it happens.
Many teams start with a narrow launch in weeks.