Skip to content
Create account or Sign in
The Stripe Docs logo
/
Ask AI
Create accountSign in
Get started
Payments
Revenue
Platforms and marketplaces
Money management
Developer resources
APIs & SDKsHelp
Overview
Versioning
Changelog
    Overview
    Clover
    Basil
    Acacia
    Previous versions
Upgrade your API version
Upgrade your SDK version
Essentials
SDKs
API
Testing
Stripe CLI
Sample projects
Tools
Stripe Dashboard
Workbench
Developers Dashboard
Stripe for Visual Studio Code
Terraform
Features
Workflows
Event Destinations
Stripe health alertsFile uploads
AI solutions
Agent toolkit
Model Context ProtocolBuild agentic AI SaaS Billing workflows
Security and privacy
Security
Stripebot web crawler
Privacy
Extend Stripe
Build Stripe apps
Use apps from Stripe
Partners
Partner ecosystem
Partner certification
United States
English (United Kingdom)
HomeDeveloper resourcesChangelogClover2026-02-25.clover

Adds display name and service user number to Bacs Direct Debit mandates

What’s new

Adds the display_name and service_user_number properties to the Mandate object for Bacs Direct Debit transactions. The display_name is the display name for the account on the mandate. The service_user_number is the service user number for the account on the mandate.

These properties provide information for Bacs Direct Debit transactions, helping platforms to manage custom branding across multiple connected accounts.

Impact

You can now access the display name and service user number for Bacs Direct Debit mandates. This information helps you provide better customer support by matching payments to the names customers see on their bank statements, and enables more detailed reconciliation and reporting for your Bacs Direct Debit transactions.

If you’re building customer-facing interfaces or reporting tools that display mandate information, you can now include these additional identification details to improve clarity and transparency.

Changes

ParametersChangeResources or endpoints
display_nameservice_user_numberAdded
Mandate.payment_method_details.bacs_debit

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-02-25.clover
  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 events for reserve holds, releases and plans
  • Adds transaction purpose to PaymentIntents for US bank account payments
  • Makes Boleto tax ID nullable in payment method details for Payment Records
Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc