Skip to main content
Rynse cards aren’t open-ended fuel cards. Every card carries a set of rules — how much it can spend, where it can spend it, how often, and on what categories — and those rules are enforced at the moment of authorization, before the swipe goes through.
Spend Controls overview
Quick overview (~20 seconds)
Spend controls are configured by your Customer Success Manager, not directly inside the dashboard. This page is your menu — read it, decide what you want enforced for your fleet, then email your CSM with the changes. Most adjustments are turned around the same day.

​
How the layers fit together

Every authorization a card sends has to clear three layers. Your CSM can use any combination — one card might be governed by all three, another by just the org-wide ceiling.

Organization-wide rules

Apply to every card in your org automatically. Used for hard ceilings — e.g., “no single transaction over $100, ever, anywhere.”

Vehicle-specific policies

Named bundles of rules attached to specific cards. Different vehicle groups (police, admin, service trucks) can each have their own policy.

Category toggles

Per-card switches for the four standard fleet categories — Car Washes, Fuel – Gas, Fuel – EV, Preventative Maintenance. Fast way to authorize or revoke an entire category for one vehicle.

Enforcement, live

Rules are enforced by the card network at authorization time. A blocked merchant declines at the terminal — there’s nothing to reconcile after the fact.

​
The kinds of controls available

Tell your CSM in plain language what you want — they’ll translate it into the right combination of these primitives.

​
Per-transaction caps

A hard maximum on any single swipe. Use it to force a specific wash package or service tier.
  • Express washes only → $12 per transaction.
  • Premium washes allowed → $25 per transaction.
  • _Block any fuel fill-up over 100→100_ → 100 per transaction in the fuel category.
Per-transaction caps and monthly caps are independent. A 25per−transactioncapdoesn′tmeana25 per-transaction cap doesn't mean a 25 monthly cap — the vehicle can still spend $25 multiple times during the month, up to whatever monthly cap you’ve set (or no monthly cap at all). If you want both, ask your CSM to stack them.

​
Frequency / velocity caps

A limit on how often a card can be used over a window.
PeriodUsed for
Per transactionCap the single swipe (see above).
Daily”No more than two washes per day.”
Weekly”Up to $100 in EV charging per week.”
Monthly”4 washes per month per vehicle.”
All timeHard lifetime cap (rarely used).
Velocity can be expressed as a dollar amount (max $300/month) or an authorization count (max 4 transactions/month).

​
Merchant allow / block lists

Restrict cards to (or away from) specific vendors. Three ways to target a merchant:
  • By category (MCC) — broad (“all car washes,” “all gas stations”).
  • By merchant name — narrower (“Shell,” “ChargePoint”).
  • By merchant ID — exact, used when you want one specific store location.
Allow-list = card works only at the listed merchants. Block-list = card works everywhere except the listed merchants.

​
Category toggles

The four standard fleet categories that can be flipped on/off per card:

Car Washes

Standard wash MCCs. Leave on for any vehicle in the wash program.

Fuel – Gas

Gas-station MCCs. Off for vehicles that should never fuel on the card.

Fuel – EV

EV charging networks. On for EVs in the fleet.

Preventative Maintenance

Service / maintenance MCCs. Useful for service trucks and supervisor vehicles.

​
Real policy examples

These are the kinds of bundles your CSM puts together. Use them as a starting point when you describe what you want.
  • Per-transaction cap: $12, express washes only
  • Monthly allowance: 2 washes per vehicle ($40/month)
  • EV charging: weekly cap of $100
  • Categories enabled: Car Washes, Fuel – EV
  • Categories disabled: Fuel – Gas, Preventative Maintenance
  • Per-transaction cap: $25, premium washes allowed
  • Monthly wash allowance: 4 washes per vehicle ($140/month)
  • Combined monthly spend on repairs, EV charging, and fuel: $500
  • Categories enabled: all four
  • Per-transaction cap: 40onwash;40 on wash; 150 on fuel
  • Daily fuel cap: $200
  • Allowed vendors: any car wash, your preferred fuel network
  • Categories enabled: all four
  • Merchant allow-list: one specific car wash near the depot
  • All other merchants decline
  • Useful when you want zero risk of drivers using the card off-route

​
What this gets you

Prevent unauthorized upgrades

Drivers can’t bump up to a premium wash if the per-transaction cap is below that price.

Enforce program compliance

Wash limits are enforced at the pump — no manual reconciliation, no after-the-fact “talk to the driver.”

Track usage by vehicle type

With separate policies per fleet group, the Fleet Wash Health report makes utilization by group easy to read.

Surgical merchant control

Block one problem vendor, lock cards to one location, or grant exceptions — all without changing the rest of your program.

​
How to request a change

1

Describe the change in plain English

“I want our 12 admin vehicles capped at $25/wash and limited to 4 washes a month.” Don’t worry about the technical shape — your CSM translates.
2

Send it to your CSM

Email or Slack works. Reference the affected vehicles, facilities, or card numbers if you have them — otherwise your CSM will pull the list.
3

Confirm and go live

Your CSM applies the policy and confirms. The new rules are enforced on the very next authorization — there’s no nightly batch, no waiting period.
Not sure what to ask for? Send your CSM the Fleet Wash Health export for the vehicles you’re concerned about. The neglected list, the frequent washers list, and the wash history together usually point at the right policy shape.

​
What’s next

Vehicles

See which vehicles are in which group — useful for telling your CSM which policy applies where.

Fleet Wash Health

Once policies are in place, watch utilization to confirm the program is still healthy.