The Invisible Chargeback Trigger

Friendly fraud accounts for an estimated 17% of fraudulent disputes, according to the 2026 Global eCommerce Payments & Fraud Report.[1] Annual subscriptions may be easier to forget than monthly ones, especially if reminder emails are poorly configured or not sent. It is necessary to consider the interplay of legal name, trading name (doing business as) and product name if they differ, and especially which one the customer is most familiar with.

There are three kinds of disputed transactions: genuine third-party fraud, deliberate first-party fraud and customers who mistakenly dispute legitimate transactions because they do not recognise or understand them. Genuine third-party fraud is where someone obtains the customer’s card details without permission and makes purchases with them. Deliberate first-party fraud is harder to spot, as it involves the customer claiming refunds for goods and services they were satisfied with or claiming deliveries never arrived, deliberately misleading the supplier and financial institution.

This can include an attempt to obtain ‘free goods’ by disputing purchases after obtaining the items or return-policy abuse, where a customer disputes a charge after keeping goods beyond the return window. Customers who mistakenly dispute transactions may be confused by the description; for instance, the merchant might have a company name on the card statement different from the product or company the customer is used to dealing with, and so the customer thinks it is a fraudulent charge. A household member using the customer’s card without permission may instead be a genuinely unauthorised transaction.

Consider whether the customer fully agrees to the subscription. For a one-off purchase with a familiar name, the customer is likely to recall the purchase when they see the payment notification, having only recently made it. But will they remember your name when doing their budgeting? For monthly subscriptions, they may remember a month later, but annual subscriptions may be particularly vulnerable to being forgotten as renewal is a year after the customer made the initial purchase.

For a trial subscription Paddle provides reminders that the customer signed up for a subscription, the date the subscription started, how long the trial period is, the name of the subscription, the recurring price and when their payment will next be due, and a link to somewhere they can update their payment method or cancel their subscription. Paddle Billing sends a trial-end reminder at least seven days before the trial ends, except for trials of seven days or less.[2][3]

Paddle offers to handle this automatically for the SaaS company, while Stripe requires the SaaS company to configure its own notifications, which must respect card-network rules. Stripe Billing can send a reminder email seven days before a free trial ends, and Stripe’s Mastercard guidance says merchants with subscription billing periods longer than 180 days should configure an upcoming-renewal event between seven and 30 days before renewal.[4] The UK is introducing reforms to prevent “subscription traps” where people are surprised by charges for services after a free trial ends. The government now anticipates the new subscription-contract regime will commence in spring 2027.[5] Two key issues are users thinking they will cancel and then forgetting, and users not realising they are signing up for subscriptions. It is highly important for sellers to make it clear on their sign-up page that the customer will be charged after a trial. An automatically renewing trial should also include an easy way to cancel. It should go without saying that the notification should be early enough to allow the customer to cancel in advance.

Here is a fictional SaaS company providing energy data analytics:

The examples in the table are illustrative. For one-off card payments, Stripe can combine a shortened account prefix with a transaction-specific suffix. For subscriptions, Stripe says custom descriptors are instead set on the Invoice or Product. Paddle prefixes card statement descriptions with PADDLE.NET* and allows a custom seller descriptor of 2–10 characters; by default it uses the first 10 characters of the company name.[6][7]

For one-off card payments, Stripe’s ability to include a suffix can instantly clarify to the customer what they purchased. This is especially valuable where the product name and the company name differ or where the company sells multiple products in different lines. For subscriptions, Stripe achieves the same aim through Product or Invoice descriptor settings rather than a PaymentIntent suffix.[6] Paddle can also use a product-focused custom descriptor, but it still appears after the PADDLE.NET* prefix.[7]

I saw a charge on my bank statement for the Naked Candle Company and, after checking the website, saw it was all candles and not something I would buy, so I disputed it. However, it turned out they had sold me dog biscuits at the local town fair. Had my statement shown an illustrative Stripe configuration of NAKEDCAND* DOGBISCUIT, I would have immediately identified the charge and never disputed it.

When Paddle sends a subscription confirmation, it uses the company display name or legal name in the dashboard, not the statement descriptor. Paddle’s statement descriptor for card payments is separate and appears as PADDLE.NET* followed by the configured seller descriptor.[7] Both Stripe and Paddle have character limits, but what the customer ultimately sees can also vary because some banks replace the submitted descriptor with their own friendly merchant name.[8]

This could mean, in this example, the customer thinks they are buying from AmpereSync but the subscription confirmation says they are subscribed with Meridian Grid Technologies Ltd or Meridian Analytics. Paddle is gradually rolling out redesigned customer emails, so the exact layout can vary.[3]

However, an additional thing to bear in mind is that many banks do not use the literal string passed to them by Stripe or Paddle but show a friendly human-readable merchant name. This is primarily to prevent disputes and charge backs by using multiple data points from a given transaction to determine what friendly name to display. However, their mapping can make a mistake and display the wrong merchant name. As different card issuers use different mapping systems, the behavior across card issuers is not consistent.[8]

Can a customer identify the purchase from their receipt? This depends entirely on the clarity of the receipt. The receipt needs to contain enough data for the customer to say, “Ah yes, that is a product or service I purchased.” A receipt containing only the legal name may be mistaken by the customer for a fraudulent purchase. If they are buying from AmpereSync.com and expect to see AmpereSync on their receipt, they may well question a receipt stating a purchase from Meridian Grid Technologies unless there is something to quickly and clearly link it to AmpereSync.

Paddle’s email and invoice styling guidance says the legal company name is shown by default unless a Company Display Name is configured, in which case the display name is used instead.[9] Paddle Billing sends transaction receipts and subscription confirmations automatically, although Paddle is gradually redesigning the emails so the exact layout can vary.[3]

