Skip to content
Create account or Sign in
The Stripe Docs logo
Search/Ask AI
Create accountSign in
  • Get started
  • Payments
  • Revenue
  • Risk
  • Data
  • Money management
  • Stablecoins
  • Embedded finance
  • Developer resources
More
APIs & SDKsHelp
Overview
Versioning
Changelog
    Endive
    Dahlia
    Clover
    Basil
    Acacia
    Previous versions
Upgrade your integrationHow API versioning works
Essentials
SDKs
API
Events
Testing
Stripe CLI
Tools
Stripe Dashboard
Stripe Projects
Provisioning
Workbench
Developers Dashboard
Stripe for Visual Studio Code
Terraform
Stripe Discord server
Features
Workflows
Batch jobs
Stripe health alertsFile uploads
AI tools
Agent pluginsModel Context ProtocolAgent skillsStripe Directory
Extend Stripe
Overview
Build Stripe apps
Use apps from Stripe
Build extensions
Custom objects
Security and privacy
Security
Activity logsStripebot web crawler
Privacy
Partners
Partner ecosystem
Partner certification
United States
English (United States)
  1. Home/
  2. Developer resources/
  3. Changelog/
  4. Endive/
  5. 2026-09-30.endive
Breaking changes

Standardizes SEPA Direct Debit payment settings in the Accounts APIBreaking changes

What’s new

The sepa_debit_payments.creditor_id property on Accounts now returns Stripe’s country-specific shared SEPA Creditor Identifier when an account doesn’t have a custom one. Previously, this property was omitted for accounts using the shared identifier.

You can now set a custom SEPA Creditor Identifier to be used for SEPA Direct Debit payments when you create a v1 Account. In Accounts v2, you can set a custom SEPA Creditor Identifier when you create or update a v2 Account using the configuration.merchant.sepa_debit_payments.creditor_id parameter.

Why is this a breaking change?

The sepa_debit_payments.creditor_id property on the Account object was previously omitted for accounts using Stripe’s shared SEPA Creditor Identifier. It now returns the shared identifier value. If your code relies on an omitted value to infer that an account uses the shared identifier, you must update your integration to handle the new response.

Impact

If your integration checks whether sepa_debit_payments.creditor_id is null or undefined to determine whether an account uses a shared SEPA Creditor Identifier, update that logic. This property now returns the shared identifier value.

Changes

ParameterChangeResources or endpoints
sepa_debit_paymentsAdded
Account#create.settingsV2.Core.Account#create.configuration.merchantV2.Core.Account#update.configuration.merchant

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: 2026-09-30.endive
  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.

Learn more about Stripe API upgrades.

Related changes

  • Adds address validation errors for CMRAs and registered agents to Accounts v1 and Accounts v2
  • Adds rejected status for Accounts v2 capabilities
  • Replaces the generic fraud rejection reason with specific fraud reasons
  • Removes the configurations parameter from the Account Links v2 API
  • Shows errors for eventually due requirements
  • Distinguishes platform-initiated account rejections from Stripe rejections
  • Adds additional shared fields to customer sharing
Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Chat with Stripe developers on Discord.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc
On this page