Set a dynamic statement descriptor per transaction on Adyen to reduce friendly fraud

Steps

1. In the Adyen payment request payload, set the 'shopperStatement' field to a customer-recognizable description of the specific purchase (e.g., 'ACME-ORD-12345 Book').
2. Keep the descriptor within the character limit enforced by card networks (typically 22 characters for the combined merchant name + descriptor suffix); truncation can make it unrecognizable.
3. Pre-populate the descriptor with the most identifying information first (order number or product name) since some issuers further truncate from the right.
4. Ensure your registered DBA (doing-business-as) name is consistent with what the cardholder will recognize from emails or receipts — mismatches are a leading cause of 'I don't recognize this charge' disputes.
5. Test descriptor rendering across multiple issuers in the Adyen test environment, as each issuer may display different subsets of the descriptor string.
6. For marketplace flows, use the descriptor to reflect the sub-merchant name rather than the platform name so cardholders recognize who they transacted with.