Stripe permits both manual and automated receipts after successful payments. Stripe creates receipts for successful payments and refunds, and subscription payments automatically generate invoices. Paid invoice receipts contain more detail than standard receipts. Stripe says the legal business name, customer support address, customer support email and privacy-policy URL are always required on receipts, while branding and public business details can be configured.[10]

Paddle controls more of the customer-facing documentation, whereas Stripe is much more flexible. For a founder using Stripe, they must check the right information is delivered to the customer instead of treating it as a set-and-forget setup. For AmpereSync, there are three names to be reconciled: the product name needs to be clear and easy to identify, the merchant name must be recognisable and the statement descriptor must correspond to the information received by the customer.

A customer could easily think that PADDLE.NET* MERIDIAN G is not something they purchased if they think of their subscription as AmpereSync, especially if customer-facing websites are using the product’s domain name and branding rather than the corporate identity.

A founder using Stripe should make sure that their business name is set and that they have a product with a clear and recognisable name. If using Paddle, they should seriously consider whether their legal name is the best representation or whether their doing-business-as name would be more instructive to the customer purchasing the product and, if so, configure this to be their display name.

Competition and Markets Authority guidance says automatic renewal clauses may be unfair if customers are not clearly informed of the renewal process, if the cancellation window is unduly long or unreasonable, or if the customer does not receive a timely reminder before renewal.[11] The DMCC Act’s subscription-contract rules are expected to commence in spring 2027.[5] Under the Act, monthly auto-renewing contracts will generally require a reminder around every six months, while contracts that auto-renew every 12 months or longer require two reminders a reasonable period ahead of renewal. Where there is a concessionary period, such as a free trial, a reminder is required before the first renewal payment.[12]

For customers in locations where it is required by law, Paddle will send auto-renewal reminder emails either seven or 30 days before renewal, and only for subscriptions of six months or longer. Paddle sends reminder emails at least seven days before a discounted period ends. Due to card-scheme rules, Paddle also sends trial-end reminders at least seven days before the trial ends unless the trial is seven days or less.[3]

Stripe allows you to configure reminder emails, including a reminder seven days before a free trial ends. For subscriptions with billing periods longer than 180 days, Stripe’s Mastercard guidance says merchants should configure an upcoming-renewal event between seven and 30 days before renewal.[4] Under the forthcoming UK subscription regime, where a contract includes a concessionary period, the seller must give a reminder notice before the first renewal payment and then at the relevant six-month points.[12]

For online SaaS sold to UK consumers, the current Consumer Contracts Regulations generally give consumers a 14-day cancellation period for distance service contracts, subject to exemptions. The £42 threshold applies to off-premises contracts, not ordinary online distance sales.[13] The new DMCC subscription regime is expected to start in spring 2027 and will add a second 14-day renewal cooling-off period after a trial or when a contract of 12 months or longer auto-renews.[5] If a service has already started, the government intends a proportionate refund based on the part of the subscription already supplied. For digital content, the current waiver of the initial cooling-off right will be retained, but the renewal cooling-off period will still apply.[5] The Act also requires an end-of-contract notice; unless regulations specify otherwise, online cancellations must be acknowledged within 24 hours and other cancellations within three working days.[14]

Paddle automatically includes a cancellation link in subscription-related emails, and sends a notification email when a subscription is canceled.[15] Stripe can include a Manage Subscription link in billing emails when Subscription Management is enabled, and its Mastercard guidance tells merchants to provide written confirmation when a recurring payment cycle is terminated.[4][16]

Before launching the SaaS, the most effective check a founder can make is to purchase their software as if they were a customer. They should check:

At checkout, is the subscription nature clear? Is it clear what they will pay and when they will pay? Does it avoid confusing the customer by, for example, showing only a monthly equivalent for an annual purchase, or making a subscription look like a one-off purchase? Is it clear when any free trial or discounted trial period ends?

When the founder makes a test transaction, they should look at their statement and see what descriptor appears. Does it show something recognisable or a legal name the customer has likely never heard of? Ideally, the descriptor should connect the company name to the product they just bought.

The founder should check the receipt. It needs to tell the customer: what was this charge for? Do the product name, merchant name and payment amount fit together sensibly? I

f the customer thinks they bought AmpereSync, a receipt showing only Meridian Grid Technologies will create unnecessary doubt and confusion.

The founder should check renewal notices and not assume that a customer will recall a subscription months later. They should make sure they know what renewal notices the platform will automatically send, what they need to configure and whether they give the customer enough time before renewal.

The founder should check cancellation and refund procedures. If the customer wishes to cancel, is canceling through the company easier than opening their banking app and disputing a charge? It is important to make sure that the cancellation process is obvious, that customers are aware of what happens after cancellation and how any refunds are processed.

[1] Visa Acceptance Solutions, 2026 Global eCommerce Payments & Fraud Report

[2] Paddle, Are my trial subscriptions compliant?

[3] Paddle, Which emails will customers receive on Paddle Billing?

[4] Stripe, Guidance for Mastercard recurring billing compliance updates

[5] UK Government, Government response to consultation on the implementation of the new subscription contracts regime

[6] Stripe, Statement descriptors

[7] Paddle, What will customers see on their statement?

[8] Stripe, Why do customers see statement descriptors that don't match what I've set in Stripe?

[9] Paddle, Editing the styling of invoices/emails?

[10] Stripe, Receipts and paid invoices

[11] UK Government, Writing a fair contract for customers

[12] Digital Markets, Competition and Consumers Act 2024, sections 258–260

[13] Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013

[14] Digital Markets, Competition and Consumers Act 2024, section 261

[15] Paddle Developer Docs, Cancel a subscription

[16] Stripe, Subscription-management links in billing emails