How does a soft descriptor work?
The merchant or its provider sends a descriptor with the transaction, and the issuer prints it on the statement. Stripe’s documentation describes two forms: a static descriptor that appears on every payment, and for card payments a static prefix combined with a dynamic suffix, so each payment can name the product or order. Its rules require only Latin characters, 5 to 22 characters in total, at least one letter, and a descriptor that reflects the business’s trading name.
Why does a soft descriptor matter?
Customers dispute what they do not recognise. Stripe notes that clear and accurate statement descriptors can reduce chargebacks and disputes, and that card network inquiries often start because the cardholder does not recognise the transaction description. As an illustrative example: a merchant with 300 disputes a month finds that 90 are coded as unrecognised transactions. Changing an opaque descriptor such as a legal entity abbreviation to the brand name customers know, and adding the order reference as a suffix, cuts those to 40, which lowers the chargeback ratio without touching approvals.
What are the limits of a soft descriptor?
Issuers decide how to display it, and some truncate or ignore the dynamic part. Wallets and local methods may show something else entirely, such as the provider’s name. Multi-brand merchants need a descriptor per brand or per merchant account, otherwise one brand’s customers see another brand’s name.
Where does Omno use it?
Descriptors are set by the PSP or acquirer that processes each payment, usually per merchant account. Omno’s routing-decision log shows which provider processed each payment, which support teams use to answer customers who ask why their card was charged under an unfamiliar descriptor.