Identify the display name shown in the Apple Pay payment sheet and the Google Pay payment sheet; these are controlled by the merchant name configured in your Apple Pay certificate domain and Google Pay merchant profile respectively
Ensure the payment sheet display name, the statement descriptor, and the push provisioning name (if applicable) are consistent to avoid cardholder confusion
On the Stripe payment request, set the statement descriptor suffix to reflect the specific product or service being purchased, keeping the combined descriptor within character limits
For Apple Pay, update the PKPaymentRequest display items to clearly itemize charges before the cardholder authorizes
For Google Pay, configure the displayItems in the PaymentDataRequest to show line items matching what will appear on the statement
Test the end-to-end descriptor flow using real wallet transactions in test mode to confirm the displayed name matches your intended branding before going live
Known gotchas
The display name in the Apple Pay or Google Pay payment sheet is set by the wallet configuration and cannot be changed per-transaction at runtime; it requires updating your merchant registration with Apple or Google
Descriptor mismatches between the wallet payment sheet and the bank statement are a leading cause of friendly-fraud disputes for wallet transactions; audit all name surfaces before launch
Some issuers render the statement descriptor differently for wallet transactions than for card-present or card-not-present transactions; test across multiple issuing banks to verify appearance
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?