Updates consent modeling for saving cards with TerminalBreaking changes
What’s new
Removes the customer_ parameter and replaces it with allow_redisplay.
Requires allow_ when using setup_.
Indicates whether customer consent has been collected to redisplay the payment method.
This field indicates whether this payment method can be shown again to its customer in a checkout flow. Stripe products such as Checkout and Elements use this field to determine whether a payment method can be shown as a saved payment method in a checkout flow. The field defaults to unspecified.
Why is this a breaking change?
This is a breaking change because it requires allow_ when saving card details with Terminal. For SetupIntents, customer_ has been removed and replaced with allow_. For PaymentIntents that specify setup_, then allow_ must also be passed before collecting card details. With the new version, you must use allow_ to control whether a payment can be shown to a customer again.
Impact
Lets you save cards in more regions using Terminal, expanding your service coverage. Additionally, the improved alignment with industry requirements for customer consent collection ensures regulatory compliance.
You must add the new parameter to your integration before March 31, 2025 and ensure that it’s set to always or limited on all Setup Intents transactions and Payment Intents that specify setup_.