New Crypto Payment Method Configuration Option

Stripe has added fine-grained control over how crypto payment methods are handled in Checkout Sessions. You can now set the setup_future_usage parameter within the payment_method_options.crypto hash to override the session-level future usage setting.

What's Changed

The new setup_future_usage parameter for crypto payments allows you to specify per-payment-method behavior, particularly useful when you want to indicate that a crypto payment method should not be reused (by setting it to none) while maintaining different settings for other payment methods in the same session.

Developer Action Items

To use this feature, update to API version 2026-03-25.dahlia:

• SDK Users: Upgrade to the latest version of your SDK (Ruby, Python, PHP, Java, Node.js, Go, or .NET)
• Direct API Users: Add Stripe-Version: 2026-03-25.dahlia header to requests
• Webhook Integration: Update webhook endpoint API versions to match
• Testing: Test your integration against the new version before deploying to production

The upgrade process supports rollback for 72 hours if needed.

Use Cases

This enhancement is particularly useful for merchants who accept multiple payment methods but want different reuse policies for crypto versus traditional card payments, providing more granular control over payment method lifecycle management.