Five Words on a Bank Statement, One Chargeback Avoided: Auditing Your Payment Descriptor

There's a moment every UK customer has had. You open your banking app on a Tuesday morning, scroll past the Tesco run and the standing order to your broadband provider, and there it is: a debit you don't recognise. Twenty-two pounds. Something like SQ*NRTHBRD LTD. You stare at it. You think: was that the dog food? The software subscription? A scam?

Somewhere, a brand has spent five figures on a landing page designed to feel effortless. And this is the bit that actually lands.

The line that gets screenshotted into a support ticket

The payment descriptor is the text that sits in the "payment to" field of a customer's bank statement. It might also appear on a card receipt, a PayPal notification, a Stripe receipt, a GoCardless Direct Debit confirmation. Most payment providers let you set it — though how many characters survive the journey varies wildly between banks, card rails and processors. Sometimes it's twenty-two. Sometimes it's a lot fewer, and the rest is quietly guillotined.

Which means the person who reads it is not reading it carefully. They're reading it at 7.40am, half-awake, deciding whether to tap "I don't recognise this transaction". That tap is where trust quietly leaves the building — and where chargebacks, support tickets and a slightly irritated review begin.

What actually goes wrong (it's rarely fraud, nearly always copy)

Three failure modes turn up again and again.

The trading name gap. Your brand is Fern & Fold. Your registered entity is JJ Holdings (UK) Ltd. Your descriptor says JJHOLD*FERN. Your customer has never heard of JJ Holdings. Fair enough.

The truncation accident. A descriptor that only works in full. THE GOOD SLEEP COMPANY becomes THE GOOD SLEEP becomes THE GOOD SLE. Now it reads like a mildly threatening wellness cult.

The multiple-charge muddle. A deposit on Tuesday under one name, the balance on Thursday under another, the subscription on the 1st under a third. Three debits, three names, one confused customer and a very long phone call.

The audit: five passes, ninety minutes

1. The cold read

Screenshot your own descriptor exactly as it appears in a Monzo, Starling, Lloyds and Barclays feed — or ask five customers to do it for you. Don't explain it first. If you have to explain it, it's failing.

2. The character cull

Chop your descriptor to its first ten characters. Does it still point at you? If not, front-load the brand and drop the order number. FERNANDFOLD ORDER beats ORDER 88231 FERN every single time.

3. The chain check

Line up the name on the checkout page, the confirmation email, the receipt, the invoice, the bank statement and the refund. Same name every time? If the invoice says your Ltd company and the statement says your brand, that's fine — as long as one of them explicitly bridges the gap.

4. The timing test

Pending transactions often show a different label to settled ones, and card authorisations can look like a charge before they are one. Know what your customer sees at each stage, and say so in the confirmation email.

5. The search-and-rescue review

Search your help desk for "who is", "unrecognised", "didn't order", "fraud" and "charged twice". Every hit is a copy problem wearing a support ticket as a disguise.

The sentence that prevents half of this

One line at checkout, repeated in the confirmation email, does more work than most brands' entire trust-building strategy:

Your statement will show FERNANDFOLD, not Fern & Fold. Any questions, reply to this email.

That's it. It costs nothing, it heads off the panic, and it makes the brand look like it has actually thought about the customer's morning.

Receipts, invoices and the billing name

While you're in there, check the receipt wording too. "Payment received" is fine. "Thank you for your payment" is warmer. But neither tells the customer what happens next, which is the thing they actually want to know at that exact moment.

Two useful additions: a plain-English line about what's being billed ("This covers your November box, delivered 18–20 Nov") and a named human or team to contact if the line looks wrong. Not a form. A reply-to address that someone reads.

Keep the tone clear, not cute

Transactional copy is not the place for the brand's playful voice. A descriptor reading YOUR FAVE SNACKS in someone's banking app is not charming — it's ambiguous. Clarity first, warmth second. "Paid — thanks, your order's on its way" is warm. "Nom nom, we've got your dosh" is a chargeback waiting to happen.

Your quick checklist

• Descriptor front-loads the brand in the first ten characters
• Checkout, confirmation, receipt, invoice and statement all agree
• One plain-English line explains the name before the customer sees it
• Refunds and partial refunds carry the same name as the original charge
• Support searches for "unrecognised" come back empty

The sales page gets the budget. The bank statement gets the verdict. Audit the line nobody briefed, and you'll spend less of next quarter explaining who you are to your own customers.