December 2025 Changelog

December brought meaningful updates to the Basis Theory Platform. Whether you're scaling Apple Pay across multiple storefronts, building better checkout experiences, or preparing your test environments for 2026, this month has something for you.

Bring Your Own Certificates for Apple Pay and Google Pay 

You can now manage your own merchant certificates for Apple Pay and Google Pay integrations instead of using Basis Theory-managed certificates.

This unlocks the following important capabilities:

• Migrate without disruption. If you already have Apple Pay or Google Pay set up with your own certificates, you no longer need to switch to Basis Theory-managed certs. Keep your existing integrations intact and reduce onboarding friction.
• Support more than 99 domains. Apple Pay limits shared certificates to 99 registered domains. By bringing your own certificates, you can register unlimited domains. This is essential for platforms, marketplaces, and businesses operating multiple storefronts.

The feature includes new API endpoints for certificate management, SDK support across all Basis Theory SDKs, and complete documentation for Apple Pay and Google Pay implementations.

Return to Top

Smarter BIN Lookups in Elements 

Elements now delivers more accurate BIN (Bank Identification Number) details as users type their card number, giving you real-time precision instead of static guesses.

Here's what changed: When the binLookup property is set to true, and a user enters the first six digits of their card number, Elements performs a lookup using those entered digits. Previously, we returned all matching BINs for those digits and kept that static list regardless of what the user typed next. Now, as additional digits are entered, we filter the results client-side to show only compatible BINs.

The result is more accurate card brand, card type, and issuer information displayed in real time.

Why this matters:

1. Better checkout experiences start with accurate card recognition. Your users see the right card brand and type as they type, which builds trust and reduces confusion.
2. For payment teams, accurate BIN data means better routing decisions. You can direct transactions to the right processor based on actual card details, not approximations.
3. This update also resolves EU co-branding card compliance, which requires merchants to allow customers to choose between card brands (e.g. Cartes Bancaires). Accurate, real-time BIN detection makes that selection process smoother.

Return to Top

Test Tenant Migration: Action Required by March 30, 2026 

We are making changes to how Test Tenants operate to provide you with better isolated testing resources. We're migrating all Test Tenants to a dedicated, isolated environment separate from production infrastructure.

This change offers better resource separation for testing, development, and load testing. It is important to us to ensure our customers have an exact environment of their Production tenants to test against, and this won’t change. Our Test tenants still follow the exact system requirements as they currently do, meaning they reflect the same responses and scaling as Production Tenants.

What's changing:

Your Test Tenant API calls will use a new endpoint: api.test.basistheory.com instead of api.basistheory.com. You'll also need to whitelist new IP addresses for third-party integrations: 18.191.73.1 and 52.13.142.52. Webhook signature verification will use a new signing key with the header BT-SIGNATURE-VERSION: v1-test.

What you need to do before March 30, 2026:

1. Update your Test Tenant API calls to use the new endpoint
2. Add the new IP addresses to your allowlists
3. Update webhook signature verification to handle the new header

Important: The Test Tenant environment is not PCI compliant. Do not store real or live consumer data in Test Tenants.

For the complete migration guide, including step-by-step instructions, visit our Test Tenant documentation.

Return to Top

Bug Fixes 

Fixed Card Editing Validation in Elements

We resolved an issue affecting card editing functionality across Web Elements, React, and React Native SDKs.

What was fixed:

When using the setValue function to populate card data for editing, the onChange event was not properly returning the proper complete validation state, and field validation was not triggered. This caused edited card fields to appear invalid even when valid token data was provided.

This fix ensures that when you pre-populate card Elements for editing:

• The onChange event now returns accurate field state.
• Validation runs automatically when setting values from a token.

Affected versions:

• Web Elements: 2.8.3
• React SDK: 2.8.3
• React Native SDK: 2.5.0