Digital products, chargebacks and payment processor risk

A card processor pays you before it knows whether the sale will stick. If a customer disputes the charge weeks later, the card scheme takes the money back from the acquirer, and the acquirer recovers it from you. With a physical product there is usually a tracking number, a delivery signature and a returned parcel to argue with. With a digital product there is often only a login timestamp, which issuers rarely find persuasive.

Three features stack the risk. Delivery is instant, so a dissatisfied buyer has already received everything before complaining. Value is subjective, so 'the course was not what I expected' is hard to rebut. And many digital businesses sell through paid social traffic, where impulse purchases and buyer's remorse are common. Underwriters have seen enough accounts fail on this pattern that they price for it from the start.

Processors do not usually react to one bad week. They react to trends their monitoring flags automatically. The most common triggers for digital-product merchants are a sudden spike in volume after a launch or viral ad; a rising refund rate, even if chargebacks stay low; chargebacks coded as 'product not received' or 'not as described'; recurring billing customers did not clearly agree to; high-ticket offers such as coaching or masterminds sold on a single call; income-claim marketing ('make 10k a month'); and a mismatch between what the account application described and what the website actually sells.

Launch-based businesses are hit hardest. A course that does 80 per cent of its yearly revenue in a five-day window looks to a risk model exactly like a merchant collecting money before disappearing. If you plan a launch, telling your processor in advance is often the difference between a smooth payout and a frozen balance.

Many founders believe refunds are bad and should be avoided. For card risk, the opposite is usually true. A refund is a voluntary return of money that the card schemes do not count against you. A chargeback is a forced reversal that is counted, carries a fee, and pushes you toward monitoring programmes once your ratio passes the scheme thresholds, typically around 0.9 to 1 per cent of transactions depending on the scheme and programme.

A generous, clearly written refund policy that is easy to find and easy to use turns many would-be chargebacks into refunds. The refund rate still matters, because a very high one tells the processor something is wrong with the offer, but it is far less damaging than the same number of disputes. Refunding quickly when a customer complains, before they call their bank, is one of the cheapest risk controls available.

Closures usually follow one of a few paths. The first is a chargeback ratio that stays above scheme limits for consecutive months. The second is a business-model mismatch: the account was opened for 'software' and the processor later finds high-ticket coaching with income claims. The third is a sudden, unexplained jump in volume that the risk team cannot reconcile with your history. The fourth is a pattern of customer complaints, including on social media or review sites, that suggests deceptive marketing.

Aggregators such as the large online checkout platforms are especially quick to act, because they onboard merchants with light underwriting and rely on monitoring afterwards. That is why many digital businesses that started on an aggregator eventually move to a dedicated merchant account, where the business is underwritten properly once and the terms, including any reserve, are agreed up front.

The practical controls are not complicated. Put clear product descriptions, deliverables and access terms on the sales page. Use a billing descriptor customers will recognise on their statement, since 'I don't recognise this charge' is a major chargeback cause. Send a receipt and an access email immediately, and keep logs of logins and downloads. Make recurring billing obvious at checkout, send renewal reminders, and make cancellation easy. Avoid income guarantees and before-and-after earnings claims in ads. Answer support tickets fast and refund early when a customer is clearly unhappy.

On the payments side, use a chargeback alert service where your processor supports one, so you can refund a disputed sale before it becomes a counted chargeback. Keep a written dispute evidence pack per product: terms accepted at checkout, delivery proof, usage logs and support correspondence. And keep at least one backup payment route, so that a pause on one processor does not stop your business.

If you are processing steady monthly volume, run launches, sell high-ticket programmes or have already had a pause or closure, a dedicated merchant account underwritten for your model is usually more stable than an aggregator. The application will ask for processing history, refund and chargeback figures, your sales pages and funnel, your terms and refund policy, and the business's ownership and bank details. A reserve may be part of the approval, especially for launches or high-ticket offers, and it is normally reviewed after a clean track record.

Xavion works with digital-product and online-education businesses to prepare that application honestly, match the business with acquirers whose risk appetite fits, and set up backup rails. We do not promise approval, we do not help disguise what is being sold, and we will tell you plainly if the marketing or refund practices need to change first.