Clover
Clover is the third release in our new API versioning model. As the first version in the Clover release, 2025-09-30.
introduces both breaking changes and new features—subsequent Clover versions will include only additive changes. Our prior releases were Acacia and Basil: every time we introduce a breaking change version, we move to the next release.
September 30, 2025
The September release of Clover includes new features in our GA channel:
- New descriptions for risk verification requirements: The new descriptions provide more specific information about the status of accounts that undergo sanctions, PEP, and legal reviews.
- Updated behavior for Elements with Checkout Sessions: Elements now prevents you from reusing client secrets in cases that could lead to broken payment forms. And you no longer have to enable saved payment methods both on the Checkout Session and explicitly in your initialization call.
- Updated behavior for Checkout: Postal codes are no longer automatically collected in Canada, United Kingdom, and Puerto Rico. Details about Adaptive pricing are now found in presentment_details rather than the
currency_
field, which has been removed as of this release. Checkout’s initialization call,conversion initCheckout
, is now synchronous, which lets you mount Elements earlier, reducing latency. - Flexible billing mode is the new default: When you create Subscriptions with this GA version, the subscriptions default to flexible billing mode, which changes how those Subscriptions behave at different points in their lifecycle.
Our public preview channel also includes several updates:
- v2 Accounts no longer have platform-specific fields: Platform-specific properties have been removed from the the Accounts v2 object because they’re platform specific and not shareable across operational contexts.
- Smart Disputes recommended evidence fields restructured: We’ve changed the structure of the
recommended_
field to group relevant evidence fields together, making it easier to identify which evidence fields you have to provide together to use Smart Disputes.evidence
To get started with these updates, review the changelog and upgrade your API version.