Common transaction decline reasons
Declines can occur for several reasons, including system rules, card limits, and real-time risk checks. When a transaction is declined, a reason describing the cause is recorded with the transaction. This list is not 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 may not be available at all.
What you can do about a decline
Many declines are expected outcomes you can act on. The table below maps common reasons to their cause and your next step:
A few additional defaults worth noting:
- ATM withdrawals are disabled by default.
- Quasi-cash and certain money-transfer categories are restricted by default.
- 3D Secure (3DS): a failed 3DS verification can result in a decline.
- Address Verification (AVS): AVS is supported and configurable 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:
Default thresholds are shown above and may change over time as risk rules are updated.
Alongside these rules, transactions are also scored by a fraud risk engine; high-risk authorizations are declined with
transaction_declined_by_risk_rules.
Blocked categories and merchants
Whop Cards block certain merchant category codes (MCCs) 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

