Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Developer tools
Get started
Payments
Finance automation
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Overview
Versioning
Changelog
    Overview
    Basil
    Acacia
    Previous versions
Upgrade your API version
Upgrade your SDK version
Developer tools
SDKs
API
Testing
Workbench
Event Destinations
Workflows
Stripe CLI
Stripe Shell
Developers Dashboard
Agent toolkit
Stripe health alertsBuild with LLMsStripe for Visual Studio CodeFile uploads
Security
Security
Extend Stripe
Stripe Apps
Stripe Connectors
Partners
Partner ecosystem
Partner certification
HomeDeveloper toolsChangelogAcacia2024-09-30.acacia

Updates consent modeling for saving cards with TerminalBreaking changes

What’s new

Removes the customer_consent_collected parameter and replaces it with allow_redisplay.

Requires allow_redisplay when using setup_future_usage.

Removed
customer_consent_collectedboolean

Indicates whether customer consent has been collected to redisplay the payment method.

Added
allow_redisplayenum

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_redisplay when saving card details with Terminal. For SetupIntents, customer_consent_collected has been removed and replaced with allow_redisplay. For PaymentIntents that specify setup_future_usage, then allow_redisplay must also be passed before collecting card details. With the new version, you must use allow_redisplay 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_future_usage.

Changes

ParametersChangeResources or endpoints
allow_redisplayAdded
Terminal.Reader#process_payment_intent.process_configTerminal.Reader#process_setup_intent
customer_consent_collectedRemoved
Terminal.Reader#process_setup_intent

Upgrade

  1. View your current API version in Workbench.
  2. If you use an SDK, upgrade to the corresponding SDK version for this API version.
    • If you don’t use an SDK, update your API requests to include Stripe-Version: 2024-09-30.acacia
  3. Upgrade the API version used for webhook endpoints.
  4. Test your integration against the new version.
  5. If you use Connect, test your Connect integration.
  6. In Workbench, perform the upgrade. You can roll back the version for 72 hours.

Learn more about Stripe API upgrades.

Related changes

  • Adds support for configuring the reboot time setting
  • Adds the Stripe S700 reader as a valid device type
  • Adds details about offline collection on card_present PaymentMethod objects
Was this page helpful?
YesNo
Need help? Contact Support.
Join our early access program.
Check out our changelog.
Questions? Contact Sales.
LLM? Read llms.txt.
Powered by Markdoc