releases.shpreview
Home/Stripe
Stripe

Stripe

Agentic Commerce Next: Seattle

June 23, 2026 | 1:00pm - 5:00pm

The Collective | Alpenglow

Prepare for the future of commerce with Stripe

Join Stripe in Seattle on June 23 for a half-day session (1:00 pm-5:00 pm) on how AI is changing commerce and what your team can do now to prepare.

AI-powered discovery is already reshaping how customers find and evaluate products. Agentic purchasing is emerging next. This event is designed to help ecommerce, product, customer experience, and billing leaders understand what matters now across discoverability, catalog readiness, checkout, trust, and fraud.

The afternoon will include a keynote from Microsoft, a panel with leaders from across the ecosystem, guided discussions and hands-on experiences with our partners Klarna, Logicbroker and Orium designed to move attendees from awareness to action.

Attendees will leave with:

  • A clearer understanding of what agentic commerce means for their business
  • A practical framework for assessing readiness and prioritizing next steps
  • Real-world perspectives from Stripe, customers, and ecosystem partners
  • Ideas they can apply now across discovery, content, checkout, and risk
Speakers and Panelists

1:20 PM - Keynote

Billy Conway VP of AI Commerce Products - Microsoft

At Sessions 2019, we shared our predictions for the future of payments.

4:10 PM - Hands on Demos

We talk to Sothebys, Wayfair, Visa, and Klarna to learn how both incumbent and digital-native enterprises are approaching payments in novel ways.

John Coy Technical Lead, Agentic - WooCommerce

Jake Sinsheimer Head of Agentic Commerce - Stripe

About the Venue

The Collective | Alpenglow

400 Dexter Avenue North Seattle, WA

Alpenglow is a members-only-style gathering place for people who value connection, creativity, and a beautifully considered experience — part social hub, part event space, entirely its own thing. Think local art, inviting lounge areas, and distinctive touches like the Campfire Circle, hanging egg chairs, Hammock Garden, and bouldering wall. It's the kind of space that feels both elevated and approachable, where every corner has something memorable to discover.

Tucked into a setting designed for engagement and ease, Alpenglow is known for hosting everything from elevated meetings and events to lively socials and culinary experiences. The design speaks for itself — warm, interactive, and genuinely distinctive.

Learn more.

Program Overview

1:15 PM - Welcome and opening remarks

A brief welcome to frame the day, outline the agenda, and highlight why agentic commerce matters now for teams across ecommerce, product, and customer experience.

1:20 PM - Featured keynote from Microsoft

An overview of how AI is beginning to reshape discovery, checkout, trust, and operations—and where businesses should focus first.

1:55 PM - Panel - Agentic in action: Learnings from the leaders

A practical discussion with leaders from across the ecosystem on what they're learning as they prepare for agent-led commerce.

2:45 PM - Guided discussions

Small-group conversations on the questions that matter most now: discoverability, catalog readiness, checkout, trust, and fraud.

4:00 PM - Closing remarks and next steps

A short wrap-up on the day's key takeaways and the practical next steps teams can take from here.

4:10 PM - Hands-on experiences and networking

Along with Klarna, Logicbroker and Orium, we'll explore demos, connect with experts, and continue the conversation with peers working through the same challenges.

Helpful resources

Survey report: How modern consumers decide and buy

A new survey of 1,810 shoppers across Australia, France, Germany, Japan, the United Kingdom, and the United States shows a shift in how people choose and purchase. They have new reasons for going in store rather than online, new preferences when it comes to AI involvement, and new expectations for payment methods at checkout. Many retailers are trying to meet these expectations by layering point solutions as needs arise, but this approach can lead to duplicated data, fragmented journeys, and inconsistent checkout experiences. Learn four findings retailers can use now to capitalize on these changing shopper behaviors.

View

Guide: How to sell on AI platforms

With the launch of in-chat purchasing through interfaces like Instant Checkout in ChatGPT, high-intent shoppers can now buy products directly where they're discovering them. While this provides an opportunity for sellers to monetize a new channel, agentic commerce also challenges one of the basic tenets of ecommerce—that bot traffic is bad—in ways that require sellers to rethink how they handle nearly every aspect of their checkouts. Read this guide to understand some of the most common questions we get about agentic commerce and what we're building to help them succeed.

View

Guide: The business impact of modern payments

Transaction fees are only one factor to consider when evaluating payment solutions. A provider with low up-front costs can quickly become a high-cost liability when factoring in fraud losses, unexpected outages, and customer churn. The right payments infrastructure should protect against these costs while creating new revenue streams and reducing operational complexity. Explore how modern payment features can expand market reach, accelerate cash flow, and eliminate inefficiencies that drain your resources.

View

Waitlist: Join the waitlist for agentic commerce

Businesses interested in selling through AI agents—including OpenAI's Instant Checkout in ChatGPT—can join the waitlist. Stripe is accepting applications from businesses selling through agents, platforms enabling merchants, and AI companies embedding commerce. The program helps companies test new distribution channels and prepare for a future where agent-driven purchasing is mainstream.

View

Checkout Studio surfaces local payment methods; Treasury expands to 120+ countries

This release6 featuresNew capabilitiesAI-tallied from the release notes

It's never been easier to reach global customers. Thirty-six percent of Stripe businesses now have customers in more than one country, and the number selling into more than 100 countries has quadrupled in five years. Turning that reach into revenue, however, requires solving a familiar set of cross-border challenges. At Sessions, we announced dozens of new products and capabilities to localize the customer experience, maximize payment performance, move money across borders, and manage tax and regulatory compliance.

Convert customers with a localized experience

Cross-border success often depends on the customer experience at checkout. A localized experience includes core components like customers' preferred languages, currencies, and payment methods; it also requires continuous optimization.

Checkout studio, the newest addition to the Optimized Checkout Suite, provides tools for businesses to tailor their checkouts to local customers. Industry-specific recommendations and location data help surface local payment methods for each market, with built-in tracking for adoption and performance. Stripe provides access to more than 125 payment methods, including support for Sunbit, Bizum, Pay by Bank, BLIK, and TWINT. A fashion retailer expanding into Spain or Poland, for instance, might be prompted in Checkout studio to add Bizum or BLIK and A/B test against live traffic before deploying it live.

Checkout studio provides recommendations to help present the right payment methods. Stripe data shows that even one geographically irrelevant payment method can decrease conversion by up to 15%. The upside of getting it right is significant: on Stripe, businesses offering Pix see up to 38.3% higher conversion from customers in Brazil, and those offering UPI see 19.8% higher conversion from customers in India.

Localization also extends beyond language and payment methods to include pricing in local currencies. Stripe data shows that 76% of customers will choose to pay in their local currency when given the option. Adaptive Pricing uses AI to display prices in local currencies, while Stripe handles conversion and the operational work behind it. On average, businesses using Adaptive Pricing see a 5% increase in authorization rates and a 17.8% lift in cross-border revenue.

Adaptive Pricing also supports subscription sign-ups and renewals, with guardrails built in to help keep renewal amounts consistent across billing cycles. On average, Adaptive Pricing for subscription businesses drives a 4.7% conversion uplift and a 5.4% increase in lifetime value (LTV) per session.

Increase payment acceptance and reduce fraud in every market

Maximizing payment performance also requires accounting for local nuances. Authorization rates vary across markets due to differences in issuers, local network preferences, and regional card behavior. Stripe helps businesses optimize global payments performance with AI-powered authentication, authorization, and fraud tools.

Stripe Authorization Boost adapts to market differences automatically with optimizations like real-time retries and issuer-specific messaging per transaction, and it includes support for Data Only authentication flows to reduce payment friction. Together, these capabilities can drive higher acceptance rates and lower processing costs without manual intervention. Businesses see an average 3.8% lift in authorization, and some Stripe customers with custom interchange pricing see processing costs decrease by up to 3.3%. Built-in A/B testing helps businesses measure impact before fully rolling out changes more broadly.

Adding new markets and payment methods also introduces new fraud vectors. Stripe Radar helps reduce fraud by automatically blocking high-risk transactions across all supported payment methods, including local bank debits; wallets; buy now, pay later options; and stablecoin payments. In a private preview, Stripe data showed that Radar reduced fraud by an average of 71% across four payment methods: Klarna, PayPal, Affirm, and Cash App Pay.

Reduce cross-border costs

