Skip to main content
​
March 2026

​
API Updates

  • Refunds are now supported via the API, including issuing and managing refunds.
  • Simplified Apple Pay integration flow
  • Increased rate limits

​
Details

Operators can now issue refunds and track their status directly through the API. Use create-refund to issue a refund, get-a-refund to retrieve details for an individual refund, and list-refunds to query all refunds.The Apple Pay integration has been simplified — operators now call authorize-payment directly with the Apple Pay token, removing the need for a separate tokenization step. See the updated Apple Pay guide for details.The API Concepts page now includes an environments section documenting sandbox and production base URLs. Rate limits have been increased and the window has been shortened to per-minute, giving operators higher throughput for bursty workloads.
​
February 2026

​
API Updates

  • New brand field returned on card objects in intent and user responses.

​
Details

A brand field is now included on card objects returned by get-intent, list-intents, get-user, and list-users endpoints. The field returns one of mastercard, visa, amex, or discover, enabling operators to display card brand information without maintaining their own BIN lookup.
​
January 2026

​
API Updates

  • New integration guides and restructured documentation.
  • Support for dynamic type assignment by omitting the type parameter in requests to the API
  • New tag field on the authorize-payment endpoint.

​
Details

The documentation has been completely refreshed with new step-by-step integration guides covering the full payment lifecycle. The previous hosted payment experience, card-only, and legacy integration guides have been retired and replaced with focused guides for each core workflow. See the welcome guide for an overview.The tag field on authorize-payment allows operators to supply an internal transaction record ID alongside the payment request for easier reconciliation.The type field on the create-user-url request body is now optional. Operators who wish to have the payment type determined dynamically from the card BIN and operator configuration can omit the parameter.
​
July 2025

​
API Updates

  • Deprecation of idempotency header for create-user and authorize-payment endpoints.

​
Details

X-Idempotency-Key is now deprecated for the create-user and authorize-payment endpoints. Developers can continue to submit requests with the parameter, but it will no longer be read or used in the de-duplication of requests.For more details on how our API idempotent request handling logic works, see our API Concepts guide.