Reducing Chargebacks with Dynamic Descriptors

Friendly fraud — chargebacks filed by customers who don't recognise a legitimate charge — accounts for over 40% of all chargebacks. Dynamic descriptors are one of the most effective tools to fight them, and they're criminally underused.

What is a payment descriptor?

A payment descriptor is the text that appears on a customer's bank or card statement against a transaction. Most merchants use a static descriptor — typically their legal entity name — that rarely matches what the customer thinks they bought.

A customer buys from "TechStore UK", sees "ACME PAYMENTS LTD" on their statement, doesn't recognise it, and files a chargeback. This happens tens of millions of times a year.

Dynamic descriptors let you customise per transaction

Dynamic descriptors allow you to include transaction-specific information in the statement text. Depending on the scheme and acquirer, you can include:

• The product or service name
• The merchant's trading name (as distinct from legal name)
• A customer-facing reference number
• A support phone number or URL

The impact on chargebacks

Merchants who implement well-crafted dynamic descriptors typically see:

• 25–40% reduction in "unrecognised transaction" chargebacks
• Higher customer satisfaction scores (fewer confused calls to support)
• Improved Visa/Mastercard chargeback ratios, reducing risk of programme penalties

Implementing with Orchestrate

Setting dynamic descriptors through Orchestrate is straightforward. Pass a statement_descriptor field on your payment intent:

{
  "amount": 4999,
  "currency": "USD",
  "statement_descriptor": "TechStore - Order #9821",
  "statement_descriptor_suffix": "techstore.io/help"
}

Orchestrate normalises this across all connected acquirers, handling the character limit differences between Visa (25 chars) and Mastercard (22 chars) automatically.

Best practices

• Always include your trading name, not your legal entity name
• Add an order reference or short product name
• Include a support contact if you have space
• Test across multiple card schemes — descriptors render differently on different statements