Hi,
We have the Payments API ( POST /v2/payments - Square API Reference ) working in one of our web apps, and the Checkout API ( POST /v2/online-checkout/payment-links - Square API Reference ) in another. I noticed that while the Payments API supports specifying a statement descriptor, this option does not appear to be available in the Checkout API.
Please clarify the following:
1.) Are custom statement descriptors supported in any way when using the Checkout API?
2.) If not supported, which integration types (Payments API, Payment Intents, Web Payments SDK/Elements, etc.) allow the use of custom statement descriptors?
3.) Is there any way to pass or override the statement descriptor when using the Checkout API flow?
4.) If the Checkout API does not support it, what is the recommended solution that allows custom statement descriptors while continuing to support Google Pay and Apple Pay transactions?
Thank you.
I’m Square Dev AI, here to help answer your question!
Based on the information you’ve provided, the following documentation will help answer your question:
Additional Documentation
Statement Descriptions
Take Payments
eCommerce API Guide: Build Custom Integrations | Square
If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.
Otherwise one of our Developer Advocates will provide additional assistance shortly.
1.) Custom statement descriptors are not supported when using the Checkout API. The Checkout API does not provide an option to specify a statement descriptor.
2.) The Payments API supports specifying a custom statement descriptor through the statement_description_identifier in a CreatePayment request. This allows you to customize how the transaction appears on a customer’s bank statement.
3.) There is no way to pass or override the statement descriptor when using the Checkout API flow. The Checkout API does not have a feature to customize statement descriptors.
4.) If you need to use custom statement descriptors while supporting Google Pay and Apple Pay transactions, the recommended solution is to use the Payments API in conjunction with the Web Payments SDK. The Web Payments SDK allows you to build a customizable checkout flow that supports various payment methods, including Google Pay and Apple Pay, and you can use the Payments API to specify custom statement descriptors.
This answer was reviewed by @Bryan-Square.