Payments API and hosted checkout API
Both APIs are versioned in the URL path (/v1/...). A version stays stable for the fields and behavior documented here; additive changes (new optional fields, new enum values, new endpoints) ship within v1 without a version bump. A breaking change — removing a field, changing a field’s type, or changing default behavior — ships as a new path version, never as a silent change to v1.
Elements SDK
The Elements SDK follows semantic versioning (major.minor.patch). Pin to a specific version (or a major range once you’ve verified compatibility) rather than always loading latest, so an SDK release can’t change your integration’s behavior without your action. A pre-release version (for example a -beta.N suffix) may change before general availability — see the Beta notice on any Beta page.
Webhook payloads
Every webhook envelope carriespayload_version: "v1". This is independent of the Payments API path version — check payload_version, not the API version, if you branch on webhook payload shape.
Deprecation policy
RadiumOne’s deprecation notice period and SDK support window (how long an older major SDK version keeps receiving fixes after a new major ships) are still being finalized. Until then, contact support to check on the status of a specific deprecation.Track releases
The version table above reflects each product’s current status. Contact support for details on a specific release.Next steps
Go-live checklist
Confirm you’re ready before you switch a product’s integration to production.
Support
Ask about a specific version or deprecation timeline.