What is Soft descriptor?
The merchant name and contact info shown on the cardholder's statement.
A Soft descriptor is the custom text that appears on a cardholder's bank statement for a specific transaction, which can be dynamically set on a per-transaction basis.
It differs from a 'hard descriptor', which is the static, legal business name registered with the acquirer and tied to the Merchant ID (MID).
The Soft descriptor allows a merchant to provide more context about a purchase, such as the product name or website, helping the cardholder recognise the charge and reducing the likelihood of a 'Friendly fraud' chargeback.
This data is passed from the merchant's payment gateway to the acquirer within the authorisation request, typically in Data Element 43 of the ISO 8583 message.
A common format combines a recognisable trading name with a product identifier, separated by an asterisk, for example, `CARDFLO*ANALYTICS`. The total length is constrained by card scheme rules, generally around 22-25 characters.
The acquirer then passes this information through the schemes to the issuer, which ultimately displays it on the cardholder's statement. A frequently misunderstood nuance is that not all acquirers support dynamic soft descriptors effectively.
Some may truncate them, ignore them entirely, or override them with the hard descriptor, undermining a merchant's efforts to prevent disputes. This makes testing descriptors across a multi-acquirer setup essential.
Worked example
A UK-based SaaS company, 'Analytics Widgets Ltd', sells two products: 'DataMiner' and 'ReportGen', each at £50/month. If they rely on their hard descriptor, the customer's statement will show a generic 'Analytics Widgets'.
A customer who bought 'ReportGen' might not recognise this and file a chargeback. Using dynamic soft descriptors, a 'ReportGen' purchase appears as 'DataMiner*ReportGen', while a 'DataMiner' purchase shows as 'DataMiner*MainTool'.
When the cardholder reviews their statement, the specific product name immediately clarifies the £50 charge, preventing a call to their bank. This avoids a potential chargeback, saving the £50 transaction value and a £15 chargeback fee.
The descriptor is passed in the API call at the point of authorisation.
Scheme notes
Scheme rules govern Soft descriptor format and length. Mastercard limits the field to 22 characters, while Visa allows up to 25.
Both schemes recommend a prefix identifying the merchant's brand name, followed by an asterisk and then a product-specific identifier. American Express provides a bit more flexibility but strongly encourages including a customer service phone number within the descriptor fields to facilitate direct contact over disputes.
The schemes do not mandate the use of dynamic descriptors, but their dispute resolution frameworks, like Visa's VCR, implicitly favour merchants who use clear descriptors as a best practice for dispute prevention.
Why it matters for merchants
An effective Soft descriptor strategy is one of the most cost-effective tools for reducing chargeback ratios. By preventing disputes arising from customer confusion, merchants save on chargeback fees, avoid revenue loss, and lower the operational burden of representment.
For businesses with multiple product lines, websites, or subscription services running on a single MID, dynamic descriptors are critical for clarity.
Using a payment orchestration provider like Cardflo allows merchants to normalise descriptor formats and ensure they are passed correctly to different acquirers in their network, avoiding common issues like truncation or acquirer overrides that can negate the descriptor's benefit.
Frequently asked
What is the character limit for a typical Soft descriptor?
Most card schemes and acquirers limit the descriptor to between 20 and 25 characters. Exceeding this limit usually results in the string being truncated, which may remove vital contact information and potentially increase chargeback rates due to lack of clarity.
Can dynamic descriptors be used for every payment type?
While most modern gateways allow dynamic soft descriptors for standard e-commerce transactions, some legacy hardware or specific high-risk processing agreements may restrict this.
It is advisable to verify with your acquirer if your MID supports per-transaction overrides, especially when managing multiple sub-brands under a single merchant account.
What are the exact character limits for soft descriptors?
The limits are set by the schemes and acquirers, but standard rules are 22 characters for Mastercard and 25 for Visa. It is important to note that the city field, which is sometimes appended, also has limits, often around 13 characters.
You should always confirm the exact supported length with your acquiring bank, as some may impose stricter limits than the schemes themselves.
My dynamic Soft descriptor isn't showing up correctly. What's the problem?
This is a common issue. The problem usually lies with the acquiring bank.
Some acquirers either do not support dynamic descriptors or have a system that incorrectly overrides the dynamic field with the static hard descriptor linked to your MID.
To resolve this, you must contact your acquirer's technical support to ensure your account is configured correctly to pass the data from ISO 8583 field DE43 through to the schemes.
What is the best format to use for a subscription service?
For subscriptions, clarity and consistency are key. A good format is `BRAND*PRODUCTNAME`.
For example, a monthly coffee subscription could be `QUICKCOFFEE*SUB`. Avoid changing the descriptor for recurring payments unless necessary, as this can cause confusion.
Appending a customer service number is also a strong best practice if character limits allow, but this is often sent in a separate field.
Is there a difference between a Soft descriptor and a statement descriptor?
The terms are often used interchangeably. However, 'statement descriptor' is a broader term that can refer to either the Soft descriptor (dynamic) or the hard descriptor (static).
A Soft descriptor is specifically the custom, transaction-level identifier, whereas a hard descriptor is the default business name applied to all transactions on a MID if a Soft descriptor is not provided or supported.
Can I include a transaction or order ID in the Soft descriptor?
While technically possible if it fits within the character limit, it is generally not a recommended practice. Cardholders will not recognise an internal order ID like `BRAND*A84XYZ-1`, which defeats the purpose of the descriptor.
The goal is human readability. It is better to use a recognisable product or service name.
The unique transaction ID is already passed in other data fields and available to the issuer.
See how Soft descriptor plays out in practice
Industries and regions where this term drives real acquiring, routing, or dispute decisions.
Related terms
A forced reversal of a card payment initiated by the cardholder's issuing bank.
A chargeback filed by a real cardholder for a transaction they actually made, often because they don't recognise the descriptor or want a refund without contacting the merchant.
A unique identifier issued by an acquirer that ties transactions to a specific merchant account.
Scheme-defined code identifying the grounds for a chargeback (e.g. Visa 10.4 for cardholder-not-authorised, 13.1 for goods not received) that dictates the evidence required to defend it.
Related guides.
Ready to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.