Why isn't a card authorized for autocharging?

You might occasionally see a message like this when attempting to autocharge a customer via WrestlingIQ's invoice feature:

This customer might have an active recurring subscription, or have paid for something in the past, and you might still see this message. What's going on?

Customers must explicitly authorize a card when saving their billing info

When checking out for a registration, or updating their card, your client needs to click this checkbox in order to authorize the card for autocharging:

Manually entering card information

If you tap the 'Add Card' button seen in the first screenshot, you as an admin can type in the customers card details. This is common in situations like a private lesson, where you want to bill them on the spot.

Saving a card this way also authorizes the card for future autocharges, it is up to you to convey this to your customer while typing in the card details, per your PCI compliance agreement.

Customers can always revoke access

Recent credit and debit card regulations state that customers must always be given a choice to revoke their authorization—which means that anyone with a card on file can revoke access at anytime to autocharging.

What if I am owed money from a client who revokes access?

As a business, you should always be collecting money upfront or at the time of service.

If you are owed money, the best way to deal with it is to send an invoice via WIQ, document the service you provided, and take them to small claims court. Most small claims courts processes are surprisingly easy, with clerks that are quite helpful.

We do not recommend autocharging a customer that you know will charge the transaction back. Visa/Mastercard has rules on the volume and ratio of chargebacks a payment processing account is allowed to have (due to money laundering / scam sites), so you may be putting your entire processing account at risk.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us