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 Shell
Stripe for Visual Studio Code
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 resourcesChangelogClover2025-12-15.clover

Accounts now support digital attestation for proof of registration and beneficial ownership verification

What’s new

Adds support for digital attestation to the Accounts API when uploading documents for proof of registration and ultimate beneficial ownership verification. You can now specify the person who electronically signed the document using the following parameters:

  • documents.proof_of_registration.signer.person: ID of the Person who electronically signed the proof of registration document
  • documents.proof_of_ultimate_beneficial_ownership.signer.person: ID of the Person who electronically signed the proof of ultimate beneficial ownership document

These parameters are available when you create an Account or update an existing Account.

Impact

You can now provide digital attestation for proof of registration and ultimate beneficial ownership verification. Digital attestation allows authorised signers to electronically sign attestation agreements as an alternative to uploading physical documents. This streamlines the onboarding process for European compliance requirements while maintaining the same level of verification.

If you use this feature, make sure the person specified in the signer.person parameter has the proper authorisation to sign on behalf of the business, and their first_name and last_name are set.

Changes

ParameterChangeResources or endpoints
signerAdded
Account#create.documents.proof_of_registrationAccount#create.documents.proof_of_ultimate_beneficial_ownershipAccount#update.documents.proof_of_registration
 + 1 more
Account#update.documents.proof_of_ultimate_beneficial_ownership

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: 2025-12-15.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

  • Connect platforms can now use Accounts v2 to manage connected accounts and customers
  • Adds the customer account property to v1 APIs for Accounts v2 interoperability
Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc