March 2025 Changelog

Apple Pay

We’ve improved the process of accepting Apple Pay payments by integrating DPANs directly into Basis Theory. No longer does custom code need to be used to decrypt these Apple Pay tokens. With this update, DPANs will automatically turn into Token Intents. We are also working on exposing MPAN functionality and will integrate that soon.

This implementation leverages the latest version of Apple Pay, which automatically works on all browsers. It allows iPhone users to scan a code and pay via phone.

Learn more about the integration with Apple Pay in our docs.

Web Elements API Request Speed Improvements

We also improved the speed of Web Elements API requests, reducing latency for all requests by 50%. This change removes unnecessary calls to the Basis Theory API from Elements, creating a faster experience for merchants and consumers.

Upgrade to the latest version of web-elements or react-elements to take advantage of these improvements. The old basis-theory-js or basis-theory-react implementations will not see this speed improvement.

3DS Improvements

Improved Documentation

New comprehensive guides are available to assist developers throughout the 3DS authentication process. Documentation now covers detailed setup instructions, recommended implementation values per use case, and guidelines on launching 3DS with your provider's results. The API reference has also been revamped with exhaustive field descriptions and practical code examples utilizing all Basis Theory backend SDKs.

Requestor Info Automation

Requestor information fields required for 3DS authentication, previously managed by customers and varying by card brand, are now automatically populated. Customers only need to supply additional values when supporting specific card networks (AMEX, Cartes Bancaires, Discover). The URL property has also been relocated to the merchant information object, simplifying configuration for customers that don't support those specific networks.

Improved Error Handling

All 3DS endpoints now consistently return standardized HTTP 424 status codes for errors originating from the various 3DS components - 3DS server, access control server (ACS), and directory server (DS). Error responses detail the origin and original status code and provide clear, descriptive messaging.

Additional Authentication and Challenge Result Response Properties

New properties, including directory status code and liability shift indicators, have been added to authentication and challenge responses to comply with PSP requirements for external 3DS data.

Bugs and Other Fixes

• [Node SDK] Fetch not loading in Node 18.x
• [3DS] Add New Status Reasons Codes
• [3DS] Added Liability Shifted Field
• [Elements] Better logging options for API requests
• [Elements] Optimized init to reduce elements added to DOM on subsequent calls.
• [React Elements] Add React 19 peer dependency
• [React Native Elements] Improve cvc length validation