Merchant Lock
Restrict to specific vendors: "AWS only" or "Hilton only."
Plan a virtual card per employee, vendor, or campaign. Confirm issuer, network, eligibility, controls, funding, transaction events, and wallet support before rollout.
Without on-demand issuance, five people share one corporate card. Procurement slows. Reimbursements stack up.
Shared cards have no per-user limits, no merchant restrictions, and no transaction-level budget enforcement.
Matching receipts to statements drains time from finance every month-end, especially when receipts are missing.
Budget owners find out about overages when the statement closes. By then it is too late.
International purchases on domestic cards trigger dynamic conversion fees and unfavorable rates.
Allocating shared card transactions across departments and projects is manual work every month.
Create a card per employee, vendor, or ad campaign. Set budgets, merchant locks, and expiry dates. See every transaction live.
Submit an approved card request and track its requested, under-review, active, frozen, or closed status.
Set spending limits by amount, frequency, merchant category, or date range. Declines happen at the point of sale, not after.
See every auth, decline, and settlement as it happens. Webhooks and dashboard, real time.
International purchases settle at competitive rates. No dynamic conversion fee surprises.
Each card maps to a team, project, or vendor. Month-end close gets simpler.
Lock a card to specific vendors or merchant categories. "AWS only" or "travel only."
Restrict to specific vendors: "AWS only" or "Hilton only."
Hard daily, weekly, or monthly spend limits. Declines happen at the register.
Cards self-expire after a date you set. Perfect for one-off trips.
Offer wallet provisioning only where the approved issuer, network, device, and program support it.
Most card programs target spend management. Gruv adds partner-issued cards as a payout destination, alongside bank transfer, wallet, and crypto.
Pull payment data from QuickBooks, NetSuite, or affiliate platforms into Gruv via API, CSV, or email.
Set payout rules once in Gruv. Scheduling, approval routing, retries, and reconciliation run without manual steps.
Give payees a branded portal to manage banking details, W-9s, W-8BENs, and payment history with Gruv.
Next step
Tell us what you are trying to do, where it needs to work, and how your team handles it today.
Contact the team