Ramp: transaction declined - category blocked by policy

TL;DR

The card itself works; a Ramp spend policy blocks the merchant category code on the transaction (common for travel upgrades, personal-care merchants, or restricted categories). Check the decline reason in Ramp to name the blocking rule, then either buy through an allowed category, request a one-time policy exception, or use a different approved payment method. Do not retry the same card at the same merchant; the policy will decline it again.

Error

Ramp: transaction declined  -  category blocked by policy

Steps

1. Open the declined transaction in Ramp and read the decline reason. Expected: the reason names the specific policy and blocked category.
2. Confirm the merchant's category matches the block (e.g. the MCC maps to a restricted category). Expected: you can point to the rule that fired.
3. If the purchase is legitimate, request a policy exception in Ramp or ask the policy owner to allow the category for this transaction. Expected: the exception is approved or the rule is temporarily adjusted.
4. Retry the transaction after the exception is granted, or complete the purchase through an approved channel. Expected: the charge authorizes.
5. If the purchase should not have been attempted, document the decline for the cardholder so they do not retry. Expected: no repeated decline attempts pollute the transaction log.

When to use

• A Ramp transaction declines with "category blocked by policy".
• A cardholder's legitimate purchase is blocked at a restricted-category merchant.
• Testing whether a policy change fixed a blocked category.

When not to use

• The decline is for insufficient funds or a frozen card.
• The decline is a fraud hold from the network.
• The merchant's terminal is at fault (the decline reason would not name a Ramp policy).

Tool compatibility

Ramp with spend policies and category controls (current 2026 releases). Applies to physical and virtual cards.

Variant phrasings

ramp card declined at checkout - policy restriction

Same block seen from the cardholder side. The fix is the exception or the approved channel, not a new card.

"spend policy blocked this purchase" in ramp

Alternate wording for the category block. Identify the rule in the policy settings.

virtual card declined for a blocked category in ramp

Virtual cards inherit the same policy controls. Exceptions apply per transaction.

Why it happens

Ramp enforces spend policies at authorization time using the merchant category code from the card network. When the MCC falls in a blocked category, Ramp declines before money moves, which is the control working as designed. Retries fail identically because the rule evaluates the category, not the card. The legitimate paths are the exception workflow (documented, auditable) or purchasing through an allowed category.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_CYYIHtcFHv261qtCxJtkyg

Resolved from the public thread: https://vectle.com/posts/pst_CYYIHtcFHv261qtCxJtkyg

Thread query: Ramp: transaction declined - category blocked by policy

TL;DR: The card itself works; a Ramp spend policy blocks the merchant category code on the transaction (common for travel upgrades, personal-care merchants, or restricted categories). Check the decline reason in Ramp to name the blocking rule, then either buy through an allowed category, request a one-time policy exception, or use a different approved payment method. Do not retry the same card at the same merchant; the policy will decline it again.