Introduction
Feature Summary: When a payment fails in CourtPay, Stripe returns a decline code explaining why. Understanding these codes helps your staff respond quickly, guide members to a resolution, and keep revenue flowing.
Use Cases:
General credit card declines: AVS, CVV, insufficient funds and more
ACH bank transfer decline codes (R-codes)
Stripe and CourtReserve payment errors, plus in-person card reader payments
Best practices and escalation guidance
Overview
This guide is for club administrators on CourtPay.
Many decline decisions are made by the cardholder's issuing bank, not by CourtReserve or Stripe.
Getting support. CourtPay is powered by Stripe, and CourtReserve support is your first stop for any payment question; you don't need to contact Stripe directly. Reach us at support@courtreserve.com.
Find a Declined Payment
Declined payments appear on the Transactions tab in CourtPay with a Failed status.
Select the CourtPay tab, then select Transactions.
Click Status, select Failed, then click Apply.
Click a payment to view its details, including the decline reason.
To export payments, including the decline reason:
On the Transactions tab, click Export.
In the Export payments window, select a Date range: Today, Current month, Last 7 days, Last month, All, or Custom. If you select Custom, enter a start and end date.
Under Columns, select one of the following:
Default (23) - The standard set of columns, including Decline Reason.
All (83) - Every available column.
Custom - Select the columns you want from the list.
Click Export.
The file downloads as a CSV, which you can open in Excel or Google Sheets.
Tip: When exporting declined payments with Custom, include Decline Reason, Seller Message, and Status. For address or security code declines, also include Card AVS Line1 Status, Card AVS Zip Status, and Card CVC Status.
Part 1: Credit Card Declines
Credit card declines are either soft (temporary, may succeed on retry) or hard (permanent, require cardholder action first).
1A. General Decline: "Do Not Honor" (Code 05)
The issuing bank rejected the transaction without a specific reason. Triggered by fraud suspicion, spending limits, or internal bank rules.
Resolution
Ask the member to call the number on the back of their card.
Suggest an alternate payment method if the transaction is time-sensitive.
Do not retry the same card immediately; wait at least 24 hours.
1B. Insufficient Funds (Code 51)
The cardholder's balance or available credit is below the transaction amount. Accounts for about 40–50% of all failed payments.
Resolution
Debit cards: member should transfer funds or use a credit card instead.
Credit cards: member may be at their limit; suggest a different card.
Offer to retry in 24–48 hours after the member confirms funds are available.
Soft decline: retrying the same card too aggressively can trigger additional bank blocks.
1C. AVS Decline: Address Verification Failure
The billing address (street number and/or ZIP) entered at checkout doesn't match what the card's issuing bank has on file. AVS reads numbers only; street number and ZIP are the critical fields.
Resolution
Ask the member to re-enter their billing address exactly as it appears on their bank statement.
Common causes: recent move, billing ZIP differs from shipping ZIP, missing unit/apt number.
If the address is correct and still declining, the member must call their bank to update the address on file.
Tip: AVS mismatches often happen after a move. The member needs to update their address with their bank first, then retry or use another card.
1D. CVV / Security Code Mismatch (Code 97)
The 3-digit CVV on the back of the card (or 4-digit on the Amex front) doesn't match the issuer's record. It confirms the member has the physical card.
Resolution
Ask the member to carefully re-enter the CVV; it's easy to misread.
If still mismatching, the member should call their issuing bank.
Repeated CVV mismatches on online or phone orders may indicate fraud; do not override without verifying identity.
1E. Quick Reference: Common Credit Card Codes
Code | Message | Reason | Action |
05 | Do Not Honor | Generic bank refusal | Member calls issuer; try alt payment |
51 | Insufficient Funds | Low balance / credit limit | Wait 24–48 hrs; try alt card |
14 | Invalid Card Number | Typo in card number | Re-enter card number |
54 | Expired Card | Card past expiration date | Ask for updated card |
41 | Lost Card | Card reported lost | Ask for different card; do not force |
43 | Stolen Card | Card reported stolen | Ask for different card; do not force |
62 | Restricted SIC or MCC | Card does not approve this type of purchase | Member calls issuer; try alt payment |
97 | CVV Mismatch | Security code doesn't match | Re-enter CVV; member calls issuer |
N/A | AVS Mismatch | Billing address mismatch | Re-enter address; member updates address with bank |
Part 2: ACH / Bank Transfer Declines
ACH payments pull funds directly from a member's bank account. Failures generate R-codes. Unlike credit card declines (near-instant), ACH returns take 1–2 banking days; unauthorized returns can take up to 60 calendar days.
Code | Reason | Retry? | What to Do |
R01 | Insufficient Funds | Yes, once; wait 3–5 days | Notify member; suggest they fund account or switch to card |
R02 | Account Closed | No | Contact member for updated bank info; do not retry closed account |
R03 | No Account / Unable to Locate | No; fix data first | Re-enter routing and account numbers in CourtReserve |
R04 | Invalid Account Number | No; fix data first | Re-enter routing and account numbers in CourtReserve |
R05 | Unauthorized Debit (Corp Code) | No; NACHA violation | Stop all retries; obtain new written authorization; re-enter ACH details in CourtReserve |
R07 | Authorization Revoked | No | Member revoked authorization; stop payments; contact member |
R08 | Payment Stopped | No | Member issued stop payment; contact member to resolve |
R09 | Uncollected Funds | Yes; wait 3–5 days | Funds present but not cleared; retry after settlement |
R10 | Not Authorized | No; NACHA violation | Immediately stop; resolve directly with member |
R16 | Account Frozen | No | Member must resolve with their bank |
R20 | Non-Transaction Account | No | Member provided savings account; collect checking info |
R29 | Not Authorized (Corporate) | No; NACHA violation | Stop all recurring debits immediately; get new authorization; re-enter ACH details in CourtReserve |
ACH Best Practices
Never retry an unauthorized return (R05, R07, R10, R11, R29) without new written authorization; doing so violates National Automated Clearing House Association (NACHA) rules.
For R01/R09: wait 3–5 business days before one retry. Cap at one retry.
For R02/R03/R04: collect updated bank details. Always request a voided check; manually entered numbers are the #1 source of R03/R04 returns.
Validate bank account details at enrollment to catch errors before the first debit.
Part 3: Stripe and CourtReserve Errors
These errors appear in CourtReserve when an issue occurs beyond a standard bank decline. Many require action from you, the member, or our Support team.
3A. Stripe Decline Codes
Stripe Code | Meaning | Action |
insufficient_funds | Balance or credit limit too low | Ask for alt card; retry after 24–48 hrs |
card_declined | Generic issuer decline | Member calls number on back of card |
incorrect_cvc | CVV/CVC entered is wrong | Re-enter CVV carefully |
incorrect_zip | ZIP code doesn't match issuer records | Re-enter correct billing ZIP |
expired_card | Card past expiration date | Update card on file |
lost_card | Card reported lost | Request different payment method; do not force |
stolen_card | Card reported stolen | Request different payment method; do not force |
fraudulent | Stripe fraud detection flagged transaction | Do NOT disclose reason; present as generic decline; escalate if recurring |
do_not_honor | Issuer declined without explanation | Member contacts issuer; suggest alt payment |
card_velocity_exceeded | Too many charges in short period | Wait before retrying; member contacts issuer |
processing_error | Temporary Stripe processing error | Retry once immediately; escalate if it persists |
For fraudulent declines: never tell the member that fraud was detected. Simply say the payment didn't go through and ask for a different method.
3B. Payment and Refund Errors
Transaction not voided: already settled
What it means: Appears after initial authorization but before the transaction has fully settled with the bank. The transaction is in a pending state.
Wait 12–24 hours for the transaction to fully settle.
Then issue the refund. Do not attempt to void or refund while pending.
Transaction not eligible for refund: use a void instead
What it means: Occurs when (1) you are attempting a partial refund and (2) the original payment has not yet settled.
Option A: Refund the full payment amount, then rerun the card for the correct amount.
Option B: Wait for the transaction to fully settle, then issue the partial refund.
Invalid ABA number
What it means: The routing number or account number entered does not match the customer name or does not correspond to an existing account. Typically a typo or data entry error.
Request a voided check from the member to confirm routing and account numbers.
Correct the payment profile and resubmit.
This is a data or member-side error, not a CourtReserve system issue.
Bank account already exists on this account
What it means: The same routing and account number is already attached to this member and cannot be added again.
Contact CourtReserve Support to remove the existing bank account entry.
The member can then re-add the bank account in CourtReserve.
No such charge
What it means: Typically appears after switching payment providers. The referenced transaction occurred with a previous processor that your CourtReserve account is no longer connected to.
If processing a refund, it must be issued directly in your previous payment provider's portal.
CourtReserve cannot access or refund transactions from a disconnected processor.
Part 4: In-Person (Card Reader) Payments
Card reader payments use the same Stripe decline codes as online payments, so Part 1 and the Stripe table in Part 3 apply at the front desk too. Only a few codes and issues are specific to card readers.
4A. PIN-Related Declines
Stripe Code | Meaning | Action |
incorrect_pin | The PIN entered was wrong | Ask the member to try again with the correct PIN |
offline_pin_required | The card requires a PIN | Ask the member to insert the card and enter their PIN |
online_or_offline_pin_required | The card requires a PIN | Enter the PIN if the reader prompts for it; otherwise insert the card and enter the PIN |
These usually happen when a member taps a card that their bank wants verified with a PIN. They're soft declines, and the payment typically goes through once the member inserts the card and enters the PIN.
4B. Card Reader Troubleshooting
These are reader or connection problems, not bank declines.
Issue | What It Means | What to Do |
Reader offline | Stripe hasn't received a signal from the reader in the past 2 minutes | Check power and the internet connection, restart the reader, then try again |
Connection error | The reader couldn't connect to Stripe | Check the internet connection and retry once |
Chip can't be read | The reader couldn't read the card's chip | The reader prompts the member to retry automatically; reinsert slowly, or try another card |
Card read timed out or card removed | The card was removed too early or took too long to read | Restart the transaction and leave the card inserted until the reader says to remove it |
Reader busy | The reader is still handling another transaction | Let the current transaction finish, or cancel it, before starting a new one |
If a restart and connection check don't fix it, contact CourtReserve Support with the error message and the time it happened.
Note: For help setting up or pairing a reader, see CourtPay: How to Connect Your Stripe Reader S700.
Part 5: Best Practices and Key Reminders
Process every refund and payment in CourtReserve. That keeps each transaction recorded in CourtReserve and in your payout reports.
Talking to Members About Declines
Use neutral language: "Your bank flagged this transaction," not "your card was rejected."
Keep decline conversations private; never discuss details in front of other members.
The fastest resolution path: the member calls the number on the back of their card.
Offer to hold a reservation or membership spot while they resolve it.
Reducing Declines Over Time
Prompt members to update payment methods before card expiration.
Collect a voided check when there is an ACH payment issue to confirm details.
For recurring billing, run charges early in the cycle when member balances are typically higher.
Monitor decline rates in CourtReserve reporting; a spike in one code often signals a fixable issue.
When to Contact CourtReserve Support
You are receiving declines for every transaction; contact CourtReserve immediately.
The same decline code is appearing across multiple members (may indicate a CourtReserve issue).
An error is not listed in this guide, and you need more guidance on what to do next.


