Skip to content

    February 2026 Changelog

    February 2026 Changelog

    This month brings the public preview of the node-22 runtime for Reactors and Proxy Transforms, multi-merchant support for Account Updater and Network Tokens, and a batch of bug fixes across Elements, Vault, and Proxy.

    Multi-Merchant Support for Account Updater and Network Tokens

    You can now pass an optional merchant_id parameter to Account Updater and Network Token endpoints, enabling multiple merchant configurations within a single tenant.

    Previously, AU and NT operated at the tenant level with a single configuration per tenant. Customers with multiple merchants or business units—like payment facilitators managing sub-merchants—were forced to create separate tenants for each, duplicating API keys, proxies, and reactors.

    The new Merchant entity removes that limitation. Each merchant stores its own AU and NT configuration, and you reference it by passing merchant_id on real-time AU requests, batch AU CSV rows, and Network Token creation.

    If you omit merchant_id, the tenant-level configuration is used, maintaining full backward compatibility.

    Documentation is available for the updated https://developers.basistheory.com/docs/api/account-updater/ and https://developers.basistheory.com/docs/api/network-tokens/ endpoints.

    See the https://developers.basistheory.com/docs/concepts/what-are-tenant-merchants concept guide to understand how merchants work within your tenant and get started.

    2026 Offsite in Playa Del Carmen

    EngineersatChichenItza

    We weren't able to get our entire engineering team off the beach and to Chichén Itzá, but it was still an incredible experience seeing one of the Seven Wonders of the World in person! 

    Bug Fixes

    Proxy Response on 520 Errors

    Fixed an issue where Proxy returned an incorrect response when the destination server responded with a 520 status code. Proxy now correctly passes through the destination's response.

    Card Details Endpoint Ordering

    The /enrichments/card-details endpoint now returns data in a consistent order, resolving an issue where results were returned unordered.

    Token Intents Error Handling

    Fixed an ArgumentNullException that could occur when accessing /token-intents/{id} under certain conditions.

    Elements Loading Consistency

    Fixed an issue where Elements loaded inconsistently, causing intermittent initialization failures.

    Elements Autofill Styling on Dark Backgrounds

    Fixed autofill text color overriding theme styling on dark backgrounds, ensuring autofilled values respect your configured theme.

    Card Expiry Field Deletion

    Fixed an issue where users could not delete the value past the / separator when a Card Expire date had been fully entered.

    Card Icon Configuration in CardElement

    You can now disable or configure the card brand icon position in CardElement using iconPosition, matching the existing behavior available in CardNumberElement.

    CVC Masking Toggle

    CVC password masking is now toggleable, giving you control over whether the CVC field displays masked or visible input.

    Stay Connected

    Receive the latest updates straight to your inbox