Menu

Credit Card Chargebacks & Fraud

We ADORE data (& honesty!) over here, and have had some great questions recently about issues like credit card chargebacks and fraud. So - rather than speaking in generalities, we pulled the data. The short answer (and the good news) - chargebacks and fraud are *really* not big issues for Thinkific instructors. But don’t just take our word for it - we ran the numbers. 


At the highest level: 


  • We looked at $2 Million in recent transactions to be sure we had a good sample size (offset to ensure time had passed for chargebacks to occur, for accuracy)

  • Chargebacks are transactions reversed for a variety of reasons, including possible fraud. Visa & Mastercard consider 1% to be the threshold for these. For Thinkific tenants, the average chargeback rate on our system is 0.1% - or one in a thousand transactions. It’s extremely low! 

  • Failed transactions are different than chargebacks, and occur when an attempt to pay you fails at the time of purchase. Failed transactions are frustrating, as you can see a student is trying to purchase but can’t. Normal failure rates for credit card purchases online are in the 10-15% range typically across any platform. That ends up artificially high though when the same student tries over and over to re-run the same card. 

    Instead, what we’re more interested in is unique failures - how many students tried to purchase, but left without completing a successful transaction? After we remove duplicate transactions and folks who subsequently had a successful payment, the rate of complete failures across the $2 Million in transactions we looked at was just under 1%. Anecdotally, when speaking with our own customers with failing transactions, about half tend to be over limit issues, and the other half aggressive bank policies. As a 
    whole though, a very small percentage of transactions. 


What can you do to ensure you maximize transaction success & reduce risk? 


  • Most purchasers (about 90%) with a card that doesn’t go through on first try will try a different credit card, which is usually the fastest route to success. You can also offer PayPal as a secondary purchase option. If your students contact you, their best bet is to use a different card, or contact their bank to find out why their transaction is being declined. If you’re in a different country from your student, the bank may have stricter rules about what it accepts or doesn’t accept for example. Unfortunately, a small percentage of purchasers won’t be successful (on our platform, that tends to be less than 1% overall). 

  • How can Thinkific maximize payment success? We already require CVC (that 3 digit security #) on your credit card purchases, and according to Stripe, this combined with card # and expiry are the primary factors that the customer’s bank uses to accept or decline the transaction. 


Does PayPal have a higher success rate? 


  • No! In fact, our data shows us that PayPal has a much lower conversion rate than Stripe payments, as purchasers are taken away from your site/branding, they’re asked to setup a PayPal account, and similar barriers. The difference though, is that you won’t see the failure rate with PayPal - they ONLY show you the successful transactions. This means that, unlike Stripe, you can’t see which students struggled with checkout.

    To corroborate, one external report shows 12% failures for Stripe and a high 20% failure rate for PayPal, for a similar platform to ours.


Help! My chargeback rate is really high, and I want to take steps to reduce it. 


Note: we don’t know of any instructors on Thinkific who are over the Visa & Mastercard thresholds for chargebacks. If that ever happens or if you’re concerned though, read on! 


  • Chargebacks are transactions reversed for a variety of reasons, including possible fraud. Visa & Mastercard consider 1% to be the threshold for these. For Thinkific tenants, the average chargeback rate on our system is 0.1% - or one in a thousand transactions. It’s extremely low! 

  • Chargebacks occur when your customers (or their banks, on their behalf) reverse credit card transactions. Commonly, this happens if their credit card is compromised, and all recent transactions are reversed. This also happens when the purchaser reports the transaction as fraud/unauthorized to their bank. 

  • The #1 way to prevent or reduce chargebacks? Deliver what you promise! Instructors who don’t deliver on what they promised purchasers or don’t honour refund policies, for example, are likely to have a much higher chargeback rate than instructors who have great relationships with their students. This just makes sense! 

  • When a chargeback is filed, as the merchant you have the ability to refute the claim. This is about gathering some data and sending it in. Stats vary, but it’s estimated only approximately 40% of chargebacks are closed in favour of the merchant, so the unfortunate thing is that data isn’t always enough. If you are faced with a chargeback however, here are some hints for what to send in to prove the student accessed your course legitimately: student activity data (from our own system, and from tools like Mixpanel), any emails with your student, discussion forum access/comments (especially if they used their name) and even if they’ve claimed their certificate (or possibly added it to LinkedIn). We have a limited number of chargebacks in our system, but those successful in refuting them used data like this to do so. 

  • If you are uniquely concerned about your own chargeback rate, you have the option to force Stripe to decline transactions where the customer’s CVC doesn’t match. THAT said, it’s important to note that once done, you will not be able to see failed transactions where they’re failing for this reason in your Stripe logs. This will make it appear that you have fewer failed transactions, but what it really means is that they’re failing earlier in the process, so they never even show up. Declining transactions for a mismatched CVC can also incorrectly capture valid transactions, so is recommended ONLY if you have an abnormally high chargeback rate and are trying to reduce it. Do this with caution! Many of the transactions declined for CVC mismatch are legitimate, so doing so will likely increase your unique purchaser failure rate. 


What about AVS data? 


  • AVS (address verification data) is primarily used not to authorize transactions by the bank, but for merchants to verify that the address they’ve been given to ship goods to matches that of the credit card. We’ve never introduced AVS matching in large part because we’re not a platform for shipping physical goods. Normally, if a chargeback occurs, merchants who have shipped physical goods to customers will be out the cost of the products they provided, making AVS relevant for those merchants. 

  • AVS only works for Canadian, US & some UK credit cards, as it is not a global program. As such, it absolutely cannot do anything to limit fraud from other countries. 

  • Even for legitimate transactions, customers entering their own address information frequently get mismatched results. This article shares that AVS matches typically are in the range of just 40-80%, and that of those transactions that are declined due to AVS mismatch, only a small fraction were actually potential fraud (!). As an instructor, if you were to force AVS matching for your purchases you would be potentially denying 20%+ of your legitimate transactions, to offset a fraction of the average 0.1% chargebacks we see on our platform. 

If you run into issues with chargebacks or failure rates above the averages we've identified here, or have specific concerns about a transaction, please do reach out to us and we'll be happy to help!

We hope this helps clarify chargeback & fraud issues. Please contact us if you've got any questions at all - we take security and credit card processing extremely seriously, and want to ensure everyone is successful in their online businesses. 

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.