Declined Tap to Pay Transactions

When a Tap to Pay transaction is declined by a bank, payment gateways (Stripe) and card networks return standardized failure reasons.

Here are the most common, legitimate card decline error messages/codes you will see in Tap to Pay logs, along with what they actually mean:

1. Most Common Bank Decline Messages

card_declined  / generic_decline  

• The customer's issuing bank declined the charge, but didn't provide a specific reason (most common for security/fraud blocks).
• Patron Fix: Call their bank or try a different card.

insufficient_funds  

• The card account doesn't have enough available credit or funds to cover the transaction amount.

do_not_honor  

• The customer's bank flagged the transaction as suspicious or unusual (e.g., a sudden donation at a new venue) and blocked it.

expired_card  

• The underlying card loaded into Apple Pay/Google Pay or the physical contactless card has passed its expiration date.

transaction_not_allowed  

• The card type isn't authorized for this specific merchant category (e.g., a corporate procurement card that blocks charitable donations).

2. Tap & Contactless-Specific Decline Messages

try_again_with_chip  / insert_or_swipe  

• The bank’s fraud system requested a higher level of security verification. The contactless chip refused the tap and requires the physical card to be inserted into a PIN pad or swiped.

contactless_limit_exceeded  

• In certain countries/banks, there is a hard maximum limit for contactless payments without entering a PIN (e.g., $250 or £100). If the donation exceeds that limit, the tap declines.

pin_required  

• The card issuer requires a PIN to authorize the transaction, which standard mobile Tap to Pay readers cannot collect.

security_code_incorrect  / authentication_required  

• The dynamic cryptogram generated by the phone/card chip failed the bank's security check (sometimes happens if the phone was pulled away from the device mid-tap too quickly).