Expanding into more countries can increase revenue, but each new market adds complexity when storing and moving money. Traditional money movement is often fragmented across currencies, accounts, and providers—forcing companies to spend precious time managing operations instead of growing the business.

Stripe Treasury brings payments and finances together in one place with the ability to store, convert, and send money across multiple currencies and stablecoins without leaving Stripe. For businesses in the US and UK, settled payment earnings are available instantly, regardless of bank holidays or weekend closures.

Holding funds in multiple currencies has traditionally required multiple bank accounts, local entities, and unnecessary FX fees. With Stripe, businesses can hold multiple currencies side by side in a Treasury account without having to convert them. When currency conversion is needed, businesses can do so instantly, 24/7, and lock in transparent, market-leading rates. Organizations can also pay out globally to more than 160 countries in fiat and stablecoins, and create cards that let employees spend directly from Treasury balances.

Additional support for stablecoins gives businesses even more ways to manage and move money globally. A global marketplace, for example, can accept stablecoin payments in 32 new markets and enable its sellers to hold stablecoins in Treasury. Sellers in 30 countries can also receive a stablecoin-backed card and offramp funds to local currencies like ARS, COP, EUR, MXN, PHP, and USD.

Today, Treasury is live in more than 120 countries—with stablecoin-backed balances in 100 of them—and we plan to add stablecoin support for an additional 41 countries by the end of 2026. Entrepreneurs in more than 50 countries already use Treasury as their primary business account.

Manage tax and regulatory compliance

Every market comes with its own tax and regulatory rule book, which can slow global expansion. A business might solve for the roughly 16,000 combinations of US sales tax rates and rules, but expanding into India requires navigating different GST structures, real-time e-invoicing, and dispute windows measured in hours instead of days.

Whether businesses choose to manage compliance themselves with Stripe Tax, or rely on Stripe to handle it through Stripe Managed Payments, both approaches help reduce overhead and make global growth easier.

For businesses that want to remain the merchant of record, Stripe Tax automates tax calculations, collection, threshold monitoring, registrations, and filing. Stripe Tax automatically calculates and collects the right tax in more than 100 countries across more than 600 product categories to simplify tax compliance as a business grows. OpenAI, ElevenLabs, and Retell AI are among more than 67,000 companies using Tax to handle compliance rather than building out a full tax team.

For businesses that want to outsource their tax responsibility, Managed Payments is Stripe's merchant of record solution. It handles tax registration, collection, and remittance in more than 80 countries, letting businesses focus on their core product, growth, and expansion.

Tax is only part of the challenge of growing globally. Building internal processes for fraud, disputes, and customer support can slow expansion and increase the cost of entering new markets. With Managed Payments, businesses also get fraud protection, dispute management, customer support, and a localized checkout experience. Managed Payments is now available to businesses selling digital goods, and it has already helped companies like Unity, RevenueCat, and Lovable expand.

Grow globally, faster

Whether you're entering your first international market or optimizing for the next 10, Stripe offers solutions to help businesses sell, operate, and grow.

See everything announced at Sessions 2026, and check out our product roadmap to see the upcoming features Stripe is planning to help global businesses. To network with industry leaders and explore new paths to growth, sign up for a Stripe Tour event near you.

DCAP integration captures $18.4M in annualized savings

This release1 featureNew capabilitiesAI-tallied from the release notes

June 3, 2026

Kanika Nayyar Global Payments Performance

Visa recently launched the Digital Commerce Authentication Program (DCAP), a new global framework designed to reduce fraud and increase authorization rates for card-not-present transactions. The program rewards businesses in the US for sharing richer transaction data with issuers during authentication, such as device ID, billing address, IP address, and customer email. Qualifying transactions receive a net interchange reduction of five basis points.

New network programs create opportunity, but they also introduce complexity. Businesses need to understand which transactions qualify, ensure their integration passes the required data, and determine whether participating will improve their end-to-end transaction economics or have unintended consequences, such as hurting authorization rates.

To participate in DCAP, businesses need to share required cardholder data with issuers via frictionless authentication in their checkout. This might introduce latency and uncertainty around how issuers interpret these newer signals.

We moved quickly to help Stripe businesses take advantage of DCAP and capture interchange savings while protecting authorization rates. Here's what we did.

Optimizing DCAP savings without sacrificing conversion

Before rolling out DCAP, we worked with Visa to run readiness testing and identify the right implementation approach. This collaborative testing underscored the need for transaction-level intelligence.

With Stripe Authorization Boost, we intelligently select which transactions should go through Data Only 3DS, which sends additional risk data from the card network to the issuer for authorization. Rather than applying static rules, Authorization Boost evaluates cost savings, conversion impact, and fraud risk at the individual transaction level to determine when to apply Data Only 3DS. This allows businesses to capture DCAP savings while limiting the impact to the customer experience and optimizing authorization rates.

Since April 18, we've helped Stripe businesses capture $18.4 million in annualized network cost savings from DCAP. By helping businesses collect and pass the required data, we saw an 8x increase in the number of DCAP-eligible transactions. We're continuing to work with Visa to optimize eligibility, so more transactions can benefit from DCAP.

Automatically benefit from DCAP optimizations

If you use Authorization Boost and are collecting the required data points, you're already automatically benefiting from DCAP optimizations. For businesses using standalone 3DS, you can participate by setting flow_preference[type] to data_share on authentication requests and ensuring required fields are populated.

Learn more about how Authorization Boost can help optimize your payments performance.

Tools plugin hint; climate commitment subcommand added

This release3 featuresNew capabilities1 enhancementImprovements to existing features1 fixBug fixesAI-tallied from the release notes
Stripe CLI · v1.42.1

