Card policies
The rules every card follows, set once, enforced at authorisation.
A policy is merchant categories, limits, and receipt requirements. Applied to a group of cards it means new cards inherit the rules rather than being configured individually and inconsistently.
Enforcement happens at authorisation. A transaction outside policy is declined at the terminal, which is different from being flagged in a report a week later.
How to work this page
Field staff, office, executive. A new hire inherits the policy of their role.
Below it, chasing receipts costs more than the risk. Above it, a missing receipt is a deduction you can lose.
An allow list of categories is tighter than a block list, because a block list has to anticipate every category you did not think of.
Repeated legitimate declines mean the policy is wrong. People route around a policy that stops their work.
On a phone
Every figure from the desktop appears here, stacked rather than reduced. Tables scroll inside themselves so the page never moves sideways, and figures keep their separators and their alignment at every width.
Questions people actually ask
Yes, and it is granted as a temporary limit raise with an expiry rather than a permanent change.
Yes, and a virtual card locked to a single merchant is the tightest control available.