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').
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.
Pre-populate the descriptor with the most identifying information first (order number or product name) since some issuers further truncate from the right.
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.
Test descriptor rendering across multiple issuers in the Adyen test environment, as each issuer may display different subsets of the descriptor string.
For marketplace flows, use the descriptor to reflect the sub-merchant name rather than the platform name so cardholders recognize who they transacted with.
Known gotchas
Dynamic descriptors are not guaranteed to reach the cardholder unchanged — issuer display logic, mobile banking app truncation, and card network processing can all alter the final displayed string.
Some card types (particularly certain debit and prepaid products) ignore the dynamic descriptor and display only the static merchant name registered with the acquirer.
Changing the descriptor format frequently can increase disputes from returning customers who don't recognize the new format — A/B test changes carefully before rolling out globally.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp