Charge Errors
Overview
A Customer's credit card may not work when purchasing, so the PodPlay system has notifications in place for every charge-failure scenario. Depending on the reason, either the Customer or the Admin is notified immediately, and in all cases an audit trail of the error is recorded for an Admin to review on the Purchase Page of the Dashboard.
Customers in Booking Flow
How the system handles a failed card depends on when the Customer is booking. During the booking flow the Customer is stopped immediately. For bookings made further out, the hold runs later and the outcome depends on whether your Club has a front desk.
When a card fails while the Customer is booking a Reservation or signing up for an Event, a notification appears immediately, the Customer cannot complete the booking, and they see one of these messages:
Your cc zip code is incorrect; please update your cc and try againYour cc CVC is incorrect; please update your cc and try againThis card does not work; please change your cc and try again
The system prompts the Customer to update the card on file. Once updated, they can complete the booking.
How timing changes what happens
The system's default behavior changes based on how far out the Reservation or Event is.
Less than 6 days out: The system tries to place a hold on the card at booking. If the hold fails, the Customer sees one of the messages above on the final page of the booking flow and is asked to update their card and try again.
More than 6 days out: The system lets the Customer book the Reservation or join the Event, then places the hold 24 hours before it starts. The delay is due to the legal classification of the product type: sports entertainment. If the hold succeeds, everything proceeds normally. If it fails, handling depends on your Club's setup:
Clubs with a front desk: the Customer is emailed that their card did not work and should be updated as soon as possible. Front desk staff can charge the Customer when they arrive. See Admin intervention during charge errors.
Clubs without a front desk (Autonomous Clubs): the Customer is emailed that their card did not work, that they should update it, and that they need to sign up or book again. The system removes the Customer from the Event or cancels the Reservation because the hold failed. Autonomous Clubs have no front desk staff to engage the Customer on arrival. In both more-than-6-days cases, the system does not notify the Waitlist. The Waitlist is notified only when a Customer cancels their participation in an Event.
To learn more, read about the Hold-on-Card Process.
Spotting a failed card at the Club
On the Reservation or Event attendee list, a Customer whose card failed appears highlighted in red (monitoring the Overview page and clicking on the upcoming Events or Reservations is the easiest way to catch a card issue early).

Hovering over the red card icon shows a tooltip explaining the failure.

Front desk staff can then ask the Customer to update their card and charge them for the Reservation or Event.
Staff also see an audit trail on the Purchases page of the Dashboard. A failed charge is visible there with its source listed as Booking or Event Signup, both initiated by a Customer.

Membership Subscription Failures
When a Customer buys a Membership in your Club's App, if there are any issues with their card, the system will not provide them with the Membership and will prompt them to update their card on file before trying to purchase the Membership again.
When a Customer has a Membership and the subscription charge fails because of insufficient funds, has the wrong zip code or CVC on file, or there's an authentication failure, the system notifies the Customer by email that their Membership charge failed. The email sent to the Customer is automated and informs the Customer to update their card as soon as possible, and the Customer then enters a GRACE/HOLD period. The failure is then recorded on the Purchase Page of the Dashboard.

Failed Charges from Dashboard
When stafff charges a Customer from the Dashboard and the card on file does not work, a unique flag appears on the Purchase tab of the Event or Reservation reading "Charge Failed."

Inside the Purchase Page of the Dashboard, the flag reads "Charge Failed" and "Customer Service," indicating that staff attempted the charge.

When this happens, staff at the front desk can ask the Customer to update their card and try again. If the second attempt fails, the Customer's bank has likely stopped the charge as a fraud-protection measure, or a different card is needed. Staff cannot always see the reason directly, Stripe surfaces the bank's two stated reasons inside the Customer's Profile, under the Purchase tab, within that specific purchase.


Review Failed Charges in Dashboard
Staff can review exactly why a charge failed when opening up the details of a charge. To do so:
Open the Purchase tab: Inside a Reservation, Event, or the Customer's Profile
Click on the charge details: Click the blue highlighted link in the Purchase Detail column. A new side panel appears.
Scroll to the Payments drawer: Scroll to the bottom of the side panel until you reach Payments.
Click on the Status Flag: Click the "Failed" Status Flag header. A new window appears showing why the charge failed.
Why a charge failed
Invalid zip code on the credit card

Insufficient funds on the card

Security authentication on the card was not completed

The Customer's bank sent back a do-not-honor code — this may require the Customer to contact their bank or check their email to release the security hold before the charge can go through

Reattempt the charge
If you want to try the charge again, you can charge from the Dashboard or send the Customer a Payment Link. Some of the bank and/or security restrictions are outside the PodPlay system and may require the Customer to act before another charge can be completed and captured.
Intervention on Charge Errors
Sometimes staff will need to step in and help complete the charge; other times, the Customer will need to rectify the charge failure. Here are the different cases:
Staff must intervene and charge from the Dashboard if the Customer receives a charge failure for:
A missed hold on Event or Reservation (>6 days) (related)
A failed charge for a Coach on a Reservation (related)
A charge from the Dashboard fails (related)
A failed charge for a Replay (related)
Customer must retry an action if there is a charge failure during:
Event signup (related)
Reservation booking (same as above)
The system will attempt another charge if the charge failure is for a Customer’s:
Membership subscription charge (related)
Last updated
Was this helpful?

