Guide
API Compatibility and Versions
Match route contracts and package instructions to the integration you ship.
Check the whole integration
Legacy licensing aliases and /v1 routes coexist with newer developer and partner operations. A package version, route version, and public guide review date describe different things. Confirm the current authentication, request, response, and error contract before changing a client.
Generated configuration changes may require regeneration and a rebuilt release. Keep existing customer and device scenarios in your regression checks when updating package enforcement.
Evidence boundary
This guide describes the current implementation and package instructions. Source review does not certify every host, operating system, provider delivery, or payment lifecycle. Test the exact build and environment you intend to release.
The October review traced current mounted operations and expanded public guidance. It did not run all financial, provider, host, or endpoint fixture workflows. The operation map is route coverage, not a formal compatibility guarantee.