Skip to content

    October 2026 Changelog

    October 2026 Changelog

    The node-bt runtime for Reactors and Proxy code transforms is being retired. Node.js runtime images (node22 and node24) provide current Node.js versions , stronger isolation, access to any npm package, and runtime logs. New runtime features ship only on those images.

    Since Oct. 5, 2026, new Reactors and Proxy code transforms have had to use node22 or node24.

    Starting Dec. 1, 2026, the remaining exceptions end, and no tenant can create a node-bt Reactor or Proxy code transform. That includes create requests that leave the runtime image unset, because an unset image defaults to node-bt. Those requests return a validation error.

    Existing node-bt resources keep running until the invocation cutoff, and you can still update, read, and delete them until then. On Feb. 1, 2027, node-bt stops running in test tenants. On March 1, 2027, it stops running in production tenants. After those dates, invoking a node-bt Reactor, or sending a request through a Proxy with a node-bt code transform, returns 403 Forbidden.

    Action Required Before Feb. 1, 2027

    1. Find your node-bt resources through the API by checking runtime.image on each Reactor and options.runtime.image on each Proxy code transform. An image of node-bt, or a missing or empty image, means the resource runs on node-bt.
    2. Update any deployment pipeline or Terraform configuration that creates these resources so it sets node22 or node24 explicitly before Dec. 1, 2026.
    3. Create a replacement for each resource on node22 or node24, test it, and move traffic once it passes. Keep the original in place so you can roll back. Start with your test tenants, then finish production before March 1, 2027.

    Follow the Migrate from node-bt guide for each step, and see the runtime comparison for every difference between the runtimes. If you have a business-critical reason to need more time, contact your account team before Dec. 1, 2026.

    Return to Top

    Run 3D Secure Natively in React Native Apps 

    Requires @basis-theory/react-native-threeds 1.3.0 or later.

    You can now run 3D Secure authentication in React Native apps through the native iOS and Android 3DS SDKs instead of a hidden WebView. Authentications from your app carry native app device signals, and shoppers see their bank's native challenge screen.

    Once you enable native 3DS, BasisTheoryThreeDS exposes configure, createSession, and startAuthentication. The platform SDK calls your authentication endpoint, presents the challenge when the bank requires one, and returns the result, with no provider component needed. Native 3DS requires React Native 0.81 or later and iOS 15 or later. It runs custom native code, so Expo apps need a development build; Expo Go supports only the WebView integration.

    Why This Matters

    1. Issuers see app traffic as app traffic, so authentications follow the mobile flow they expect instead of a browser flow.
    2. Shoppers complete challenges in their bank's native screen, which removes the WebView rendering problems that could leave a challenge stuck until it timed out.

    Learn more in the React Native 3DS documentation.

    Return to Top

    Keep EU Traffic Flowing With Regional Endpoints 

    You can now call the API through a dedicated endpoint for your tenant's region:

    • https://api.eu.basistheory.com for EU production tenants. 

    • https://api.us.basistheory.com for US production tenants. 

    Regional endpoints stay reachable when we bypass our edge network to restore service during an outage.

    Under normal operation, the shared https://api.basistheory.com endpoint uses a routing layer in our edge network to find your tenant's region. If that edge network is bypassed, all traffic to the shared endpoint goes to the United States, and EU requests fail until regional routing returns. Regional endpoints name the destination region directly, so they don't depend on that routing step. They use the same API, the same keys, and the same data.

    EU production tenants should move to https://api.eu.basistheory.com now, by setting the base URL or selecting the EU region in your SDK. US tenants aren't affected by this failure mode, but moving to https://api.us.basistheory.com removes the routing dependency entirely. Test tenants should use https://api.test.basistheory.com.

    The shared endpoint remains available for existing integrations, and SDK defaults don't change, so your endpoint changes only when you configure it. 

    Why This Matters

    1. EU integrations keep working during an edge-network incident instead of failing until routing is restored.
    2. Regional routing becomes an explicit setting in your integration rather than a dependency inside our network.

    The documentation lists the minimum version for each SDK and shows the configuration option for each one. Configure each SDK and migrate an existing integration, as outlined in the Regional Endpoints documentation.

    Return to Top

    Identify the Card Product Behind a Network Token 

    You can now see the network's own description of the card product behind a provisioned Network Token. That includes American Express products such as Platinum, which BIN (Bank Identification Number) data can't tell apart.

    The Get a Network Token Account response returns short_description and long_description alongside the existing card art. BIN-derived product codes can distinguish products like Visa Signature or Mastercard World Elite, but they report every American Express card as consumer or corporate. The network-supplied description fills that gap.

    Both fields are optional for every network: treat a missing or empty description as an unknown product, not as a sign that the card isn't a premium tier.

    Why This Matters

    1. You can route payments or apply card-specific promotions based on the exact product a shopper is paying with.
    2. American Express tiers become identifiable through a documented field instead of guesswork.


    Learn more in the card product identification documentation.

    Return to Top

    Make v3 Elements Match Your Checkout Fonts 

    You can now make v3 Web Elements match the rest of your checkout: your own fonts, your own field heights, and a card display that follows your theme.

    Element fields render inside iframes, and an iframe can't use the fonts your page loads, so fields used to fall back to the device's system font. Pass your web font files in the new fonts option on BasisTheory() and name the same family in typography.fontFamily. The fields then render in your brand font, including Google Fonts. Each font accepts a WOFF2, WOFF, TrueType, or OpenType file under 1 MB, and the SDK logs a specific warning for each reason a font fails to load.

    Field height is now a theme setting too: set sizing.input.height, and every input renders at exactly that height, instead of the card number field never rendering shorter than 48px.

    The cardDisplay element now uses your theme's font, background, and accent color. Amex and Diners Club numbers are grouped the way they're printed on the card. For co-badged cards in manual mode, the built-in network selector also gets its own theme controls for the panel, border, shadow, and option rows. It stays fully visible when opened and no longer closes while the shopper is still typing.

    Selector styling is available on request; contact your account team to enable it for your tenant.

    Why This Matters

    1. Your card fields look like part of your checkout instead of a separate form dropped into the page.
    2. Teams moving to v3 keep the typography and sizing they had before without workarounds.


    Learn more in the v3 theming documentation and the co-badge documentation.

    Return to Top

    Search and Tail Your Reactor and Proxy Logs 

    You can now search, filter, and follow the runtime logs your Reactors and Proxy code transforms write from the Customer Portal, the Basis Theory CLI, or the API.

    In the Portal, open a Reactor or Proxy and select Logs beside Configuration. Search history by time range and by words in the log message, and filter by trace ID, severity, platform event, outcome, and, for Proxies, request or response transform. A live view shows new entries as they're indexed. Message search matches records whose own message contains every word you enter, so a few remembered words are enough to find the line that explains a failure.

    Version 5.0.0 of the CLI brings the same search to your terminal. bt reactors logs read and bt proxies logs read return past logs, and logs tail follows new ones. Both accept --message-search, --level, and --trace-id, and Proxy commands also accept --transform-type.

    Interactive tail sessions ask to continue every 60 minutes. From your own code, the List Reactor Logs and List Proxy Logs endpoints offer the same filters with cursor pagination. Every method requires the log:read permission, and history is limited by your tenant's Log Retention quota.

    Runtime logs are available on Node.js runtime images.

    Why This Matters

    1. You can debug a failed invocation or transform yourself, without reproducing the call or opening a support request.
    2. One set of filters works across the Portal, the CLI, and the API, so you can move between them without relearning anything.

    Learn more in the runtime logs documentation.

    Return to Top

    Improvements 

    Apple Pay: List Merchant Registrations and Certificates

    You can now list your Apple Pay merchant registrations with GET /apple-pay/merchant-registration, and the certificates stored under each one with GET /apple-pay/merchant-registration/{merchantId}/certificates, including fingerprints and expiration dates. Results are paginated, expired certificates are included so you can find records to rotate or delete, and both endpoints require a Management application with apple-pay: manage.

    See the Apple Pay API reference documentation.

    3D Secure: Test Cards That Work in Your Processor's Sandbox

    You can now test a complete authenticate-then-authorize flow in sandbox with published card numbers that are valid both for Basis Theory 3DS and in the sandboxes of Stripe, Adyen, Shift4, Checkout.com, and Nuvei. They cover frictionless, challenge, and failure outcomes.

    See: Payment Provider Test Cards.

    Platform: Tenants Have a Default Limit of 30 Applications

    Each tenant can now have up to 30 applications by default. A successful POST /applications response includes remaining_applications, and requests past the limit return a 400. If you create one application per merchant, use sessions instead, or request a higher limit from your tenant's Quotas page.

    See: Other Limits.

    Portal: Configure Bank Verification and BIN Enrichment in Test Tenants

    You can now set the bank account verification mode, the BIN enrichment level, and the allowed test card numbers for a test tenant yourself under Settings → Quotas, without a support request. These settings stay fixed for production tenants.

    Proxy: Destination Status in Response Transforms and Clearer Detokenization Errors

    Response transforms now receive the destination's HTTP status in the BT-PROXY-DESTINATION-STATUS header, so your code can tell a 200 apart from a 202 or 204 with an empty body (docs). When a detokenization expression can't be resolved, the error response now lists the failing token and token intent values in proxy_error.invalid_values.

    Reactors: callback_url Removed From Synchronous Invocation

    POST /reactors/{id}/react no longer accepts callback_url. If you still send it, switch those calls to asynchronous Reactor invocation and resolve the returned request to read the result.

    iOS Elements: Smaller CocoaPods Install

    The CocoaPods integration for iOS Elements no longer pulls in the unused Basis Theory API client, reducing the bundle size from about 2.2 MiB to about 847 KiB. If your app imports the API client directly, add pod 'BasisTheory' to your Podfile when you upgrade. Requires BasisTheoryElements 6.0.0 or later.

    Return to Top

    Stay Connected

    Receive the latest updates straight to your inbox