Common transaction decline reasons
Declines can occur for several reasons, including system rules, card limits, and real-time risk checks. When Whop declines a transaction, it records a reason with the transaction. This list isn’t exhaustive. Some declines originate at the card network or processor rather than from a Whop rule, and these take precedence. In those cases, the reason may be a generic description such asrestricted card, or Whop may not receive a reason.
What you can do about a decline
Many declines represent outcomes you can act on. The following table maps common reasons to their cause and your next step:
A few additional defaults worth noting:
- Automatic teller machine withdrawals are unavailable by default.
- Whop restricts quasi-cash and certain money-transfer categories by default.
- 3D Secure (3DS): a failed 3DS verification can result in a decline.
- Address Verification Service (AVS): Whop supports this service and lets you configure it per card. Mismatches can contribute to a decline.
Authorization codes and their meanings
Whop Cards use specific authorization codes to classify the context and status of each transaction. Here are some commonly encountered codes:Risk rules enforced during authorization
Whop Cards enforce automatic risk detection rules to prevent high-risk or suspicious transactions. Each rule includes a time window and trigger threshold:
The table shows default thresholds. Whop may update them over time as risk rules change.
Alongside these rules, a fraud risk engine scores transactions. Whop declines high-risk authorizations with
transaction_declined_by_risk_rules.
Blocked categories and merchants
Whop Cards block certain merchant category codes and specific merchants by default. See Blocked categories & merchants for the full lists.Next steps
Blocked categories & merchants
See the merchant categories and merchants that Whop Cards block by default
Whop Cards
Spend your balance instantly and earn cashback on select merchants

