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 States)
HomeDeveloper resourcesChangelogClover2025-10-29.preview

Adds the ability to attest to the authorized company representative for Accounts v2Public preview

What’s new

You can now record the attestation of an authorized company representative for a Stripe account by specifying these parameters for identity.attestations when using Accounts v2:

  • representative_declaration.ip for the originating IP address of the attestation
  • representative_declaration.date for the date of the attestation
  • representative_declaration.user_agent for the user agent used for the attestation

Impact

A representative is the singular person designated by a business to manage their Stripe account. They are identified by setting the identity.individual.relationship.representative field.

In certain countries, Stripe is required to collect and verify that the representative’s information matches government records. When an account is created, the representative should be set to whoever is responsible for managing the account.

Accounts that require the attestation of a company’s representative will see identity.attestations.representatives_declaration.ip and identity.attestations.representatives_declaration.date in their requirements field.

Command Line
cURL
No results
curl -X POST https://api.stripe.com/v2/core/accounts/{{CONNECTED_STRIPE_ACCOUNT_ID}}/ \ -H "Authorization: Bearer
sk_test_BQokikJOvBiI2HlWgH4olfQ2
"
\ -H "Stripe-Version: {{STRIPE_API_VERSION}}" \ --json '{ "include": [ "identity" ], "identity": { "attestations": { "representative_declaration": { "ip": "67.180.161.149", "date": 1737936000, "user_agent": "Mozilla/5.0 (platform; rv:gecko-version) Gecko/gecko-trail Firefox/firefox-version" } } } }'

Changes

ParameterChangeResources or endpoints
representative_declarationAdded
V2.Core.Account#create.identity.attestationsV2.Core.Account#update.identity.attestationsV2.Core.Account.identity.attestations

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-10-29.preview
  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 new error code for missing verification data from connected accounts
  • Adds support for using Accounts v2 payment method billing details for Stripe Tax location
  • Adds support for retrieving and listing closed v2 Accounts
Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc