Forward Compatibility

We change our APIs in a way that is both additive and backward-compatible, and the developers are expected to ensure forward compatibility for our future enhancements. Accordingly,

• We retain the right to extend our API in an additive manner.

• Additional or optional fields may be introduced to our API requests.

• Supplementary fields may be incorporated into our existing API responses and callbacks.

• Fields explicitly declared with enums may undergo extensions in the future, and integrators should be capable of handling newly introduced enum values, such as additional error codes or card brand names.

• We reserve the right to modify the length or format of opaque strings, such as error messages and human-readable strings; this includes the potential addition or removal of prefixes from identifiers generated by the API.