Changelog

  • 6fecb501f3af0ff8edd296608cf886c3159db5b9 Add 'tools' plugin hint command (#1615)
  • acd7dfcb4bde2515a2b53918b6d8caa27fc58f30 Add canary tests for v2 API endpoints and triggers (#1611)
  • 2295a552d089a364e5508017081b66b7c9350030 Add stripe climate commitment subcommand (#1599)
  • a157144d9001e57376432f71689f8de569dd6bb0 OpenAPI Update for 2026-05-27.dahlia (#1610)
  • 9e0aa035244da37993be50893a459d7d7a051a41 Route unauthenticated plugin metadata requests to dashboard API (#1614)
  • f440fad19c3681185df2212599164df035125dcf fix: show apps hint command in stripe --help (#1601)

Bizum and Scalapay payment methods added; TWINT enum expanded

This release7 featuresNew capabilities1 enhancementImprovements to existing featuresAI-tallied from the release notes
stripe-python · v15.2.0

This release changes the pinned API version to 2026-05-27.dahlia.

  • #1816 Update generated code
    • Add support for new resource v2.commerce.ProductCatalogImport
    • Add support for create and retrieve methods on resource v2.commerce.ProductCatalogImport
    • Add support for bizum_payments and scalapay_payments on Account.Capability, AccountCreateParamsCapability, and AccountModifyParamsCapability
    • Add support for automatic_transfer_rules_by_currency on BalanceSettings.Payment.Payout and BalanceSettingsModifyParamsPaymentPayout
    • Add support for start_of_day on BalanceSettings.Payment.SettlementTiming and BalanceSettingsModifyParamsPaymentSettlementTiming
    • Add support for description on ChargeCreateParamsTransferDatum, PaymentIntent.TransferDatum, PaymentIntentCreateParamsTransferDatum, and PaymentIntentModifyParamsTransferDatum
    • Add support for bizum on Charge.PaymentMethodDetail, ConfirmationToken.PaymentMethodPreview, ConfirmationTokenCreateParamsPaymentMethodDatum, PaymentAttemptRecord.PaymentMethodDetail, PaymentIntent.PaymentMethodOption, PaymentIntentConfirmParamsPaymentMethodDatum, PaymentIntentConfirmParamsPaymentMethodOption, PaymentIntentCreateParamsPaymentMethodDatum, PaymentIntentCreateParamsPaymentMethodOption, PaymentIntentModifyParamsPaymentMethodDatum, PaymentIntentModifyParamsPaymentMethodOption, PaymentMethodConfigurationCreateParams, PaymentMethodConfigurationModifyParams, PaymentMethodConfiguration, PaymentMethodCreateParams, PaymentMethod, PaymentRecord.PaymentMethodDetail, SetupIntent.PaymentMethodOption, SetupIntentConfirmParamsPaymentMethodDatum, SetupIntentConfirmParamsPaymentMethodOption, SetupIntentCreateParamsPaymentMethodDatum, SetupIntentCreateParamsPaymentMethodOption, SetupIntentModifyParamsPaymentMethodDatum, and SetupIntentModifyParamsPaymentMethodOption
    • Add support for scalapay on Charge.PaymentMethodDetail, Checkout.Session.PaymentMethodOption, ConfirmationToken.PaymentMethodPreview, ConfirmationTokenCreateParamsPaymentMethodDatum, PaymentAttemptRecord.PaymentMethodDetail, PaymentIntent.PaymentMethodOption, PaymentIntentConfirmParamsPaymentMethodDatum, PaymentIntentConfirmParamsPaymentMethodOption, PaymentIntentCreateParamsPaymentMethodDatum, PaymentIntentCreateParamsPaymentMethodOption, PaymentIntentModifyParamsPaymentMethodDatum, PaymentIntentModifyParamsPaymentMethodOption, PaymentMethodConfigurationCreateParams, PaymentMethodConfigurationModifyParams, PaymentMethodConfiguration, PaymentMethodCreateParams, PaymentMethod, PaymentRecord.PaymentMethodDetail, Refund.DestinationDetail, SetupIntentConfirmParamsPaymentMethodDatum, SetupIntentCreateParamsPaymentMethodDatum, SetupIntentModifyParamsPaymentMethodDatum, and checkout.SessionCreateParamsPaymentMethodOption
    • Add support for mandate on Charge.PaymentMethodDetail.Twint, PaymentAttemptRecord.PaymentMethodDetail.Twint, and PaymentRecord.PaymentMethodDetail.Twint
    • Add support for new values bizum and scalapay on enums PaymentIntentConfirmParams.excluded_payment_method_types, PaymentIntentCreateParams.excluded_payment_method_types, PaymentIntentModifyParams.excluded_payment_method_types, SetupIntentCreateParams.excluded_payment_method_types, SetupIntentModifyParams.excluded_payment_method_types, and checkout.SessionCreateParams.excluded_payment_method_types
    • Change type of PaymentIntentConfirmParamsPaymentMethodOptionTwint.setup_future_usage, PaymentIntentCreateParamsPaymentMethodOptionTwint.setup_future_usage, PaymentIntentModifyParamsPaymentMethodOptionTwint.setup_future_usage, and checkout.SessionCreateParamsPaymentMethodOptionTwint.setup_future_usage from literal('none') to enum('none'|'off_session')
    • Add support for new values bizum and scalapay on enum checkout.SessionCreateParams.payment_method_types
    • ⚠️ Change type of Checkout.Session.PaymentMethodOption.Twint.setup_future_usage and PaymentIntent.PaymentMethodOption.Twint.setup_future_usage from literal('none') to enum('none'|'off_session')
    • Add support for new values bizum and scalapay on enums ConfirmationTokenCreateParamsPaymentMethodDatum.type, PaymentIntentConfirmParamsPaymentMethodDatum.type, PaymentIntentCreateParamsPaymentMethodDatum.type, PaymentIntentModifyParamsPaymentMethodDatum.type, SetupIntentConfirmParamsPaymentMethodDatum.type, SetupIntentCreateParamsPaymentMethodDatum.type, and SetupIntentModifyParamsPaymentMethodDatum.type
    • ⚠️ Add support for new values bizum and scalapay on enums ConfirmationToken.PaymentMethodPreview.type and PaymentMethod.type
    • Add support for new values bizum and scalapay on enums CustomerListPaymentMethodsParams.type, PaymentMethodCreateParams.type, and PaymentMethodListParams.type
    • Add support for credited_items on InvoiceItem.ProrationDetail
    • Add support for new value twint on enums InvoiceCreateParamsPaymentSetting.payment_method_types, InvoiceModifyParamsPaymentSetting.payment_method_types, SubscriptionCreateParamsPaymentSetting.payment_method_types, and SubscriptionModifyParamsPaymentSetting.payment_method_types
    • Add support for discountable on InvoiceCreatePreviewParamsScheduleDetailPhaseAddInvoiceItem, SubscriptionCreateParamsAddInvoiceItem, SubscriptionModifyParamsAddInvoiceItem, SubscriptionSchedule.Phase.AddInvoiceItem, SubscriptionScheduleCreateParamsPhaseAddInvoiceItem, and SubscriptionScheduleModifyParamsPhaseAddInvoiceItem
    • Add support for billing_schedules on InvoiceCreatePreviewParamsSubscriptionDetail, SubscriptionCreateParams, SubscriptionModifyParams, and Subscription
    • Add support for new value max_billed_until on enums InvoiceCreatePreviewParamsSubscriptionDetail.cancel_at, SubscriptionCreateParams.cancel_at, and SubscriptionModifyParams.cancel_at
    • Add support for amount_paid_off_stripe on Invoice
    • ⚠️ Add support for new value twint on enums Invoice.PaymentSetting.payment_method_types and Subscription.PaymentSetting.payment_method_types
    • Add support for twint on Mandate.PaymentMethodDetail and SetupAttempt.PaymentMethodDetail
    • Add support for metadata on PaymentIntent.TransferDatum, PaymentIntentCreateParamsTransferDatum, PaymentIntentModifyParamsTransferDatum, and Subscription.PendingUpdate
    • Add support for payment_data on PaymentIntent.TransferDatum, PaymentIntentCreateParamsTransferDatum, and PaymentIntentModifyParamsTransferDatum
    • ⚠️ Add support for new values bizum and scalapay on enums PaymentIntent.excluded_payment_method_types and SetupIntent.excluded_payment_method_types
    • Add support for blik_authorize on PaymentIntent.NextAction and SetupIntent.NextAction
    • Add support for payment_method_options on PaymentLinkCreateParams, PaymentLinkModifyParams, and PaymentLink
    • Add support for new value bizum on enums PaymentLinkCreateParams.payment_method_types and PaymentLinkModifyParams.payment_method_types
    • ⚠️ Add support for new value bizum on enum PaymentLink.payment_method_types
    • Add support for active on PaymentMethodConfigurationListParams
    • Add support for billed_until on SubscriptionItem
    • Add support for discount and discounts on Subscription.PendingUpdate
    • Add support for verifone_m425, verifone_p630, verifone_ux700, and verifone_v660p on Terminal.Configuration, terminal.ConfigurationCreateParams, and terminal.ConfigurationModifyParams
    • Add support for new values simulated_verifone_m425, simulated_verifone_p630, simulated_verifone_ux700, simulated_verifone_v660p, verifone_m425, verifone_p630, verifone_ux700, and verifone_v660p on enum terminal.ReaderListParams.device_type
    • Add support for api_error and print_content on Terminal.Reader.Action
    • ⚠️ Add support for new value print_content on enum Terminal.Reader.Action.type
    • ⚠️ Add support for new values simulated_verifone_m425, simulated_verifone_p630, simulated_verifone_ux700, simulated_verifone_v660p, verifone_m425, verifone_p630, verifone_ux700, and verifone_v660p on enum Terminal.Reader.device_type
    • Add support for customer on test_helpers.TestClockCreateParams
    • Add support for new value 2026-05-27.dahlia on enum WebhookEndpointCreateParams.api_version
    • Add support for signer on V2.Core.Account.Identity.BusinessDetail.Document.ProofOfRegistration, V2.Core.Account.Identity.BusinessDetail.Document.ProofOfUltimateBeneficialOwnership, v2.core.AccountCreateParamsIdentityBusinessDetailDocumentProofOfRegistration, v2.core.AccountCreateParamsIdentityBusinessDetailDocumentProofOfUltimateBeneficialOwnership, v2.core.AccountModifyParamsIdentityBusinessDetailDocumentProofOfRegistration, v2.core.AccountModifyParamsIdentityBusinessDetailDocumentProofOfUltimateBeneficialOwnership, v2.core.AccountTokenCreateParamsIdentityBusinessDetailDocumentProofOfRegistration, and v2.core.AccountTokenCreateParamsIdentityBusinessDetailDocumentProofOfUltimateBeneficialOwnership
    • Add support for azure_event_grid on V2.Core.EventDestination and v2.core.EventDestinationCreateParams
    • ⚠️ Add support for new value no_azure_partner_topic_exists on enum V2.Core.EventDestination.StatusDetail.Disabled.reason
    • ⚠️ Add support for new value azure_event_grid on enum V2.Core.EventDestination.type
    • Add support for new value azure_event_grid on enum v2.core.EventDestinationCreateParams.type
    • ⚠️ Add support for new value meter_event_value_too_many_digits on enums EventsV1BillingMeterErrorReportTriggeredEvent.Reason.ErrorType.code and EventsV1BillingMeterNoMeterFoundEvent.Reason.ErrorType.code
    • Add support for event notifications V2CommerceProductCatalogImportsFailedEvent, V2CommerceProductCatalogImportsProcessingEvent, V2CommerceProductCatalogImportsSucceededEvent, and V2CommerceProductCatalogImportsSucceededWithErrorsEvent with related object v2.commerce.ProductCatalogImport
    • Add support for error codes payment_method_microdeposit_processing_error and siret_invalid on Invoice.LastFinalizationError, PaymentIntent.LastPaymentError, SetupAttempt.SetupError, SetupIntent.LastSetupError, and StripeError
  • #1813 Emit warning when stripe-notify header is present in response

See the changelog for more details.

API version pinned to 2026-05-27.dahlia; Bizum and Scalapay payment methods added

This release31 featuresNew capabilitiesAI-tallied from the release notes
stripe-node · v22.2.0

This release changes the pinned API version to 2026-05-27.dahlia.

  • #2710 Update generated code
    • Add support for new resource V2.Commerce.ProductCatalogImport
    • Add support for create and retrieve methods on resource V2.Commerce.ProductCatalogImport
    • Add support for bizum_payments and scalapay_payments on Account.capabilities, AccountCreateParams.capabilities, and AccountUpdateParams.capabilities
    • Add support for automatic_transfer_rules_by_currency on BalanceSettingUpdateParams.payments.payouts and BalanceSettings.payments.payouts
    • Add support for start_of_day on BalanceSettingUpdateParams.payments.settlement_timing and BalanceSettings.payments.settlement_timing
    • Add support for description on ChargeCreateParams.transfer_data, PaymentIntent.transfer_data, PaymentIntentCreateParams.transfer_data, and PaymentIntentUpdateParams.transfer_data
    • Add support for bizum on Charge.payment_method_details, ConfirmationToken.payment_method_preview, ConfirmationTokenCreateParams.testHelpers.payment_method_data, PaymentAttemptRecord.payment_method_details, PaymentIntent.payment_method_options, PaymentIntentConfirmParams.payment_method_data, PaymentIntentConfirmParams.payment_method_options, PaymentIntentCreateParams.payment_method_data, PaymentIntentCreateParams.payment_method_options, PaymentIntentUpdateParams.payment_method_data, PaymentIntentUpdateParams.payment_method_options, PaymentMethodConfigurationCreateParams, PaymentMethodConfigurationUpdateParams, PaymentMethodConfiguration, PaymentMethodCreateParams, PaymentMethod, PaymentRecord.payment_method_details, SetupIntent.payment_method_options, SetupIntentConfirmParams.payment_method_data, SetupIntentConfirmParams.payment_method_options, SetupIntentCreateParams.payment_method_data, SetupIntentCreateParams.payment_method_options, SetupIntentUpdateParams.payment_method_data, and SetupIntentUpdateParams.payment_method_options
    • Add support for scalapay on Charge.payment_method_details, Checkout.Session.payment_method_options, Checkout.SessionCreateParams.payment_method_options, ConfirmationToken.payment_method_preview, ConfirmationTokenCreateParams.testHelpers.payment_method_data, PaymentAttemptRecord.payment_method_details, PaymentIntent.payment_method_options, PaymentIntentConfirmParams.payment_method_data, PaymentIntentConfirmParams.payment_method_options, PaymentIntentCreateParams.payment_method_data, PaymentIntentCreateParams.payment_method_options, PaymentIntentUpdateParams.payment_method_data, PaymentIntentUpdateParams.payment_method_options, PaymentMethodConfigurationCreateParams, PaymentMethodConfigurationUpdateParams, PaymentMethodConfiguration, PaymentMethodCreateParams, PaymentMethod, PaymentRecord.payment_method_details, Refund.destination_details, SetupIntentConfirmParams.payment_method_data, SetupIntentCreateParams.payment_method_data, and SetupIntentUpdateParams.payment_method_data
    • Add support for mandate on Charge.payment_method_details.twint, PaymentAttemptRecord.payment_method_details.twint, and PaymentRecord.payment_method_details.twint
    • Add support for new values bizum and scalapay on enums Checkout.SessionCreateParams.excluded_payment_method_types, PaymentIntentConfirmParams.excluded_payment_method_types, PaymentIntentCreateParams.excluded_payment_method_types, PaymentIntentUpdateParams.excluded_payment_method_types, SetupIntentCreateParams.excluded_payment_method_types, and SetupIntentUpdateParams.excluded_payment_method_types
    • Change type of Checkout.SessionCreateParams.payment_method_options.twint.setup_future_usage, PaymentIntentConfirmParams.payment_method_options.twint.setup_future_usage, PaymentIntentCreateParams.payment_method_options.twint.setup_future_usage, and PaymentIntentUpdateParams.payment_method_options.twint.setup_future_usage from literal('none') to enum('none'|'off_session')
    • Add support for new values bizum and scalapay on enum Checkout.SessionCreateParams.payment_method_types
    • ⚠️ Change type of Checkout.Session.payment_method_options.twint.setup_future_usage and PaymentIntent.payment_method_options.twint.setup_future_usage from literal('none') to enum('none'|'off_session')
    • Add support for new values bizum and scalapay on enums ConfirmationTokenCreateParams.testHelpers.payment_method_data.type, PaymentIntentConfirmParams.payment_method_data.type, PaymentIntentCreateParams.payment_method_data.type, PaymentIntentUpdateParams.payment_method_data.type, SetupIntentConfirmParams.payment_method_data.type, SetupIntentCreateParams.payment_method_data.type, and SetupIntentUpdateParams.payment_method_data.type
    • ⚠️ Add support for new values bizum and scalapay on enums ConfirmationToken.payment_method_preview.type and PaymentMethod.type
    • Add support for new values bizum and scalapay on enums CustomerListPaymentMethodsParams.type, PaymentMethodCreateParams.type, and PaymentMethodListParams.type
    • Add support for credited_items on InvoiceItem.proration_details
    • Add support for new value twint on enums InvoiceCreateParams.payment_settings.payment_method_types, InvoiceUpdateParams.payment_settings.payment_method_types, SubscriptionCreateParams.payment_settings.payment_method_types, and SubscriptionUpdateParams.payment_settings.payment_method_types
    • Add support for discountable on InvoiceCreatePreviewParams.schedule_details.phases[].add_invoice_items[], SubscriptionCreateParams.add_invoice_items[], SubscriptionSchedule.phases[].add_invoice_items[], SubscriptionScheduleCreateParams.phases[].add_invoice_items[], SubscriptionScheduleUpdateParams.phases[].add_invoice_items[], and SubscriptionUpdateParams.add_invoice_items[]
    • Add support for billing_schedules on InvoiceCreatePreviewParams.subscription_details, SubscriptionCreateParams, SubscriptionUpdateParams, and Subscription
    • Add support for new value max_billed_until on enums InvoiceCreatePreviewParams.subscription_details.cancel_at, SubscriptionCreateParams.cancel_at, and SubscriptionUpdateParams.cancel_at
    • Add support for amount_paid_off_stripe on Invoice
    • ⚠️ Add support for new value twint on enums Invoice.payment_settings.payment_method_types and Subscription.payment_settings.payment_method_types
    • Add support for twint on Mandate.payment_method_details and SetupAttempt.payment_method_details
    • Add support for metadata on PaymentIntent.transfer_data, PaymentIntentCreateParams.transfer_data, PaymentIntentUpdateParams.transfer_data, and Subscription.pending_update
    • Add support for payment_data on PaymentIntent.transfer_data, PaymentIntentCreateParams.transfer_data, and PaymentIntentUpdateParams.transfer_data
    • ⚠️ Add support for new values bizum and scalapay on enums PaymentIntent.excluded_payment_method_types and SetupIntent.excluded_payment_method_types
    • Add support for blik_authorize on PaymentIntent.next_action and SetupIntent.next_action
    • Add support for payment_method_options on PaymentLinkCreateParams, PaymentLinkUpdateParams, and PaymentLink
    • Add support for new value bizum on enums PaymentLinkCreateParams.payment_method_types and PaymentLinkUpdateParams.payment_method_types
    • ⚠️ Add support for new value bizum on enum PaymentLink.payment_method_types
    • Add support for active on PaymentMethodConfigurationListParams
    • Add support for billed_until on SubscriptionItem
    • Add support for discount and discounts on Subscription.pending_update
    • Add support for verifone_m425, verifone_p630, verifone_ux700, and verifone_v660p on Terminal.ConfigurationCreateParams, Terminal.ConfigurationUpdateParams, and Terminal.Configuration
    • Add support for new values simulated_verifone_m425, simulated_verifone_p630, simulated_verifone_ux700, simulated_verifone_v660p, verifone_m425, verifone_p630, verifone_ux700, and verifone_v660p on enum Terminal.ReaderListParams.device_type
    • Add support for api_error and print_content on Terminal.Reader.action
    • ⚠️ Add support for new value print_content on enum Terminal.Reader.action.type
    • ⚠️ Add support for new values simulated_verifone_m425, simulated_verifone_p630, simulated_verifone_ux700, simulated_verifone_v660p, verifone_m425, verifone_p630, verifone_ux700, and verifone_v660p on enum Terminal.Reader.device_type
    • Add support for customer on TestHelpers.TestClockCreateParams
    • Add support for new value 2026-05-27.dahlia on enum WebhookEndpointCreateParams.api_version
    • Add support for signer on V2.Core.Account.identity.business_details.documents.proof_of_registration, V2.Core.Account.identity.business_details.documents.proof_of_ultimate_beneficial_ownership, V2.Core.AccountCreateParams.identity.business_details.documents.proof_of_registration, V2.Core.AccountCreateParams.identity.business_details.documents.proof_of_ultimate_beneficial_ownership, V2.Core.AccountTokenCreateParams.identity.business_details.documents.proof_of_registration, V2.Core.AccountTokenCreateParams.identity.business_details.documents.proof_of_ultimate_beneficial_ownership, V2.Core.AccountUpdateParams.identity.business_details.documents.proof_of_registration, and V2.Core.AccountUpdateParams.identity.business_details.documents.proof_of_ultimate_beneficial_ownership
    • Add support for azure_event_grid on V2.Core.EventDestinationCreateParams and V2.Core.EventDestination
    • ⚠️ Add support for new value no_azure_partner_topic_exists on enum V2.Core.EventDestination.status_details.disabled.reason
    • ⚠️ Add support for new value azure_event_grid on enum V2.Core.EventDestination.type
    • Add support for new value azure_event_grid on enum V2.Core.EventDestinationCreateParams.type
    • ⚠️ Add support for new value meter_event_value_too_many_digits on enums EventsV1BillingMeterErrorReportTriggeredEvent.reason.error_types[].code and EventsV1BillingMeterNoMeterFoundEvent.reason.error_types[].code
    • Add support for event notifications V2CommerceProductCatalogImportsFailedEvent, V2CommerceProductCatalogImportsProcessingEvent, V2CommerceProductCatalogImportsSucceededEvent, and V2CommerceProductCatalogImportsSucceededWithErrorsEvent with related object V2.Commerce.ProductCatalogImport
    • Add support for error codes payment_method_microdeposit_processing_error and siret_invalid on Invoice.last_finalization_error, PaymentIntent.last_payment_error, SetupAttempt.setup_error, SetupIntent.last_setup_error, and StripeError
  • #2723 Emit warning when stripe-notify header is present in response
  • #2717 Add V2List and V2ListPromise types for v2 list endpoints
    • Adds V2List and V2ListPromise types to represent API v2 list responses. These types include deprecated fields from the previously returned list shapes. These fields will be removed in the next major release.
  • #2715 Add WinterTC compatibility ESLint rule
  • #2711 Export manually maintained types for OAuthToken and OAuth param classes
    // ❌ Before (v22.0.0-v22.1.1)
    const oAuthToken: Stripe.OAuthToken = {};
    
    // ✅ After (works on v22.1.2+)
    const oAuthToken: Stripe.OAuthToken = {};
  • #2712 Exported types for nested param classes
    • Types inside nested param class namespaces(e.g. Stripe.V2.Core.AccountCreateParams.Configuration, Stripe.V2.Core.AccountCreateParams.Dashboard) are now accessible.

See the changelog for more details.

API Changelog · v2026-05-27.dahlia

Payments

  • Adds support for Twint as a payment method for recurring payments
  • Adds destination payment description and metadata support to transfer data
  • Adds active status filtering to payment method configurations
  • Adds card brand restrictions to Payment Links
  • Adds support for Scalapay payments

Billing

  • Adds discount eligibility options for add-on invoice items on Subscriptions and Preview Invoice APIs
  • Adds amount paid off Stripe property to Invoice object
  • Adds billing schedules to enable prebilling on subscriptions
  • Adds discount and discounts properties to pending subscription updates
  • Adds metadata support to pending subscription updates
  • Adds credited items information to invoice item proration details
  • Adds customer parameter to test clock creation

Terminal

  • Adds support for printing images on Terminal readers with embedded printers
  • Adds support for Verifone third-party device types to Terminal APIs
  • Adds API error details to Terminal reader action failures

Elements

  • Renames Link Authentication Element to Contact Details Element
  • Adds the ability to collect email in Checkout Sessions with Contact Details Element

Connect

  • Adds digital attestation support to Accounts v2 for proof of registration and beneficial ownership verification
  • Adds automatic transfer rules to balance settings
  • Adds the ability to configure custom start of day per connected account

Additional updates

  • Adds support for Bizum payments

Radar now blocks high-risk transactions across all payment methods

This release1 featureNew capabilitiesAI-tallied from the release notes

Radar now blocks high-risk transactions across all supported payment methods; defends against new fraud types like multi-account abuse and pay-as-you-go abuse, regardless of which payment processor you use; and gives platforms new tools to evaluate and mitigate merchant risk on and off Stripe.

Sandbox create and claim commands ship for IDE onboarding

This release2 featuresNew capabilities1 enhancementImprovements to existing features1 fixBug fixesAI-tallied from the release notes
Stripe CLI · v1.42.0

Changelog

  • fa17253ae6156ecc90ea0feb860db2c44136ab49 Add stripe sandbox create and claim commands for agentic IDE onboarding (#1577)
  • f6c6986fb42a61cacf4514f03c13321004825cda Improve expired API key error message (#1602)
  • def5138c3a721590637d03bd5c56a5a8e242ee44 Restrict install-test workflow to workflow_dispatch and schedule only (#1596)
  • 5b3b9a80b4fa584fcf6fe949ba1d8c611ab7c75b Support unauthenticated plugin lookup for install and upgrade (#1587)
  • 53666447d6944cca0453549fe37c9ff0df966128 fix: direct unauthenticated users to login when docs plugin is unavailable (#1600)

macOS keychain visibility retried; plugin hints now in --help

This release1 enhancementImprovements to existing features2 fixesBug fixesAI-tallied from the release notes
Stripe CLI · v1.41.2

Changelog

  • 77d0ae046bc132639a70df62d75f9d7f2c74a713 Add keychain visibility retry for macOS (#1579)
  • e5f95ea39e66496f5a5770349d9c6233450aed76 Fix release target to chain tag and push commands correctly (#1592)
  • 2600b2e89ad8fd0464e8b6019f32c05b751c8deb Make plugin hint commands visible in --help for discoverability (#1594)

.env writes protected from symlink targets

This release3 featuresNew capabilities2 enhancementsImprovements to existing features2 fixesBug fixesAI-tallied from the release notes
Stripe CLI · v1.41.1

Changelog

  • a25a0a9261a592c81b76bd9db75e9d4d74aa4c30 Bump github.com/go-git/go-billy/v5 from 5.8.0 to 5.9.0 (#1588)
  • efec00c84b5d01d1c378cdff6a7355647c513977 Capture plugin name in install telemetry (#1576)
  • 69cf2f795a461d7aad5f80fa651f1bc65e0f8707 Emit Claude Code plugin hint to stderr (#1550)
  • 59df362e14ae9988d2f4b0b66b8b627ac4545f9e Protect writes from symlink targets (#1586)
  • 754e7bc31b78aa188c75d600b79de4d52135b7b3 Re-enable test workflow on pull_request events (#1578)
  • dffad7ec143fdb8cb0f198f1e3b78a5327ed9de5 Read consolidated Stripe-Notice header (#1570)
  • ec6b9079c5eae7b86c3377e2d2746a4ea1381c8c Refactor symlink protection for .env writes (#1574)
  • e5de13915948ebfd69d0dec19dc05bfecfd37d16 Resolve plugin subcommand paths for telemetry analytics (#1567)
  • c2f0d364be8731e6bd113838ac5e8272f7e6aef8 Use plugin metadata endpoint for plugin installs when API key is available (#1575)
  • 776d7b57c33aa3974916ee83d9e25a438a88a3c0 fix fixture path losing suffix after dynamic ID substitution (#1549)

At Stripe Sessions and our inaugural SaaS Platform Leaders Summit, vertical SaaS leaders shared how they’re staying differentiated as AI raises the bar for software. The takeaways: why payments and financial services create moats that AI can’t easily replicate, how platforms are moving from AI experimentation to monetization, and why platforms are expected to lead the way on agentic commerce.

  • #2703 Export Decimal type from Stripe namespace

    • Added Stripe.Decimal as a usable type in the Stripe namespace, enabling type annotations like function takesDecimal(d: Stripe.Decimal).
  • #2704 Fix file upload regression: restore multipart request data processor

    • Fixed file uploads failing with StripeInvalidRequestError on the /v1/files endpoint since v22.

See the changelog for more details.

  • #1804 Update generated code for private-preview
    • Add support for new resource PaymentLocation
    • Add support for create, delete, modify, and retrieve methods on resource PaymentLocation
    • Add support for protections on AccountCreateParamsCapabilityCardPayment, AccountModifyParamsCapabilityCardPayment, and Capability
    • Add support for gift_card on ConfirmationToken.PaymentMethodPreview, ConfirmationTokenCreateParamsPaymentMethodDatum, PaymentIntentConfirmParamsPaymentMethodDatum, PaymentIntentCreateParamsPaymentMethodDatum, PaymentIntentModifyParamsPaymentMethodDatum, PaymentMethodCreateParams, PaymentMethod, SetupIntentConfirmParamsPaymentMethodDatum, SetupIntentCreateParamsPaymentMethodDatum, SetupIntentModifyParamsPaymentMethodDatum, and SharedPayment.GrantedToken.PaymentMethodDetail
    • Add support for new value gift_card on enums ConfirmationTokenCreateParamsPaymentMethodDatum.type, PaymentIntentConfirmParamsPaymentMethodDatum.type, PaymentIntentCreateParamsPaymentMethodDatum.type, PaymentIntentModifyParamsPaymentMethodDatum.type, SetupIntentConfirmParamsPaymentMethodDatum.type, SetupIntentCreateParamsPaymentMethodDatum.type, and SetupIntentModifyParamsPaymentMethodDatum.type
    • ⚠️ Add support for new value gift_card on enums ConfirmationToken.PaymentMethodPreview.type, PaymentMethod.type, and SharedPayment.GrantedToken.PaymentMethodDetail.type
    • Add support for new value gift_card on enums CustomerListPaymentMethodsParams.type, PaymentMethodCreateParams.type, and PaymentMethodListParams.type
    • Add support for metadata on delegated_checkout.RequestedSessionConfirmParams
    • Add support for credited_items on InvoiceItem.ProrationDetail
    • Add support for network_lifecycle on Issuing.Dispute
    • Add support for new value gift_card on enums PaymentIntentConfirmParams.excluded_payment_method_types, PaymentIntentCreateParams.excluded_payment_method_types, PaymentIntentModifyParams.excluded_payment_method_types, SetupIntentCreateParams.excluded_payment_method_types, and SetupIntentModifyParams.excluded_payment_method_types
    • ⚠️ Add support for new value gift_card on enums PaymentIntent.excluded_payment_method_types and SetupIntent.excluded_payment_method_types
    • Add support for status_details on Subscription
  • #1805 Add EventNotificationHandler (private preview)

See the changelog for more details.

  • #1802 Update generated code for private-preview
    • Add support for debit_card on V2.Core.Account.Configuration.CardCreator.Capability.Consumer.Lead, V2.Core.Account.Identity.Attestation.TermsOfService.CardCreator.Consumer.Lead, v2.core.AccountCreateParamsConfigurationCardCreatorCapabilityConsumerLead, v2.core.AccountCreateParamsIdentityAttestationTermsOfServiceCardCreatorConsumerLead, v2.core.AccountModifyParamsConfigurationCardCreatorCapabilityConsumerLead, and v2.core.AccountModifyParamsIdentityAttestationTermsOfServiceCardCreatorConsumerLead
    • ⚠️ Add support for new value consumer.lead.debit_card on enums V2.Core.Account.FutureRequirement.Entry.Impact.RestrictsCapability.capability and V2.Core.Account.Requirement.Entry.Impact.RestrictsCapability.capability
    • ⚠️ Add support for new value consumer.lead.debit_card on enum EventsV2CoreAccountIncludingConfigurationCardCreatorCapabilityStatusUpdatedEvent.updated_capability

See the changelog for more details.

This morning at our annual conference, Stripe Sessions, we shared 288 new products and features with more than 9,000 business leaders and builders. We're making Stripe even more programmable; protecting and propelling your business with the strength of the Stripe network; and building economic infrastructure for AI.

Here's everything we announced.

Payments

Today, we launched and demoed payments infrastructure for the next era of commerce. We expanded the Agentic Commerce Suite through partnerships with Meta and Google; announced a new way to grant agents the ability to pay with Link's agent wallet; and unveiled Checkout studio, which helps you build, analyze, and optimize high-converting checkouts in a few clicks. Here's what's new:

Agentic commerce

  • You can now sell through AI agents by uploading your product catalog and managing agent access directly from the Stripe Dashboard with the Agentic Commerce Suite.
  • We previewed the ability for platforms to use the Agentic Commerce Suite, allowing their connected accounts to become agent-ready with discovery, checkout, payments, and fraud detection handled through a single Stripe integration.
  • We partnered with Meta to enable native checkout inside ads on Facebook so discovery and purchase happen in one flow.
  • Customers will soon be able to buy your products in AI Mode and the Gemini app via the Universal Commerce Protocol (UCP), through a new partnership between Stripe and Google.
  • Agents can now programmatically transact with your business via microtransactions, recurring payments, and more with the Machine Payments Protocol (MPP), co-authored by Stripe and Tempo.
  • You can now accept payments from agents over MPP in stablecoins as well as fiat through cards, Klarna, and Affirm via Shared Payment Tokens (SPTs), using our Payment Intents API.

Link

  • You can now grant agents the ability to pay with Link's agent wallet, while maintaining control via spending approvals and full purchase visibility.
  • Link now supports additional payment methods. Via Link, US businesses can now accept Pix in Brazil and stablecoins. We also previewed the ability for US businesses to accept UPI via Link in India.
  • You can now see Link's impact on your conversion, authorization rates, and payments costs in a dedicated tab in the Dashboard.

Optimized Checkout Suite

  • We previewed Checkout studio, a new way for you to configure, analyze, and optimize your checkout with an AI assistant, live transaction replay, A/B testing, and personalized recommendations.
  • We previewed Stripe Checkout's new embedded form, built for embedded use cases like sidebars, chat boxes, and modals.
  • More payment methods, including Pix and UPI, now support subscriptions, localized currency presentment, and cross-border payments.
  • You can now accept Sunbit in the US, Bizum in Spain, and Pay by Bank in Finland.
  • You can now accept Bizum, BLIK, and Pay by Bank for cross-border payments.
  • You can now accept TWINT for recurring transactions.
  • You can now automatically detect and display your customer's preferred currency with a new Adaptive Pricing AI model that analyzes dozens of session signals in real time.
  • You can now use Adaptive Pricing to localize subscription prices to your customer's domestic currency.
  • We previewed a new way for your customers to save a card in your app by tapping it on their Android device instead of manually entering the card information.

Stripe Terminal

  • We announced the Stripe Reader T600, a new countertop device with an eight-inch screen and the power to run custom apps that support experiences like loyalty and upsells.
  • We announced the ability to process in-person payments with Terminal in 15 additional markets, including Hong Kong and Mexico.
  • We announced the ability to accept additional payment methods such as Alipay, Klarna, and UnionPay International for in-person payments with Terminal.
  • We previewed Terminal's standalone mode, so you can quickly start accepting payments on Stripe readers with no code or point of sale required.

Stripe Managed Payments

  • All digital businesses can now use Managed Payments, Stripe's merchant of record solution. It helps digital businesses sell globally by handling indirect tax compliance in 80+ countries, as well as fraud prevention, dispute management, and customer support.

Payments Intelligence Suite

  • We previewed the ability to A/B test Authorization Boost against your existing payments performance.
  • You can now use Authorization Boost's new AI-powered optimizations, including support for Data Only authentication flows and PINless debit retries, helping increase acceptance rates by an average of 3.8% and lower processing costs by up to 3.3%.
  • You can now use Stripe's 3DS solution on a standalone basis—enabling regulatory compliance, including support for exemptions, and fraud protection to payments processed by another payment service provider.
  • You can now use the Stripe Dashboard assistant for payments analytics, which investigates performance issues, diagnoses root causes, and recommends next steps in natural language.

Radar

Millions of global businesses use Stripe Radar to fight fraud, from leading AI companies like OpenAI, Anthropic, ElevenLabs, and Cursor to global enterprises like PepsiCo and Hertz. Today, we announced the biggest-ever upgrades to Radar, helping you to defend against new types of fraud—including token abuse and account fraud—protect more of your payments on and off Stripe, and win more disputes. Here's what's new:

Revenue

Agentic activity requires new, real-time infrastructure for metering, rating, alerting, and payments. We upgraded our Revenue suite to support new AI-native business models with dimensional pricing and streaming payments. We also made Stripe more programmable with three new Stripe Billing customizations and expanded access to real-time, ready-to-query data. Here's what's new:

Stripe Billing

  • You can now power a broader range of usage-based and hybrid pricing models with Metronome, a Stripe product. You can manage commits, multidimensional pricing structures, bespoke contracts, and more, with real-time revenue visibility down to the account, contract, and product level.
  • You can now access and manage Metronome contracts, customers, and data directly in the Stripe Dashboard with the Metronome app.
  • We announced the ability to support streaming payments by combining Metronome and Tempo, allowing you to get paid the instant value is delivered and cost incurred.
  • You can now track credit balances at industry-leading rates, get instant low-balance alerts, and configure automatic credit top-ups.
  • We previewed support for three new types of Billing customizations, allowing you to programmatically define how subscription items appear on invoices, how prorations behave, and how balances and credits are applied.
  • We previewed payment plans that you can use to accept installment payments with automated collection, giving your customers more flexibility and improving cash flow.
  • We previewed subscription invoice revisions, so you can edit finalized subscription invoices and automatically void the original invoice.

Stripe Tax

  • You can now automate US tax filing, track status, and view filing details in the Stripe Dashboard, powered by TaxJar.
  • We previewed additional Stripe Tax Connectors for Shopify and NetSuite, so you can extend Tax to platforms where you already do business.
  • We previewed the ability for Tax to verify tax IDs against government databases during checkout flows, blocking invalid IDs.
  • Payment Intents API users can now calculate and record tax on a payment with a single parameter—no separate API calls required.
  • Businesses located in Liechtenstein and Mexico and digital sellers in Sri Lanka can now use Tax. We will also offer full support for businesses in Malaysia and remote sellers in French and Spanish territories soon.

Data

  • We previewed the ability to retrieve real-time subscription metrics within AI agents using the Stripe MCP, or within Stripe Console.
  • We previewed Stripe Database, giving you real-time Stripe data in a managed, hosted, read-only Postgres database. You can spin up the database with one click from the Dashboard or a single CLI command, allowing you to build and ship applications faster.
  • We previewed the next generation of Stripe Data Pipeline, enabling real-time data syncs to Google Sheets with more data destinations coming soon.
  • You can now sync all of your Stripe data directly to Databricks with Data Pipeline.
  • We previewed the ability for you to programmatically retrieve prebuilt financial reports across accounts in your organization using the Reports API v2.
  • We previewed the ability for businesses using Stripe Sigma to execute custom SQL queries programmatically for advanced data modeling and reporting with the Reports API v2.

Money Management

The AI economy is growing at breakneck speed, and more companies have a global footprint from day one. But the tools to manage your money haven't kept up, with finances typically scattered across half a dozen apps and spreadsheets. We previewed new capabilities to help you store, spend, and manage money—including a Stripe card that rewards you for spending, free transfers to other Stripe Treasury users, and MCP support for Treasury APIs so you can build your own financial agents. Here's what's new:

Stripe Atlas

  • We announced the ability for Atlas founders to track and receive SAFE funding from investors via ACH, wire transfer, or stablecoin transfer with a Treasury financial account.

Stripe Treasury

  • We announced that for US and UK businesses, Treasury will support storage in 15 currencies by the end of the year.
  • You can now instantly transfer funds between US businesses on Stripe for free.
  • US users can now spend their settled Stripe earnings with a Stripe card powered by Mastercard, with 2% cashback on purchases.
  • We announced that Treasury balances in the US will earn Stripe credits that you can apply toward your processing fees.
  • You can now see a full view of balances, transactions, cards, and spending directly from your phone with the new mobile experience for Treasury within the Stripe app.
  • We announced that Treasury will be available in Australia and Canada by the end of the year. We will also add stablecoin support for an additional 41 markets.
  • We announced that Treasury balances will soon be backed by noncustodial wallets from Privy, enabling businesses in more than 150 markets to instantly move money across borders.
  • We announced agent-ready financial accounts that enable agents to check balances, pay invoices, store funds, create cards, send money, and manage cash flow—with human-in-the-loop confirmation for key actions.

Stripe Global Payouts

  • We previewed expanded Global Payouts coverage, so you can send payouts to recipients in more than 100 countries in fiat and 160 countries in stablecoins.
  • We previewed the ability for Global Payouts users to send USD payouts to Link users instantly.

Embedded Finance

Stripe Connect powers more than 16,000 platforms, including Shopify, DoorDash, and Substack, which collectively help 11 million businesses accept payments. Today, we shared new ways to help platforms grow as AI reshapes software, including a new growth studio that uses Stripe data to surface actionable recommendations and the ability to launch new revenue streams through Treasury and Stripe Capital. Here's what's new:

Stripe Connect

  • We previewed the platform growth studio, which generates recommendations directly in the Dashboard to help you expand your product offerings and grow faster. It includes AI-powered margin optimization recommendations, peer benchmarking, and no-code promotional pricing campaigns for local payment methods and Instant Payouts.
  • Network cost passthrough (IC++) is now available to platforms in 45 markets, including the US, Canada, UK, and EU. You can now enable IC+ pricing and prebuilt reports for your connected accounts directly in the Dashboard.
  • We previewed new embedded components for your connected accounts to order Terminal hardware, scan checks, view business performance charts, and access balance or payout reconciliation reports.
  • We previewed the ability for you to use Stripe Managed Risk via API, allowing platforms and banks to outsource risk management to Stripe while maintaining full control over the user experience.
  • Platforms will soon be able to launch full-scale financial services with less operational overhead using Managed Risk for Treasury.
  • Platforms can now use Smart Disputes to automatically compile and submit dispute evidence on behalf of their connected accounts.
  • Platforms can now mitigate risk across their business with Radar, featuring 0-to-100 fraud scores for every business and transaction, AI-powered insights that explain why accounts are flagged, and a comprehensive view of account activity.
  • Your connected accounts can now onboard onto your platform in one click with networked onboarding. We also previewed support for Link wallet users to onboard in one click, even if they don't already have a Stripe account.
  • Marketplaces in the US, UK, European Economic Area (EEA), and Canada can now programmatically pay out funds to sellers' connected accounts across any of these regions with cross-border payouts.
  • We previewed the ability for marketplaces that sell in Europe to continue using multiple payment providers while making unified payouts through Stripe. This will help marketplaces comply with upcoming PSD3 regulations without disrupting their multiprocessor setups.
  • We previewed wallets for marketplace sellers to receive earnings, hold funds, and make on-marketplace purchases using their financial account balance.
  • We previewed the ability for marketplaces to allow both sellers and customers to spend their financial account balance on the marketplace and other businesses by issuing prepaid debit cards.
  • We previewed how we will use stablecoin rails to allow Connect marketplaces to instantly transfer funds to sellers in 100 additional countries.

Stripe Treasury for platforms

  • You will soon be able to offer Treasury and spend cards for your users in just a few lines of code with embedded components.
  • We previewed several new features available through Treasury for platforms, including bill pay, automated cash rewards, cash acceptance, check acceptance, real-time payments, and accounting integrations.

Stripe Capital for platforms

Stripe Issuing

  • We previewed Issuing for agents, which allows businesses and agentic platforms to programmatically issue single-use virtual cards, so agents can make purchases and manage financial workflows autonomously.
  • We previewed the ability to launch a live card program for humans and agents in minutes, with self-serve onboarding, prebuilt program templates, and live funds.
  • We previewed consumer debit issuing, so you can offer prepaid rewards cards, disbursements, and branded cards.

Stablecoins and Crypto

Stablecoins and crypto are helping you move money faster and more affordably around the world. We introduced a new primitive from Privy to manage multichain balances with one simple API, expanded Bridge's Open Issuance so businesses can launch and manage their own stablecoins, and launched stablecoin-backed cards for recipients to spend funds locally or globally. Here's what's new:

Stripe Platform

As agents become a foundational part of how developers build and operate on Stripe, we're investing in three areas: making Stripe extensible and programmable with primitives like custom objects; giving agents reliable tools for building, integrating, and operating on Stripe; and introducing new agentic surfaces to help you analyze and act on your Stripe data. Here's what's new:

  • We previewed Stripe Console, an agentic execution environment built directly into the Dashboard. Ask a business question in plain language and Console returns a structured diagnosis drawn from across your Stripe products. Or, give Console a Stripe-related task, and it will carry it out, asking for confirmation before taking consequential actions.
  • AI partners and developer platforms can now use the Claimable Sandboxes API to embed Stripe into their platforms. We've also added more test data, including product catalogs, that you can push to your live Stripe account.
  • We previewed the ability to securely create and pass live API keys to your platform on behalf of your users with automated key exchanges from Stripe's claimable sandboxes.
  • We previewed custom objects, so you can model your business data and logic inside Stripe. You can define, store, and manage custom objects with typed fields, relationships, methods, and the same APIs and operational controls as native Stripe resources.
  • Stripe Workflows is now generally available. We also previewed new features, including looping, third-party custom actions, prebuilt actions for Mailchimp and Slack, programmatic invocation, and support for Connect.
  • We previewed the ability for app developers to build full-page, multitab experiences inside the Stripe Dashboard.
  • You can now provision, manage, and bill for your entire dev stack—including hosting, databases, authentication, observability, analytics, and AI—with Stripe Projects.
  • We previewed the ability to set up agent guardrails in Stripe to assign agent identities, enforce scope rules, and configure approval flows for sensitive actions.

What's coming later this year

Today, we launched our public roadmap: an itemized list with hundreds of detailed entries through Q1 2027, covering products, features, and improvements across Payments, Revenue, Money Management, and beyond. While it's extensive, it's noncomprehensive—we're moving at breakneck speed, so you'll see us ship even more things that aren't on the roadmap, too.

Here's what you can expect:

Payments

Agentic commerce

  • [Q2, public preview] Agents can initiate payments using a customer's permitted payment method, without exposing the underlying credentials.

Link

  • [Q2, GA] A native Link app for iOS and Android gives buyers a single place to manage payment methods, view transaction history, and automate purchases with configurable alerts.

Payment processing

  • [Q2, GA] Route Apple Pay payments through the local eftpos network in Australia.
  • [Q2, GA] Accept Satispay for cross-border payments.
  • [Q2, GA] Accept Scalapay, an Italian buy now, pay later method, for cross-border and domestic payments.
  • [Q2, GA] Legal CBD businesses can use Stripe.
  • [Q2, public preview] Integrate Stripe Payments directly into Aptos ONE workflows.
  • [Q3, public preview] Use an off-session payments API for transactions you initiate.
  • [Q3, public preview] Build session-based payment flows that bill at the granularity of usage events like token consumption and API invocations.
  • [Q3, GA] Dating service businesses can use Stripe.
  • [Q4, GA] Convert 13+ currencies instantly in your Stripe Payments balance—from the Dashboard or via API—in 35 markets including the US, UK, EU, CH, SG, HK, AU, and NZ.

Stripe Terminal

  • [Q4, public preview] Stripe Terminal supports dynamic currency conversion to present pricing in the customer's local currency.
  • [Q4, GA] Stripe Terminal supports multicapture, so merchants can partially capture an authorized payment multiple times.
  • [Q4, public preview] Use Tap to Pay on Android in Japan.

Stripe Financial Connections

  • [Q2, private preview] Use

In the Sessions keynote, we talked about how agents are becoming active participants in the internet economy, and how we're building the infrastructure to support them.

Agents have become increasingly capable in recent months, but making purchases across the internet remains difficult. While machine payments protocols are still gaining adoption, agents need to work with the payment options sellers and consumers use today.

Today we're launching Link's wallet for agents, built on top of Stripe's new Issuing for agents. You can now give agents programmatic access to Link and the ability to get a one-time-use card or a Shared Payment Token (SPT), backed by the cards and bank accounts already in your wallet. The agent never gets access to your raw payment credentials.

You can review and approve each spend request from the agent on the web, or in Link's new iOS and Android apps. This makes it easy for consumers to enable personal AI agents such as OpenClaw to make an authorized purchase on their behalf.

If you're a developer or business building consumer-facing agents, such as personal assistants, Link's wallet for agents removes the need to build wallet infrastructure from scratch. Link handles the abstraction across payment options your agent might need—like cards and SPTs (with stablecoins and other payment methods coming soon). It also takes care of fund flow complexity and helps you reach Link's customer base of more than 200 million consumers.

How Link's wallet for agents works

Imagine you are building a shopping agent that recommends apparel to your consumers. First, the consumer grants your agent access to their Link wallet via a standard OAuth flow.

Once your agent has access, it can create a spend request to get either a one-time-use card or an SPT to complete the transaction. Your agent provides context on the transaction, so the person can understand and approve the request. In both card and machine-native flows, the payment credential can be scoped with controls like amount, currency, and merchant. Support for agentic tokens, stablecoins, and other payment types are coming soon.

link-cli spend-request create \
payment-method-id csmrpd_12345 \
merchant-name "Powdur" \
merchant-url "https://powdur.com" \
amount 3500 \
context "Purchasing the Powdur Glow Renewal Vitamin C Serum as a gift for $35." \
request-approval

The consumer gets a notification and approves the spend request in Link (on the web, or in the Link iOS or Android app). Today, each request requires the person's review before the credential is shared with your agent. We're planning on expanding these controls to let people set spending limits, and choose when agents can act without additional approval.

After approval, Link returns the one-time-use card or SPT to your agent for it to complete the purchase. The person can track agent spending and manage connected agents directly in Link.

Stripe Issuing for agents

Link's wallet for agents is built directly on top of Stripe's Issuing primitives. For businesses that want to build and customize their own agentic wallets and cards, Issuing for agents gives developers access to the full set of Issuing APIs to power agentic spending and custom financial workflows for agents and their users.

Businesses can design user-facing experiences to fit their product, including onboarding, fund flows, and spending controls. They can define when and how agents move funds, set permissions at the card level, introduce fraud controls at transaction authorization, and gain visibility into historical and real-time card activity.

Issuing for agents provides the underlying infrastructure for these experiences, from single-use virtual cards and fund storage to spending controls, transaction monitoring, and advanced fraud tools. This infrastructure supports a range of use cases:

  • Developers can use agents to automate their own business spend, allowing them to create programmatic workflows and recurring purchases.
  • Fintech providers can embed agent-issued cards to control and reconcile spend for expense management in real time.
  • Vertical SaaS platforms can issue agent cards to SMB customers, letting agents automate spend under the platform's own brand.
  • Marketplaces can issue cards to sellers, so their agents can automate supplier payments, logistics, and fulfillment purchases.

Get started

Get started today with Link's wallet for agents, and read our docs to learn more about Issuing for agents.

Last Checked
2h ago
Category
Tracking since Aug 15, 2017