June 2026 Summaries

Involuntary churn occurs when otherwise willing subscription customers lose access because payments fail, unlike voluntary churn, which reflects a deliberate cancellation due to dissatisfaction or changing needs. Common causes include expired or reissued cards, insufficient funds, bank declines, card limits, and hard or soft declines, with soft declines often suitable for retry attempts while hard declines generally are not. The passage argues that merchants can reduce these losses by retaining control of payment data and using multiple payment processors to retry eligible failed transactions, automated account-updater services to refresh stored card credentials, and BIN intelligence to identify potentially unsuitable card types such as prepaid cards before enrollment. It also highlights network tokens, which can remain current when underlying cards change, and presents the combination of retries, card updates, and card-type intelligence as a strategy for improving authorization rates and protecting recurring revenue.

A multi-payment gateway strategy uses more than one payment service provider to route transactions, helping merchants improve authorization rates, lower processing costs through least-cost routing, offer additional payment methods, expand internationally, and maintain continuity during provider outages. It is most relevant for businesses with high transaction volumes, recurring revenue, high-risk profiles, time-sensitive sales, or a need for differentiated checkout experiences, while smaller merchants may see limited benefit. Key implementation challenges include PSP-specific payment tokens that can lock card data into a single provider and the operational complexity of building routing, retry, analytics, and orchestration logic. The text recommends independently controlling cardholder data through a merchant-managed or vendor-agnostic payment vault, enabling processors to be added or replaced without customer disruption. Examples involving Maxio, Marble, and YouPay describe using an independent tokenization layer to support geographic expansion, securely route payments to partners, reduce compliance burdens, and shorten processor integration times.

Data tokenization replaces sensitive values such as credit card numbers, personal information, files, or images with non-sensitive digital identifiers while storing the original encrypted data in a secure token vault. Unlike encryption alone, tokenization enables organizations to use tokens across applications, databases, processors, partners, and devices without broadly exposing plaintext data or expanding compliance obligations such as PCI requirements. Tokenization vendors provide compliant infrastructure, access controls, APIs, developer tools, encryption and key-management services, global redundancy, and support for evolving data-residency rules, helping merchants address security, regulatory, and operational complexity. Effective platforms keep sensitive data out of downstream systems, give merchants ownership and portability of tokens, avoid creating payment-path single points of failure, and support capabilities such as masking, aliases, metadata tagging, fingerprinting, authorization controls, and searchable encrypted datasets. Common uses include processor-independent payment routing, lower-cost payment optimization, controlled sharing of confidential data, embedded-finance clearinghouses, and e-commerce payments using existing cards on file.

May’s updates introduce self-service merchant onboarding, expanded Stripe wallet migration, and several token vault improvements. Customers can now create Merchants and enroll in Account Updater and Network Token services directly through the Customer Portal, with per-network status tracking and support for multiple independent merchant configurations under one tenant. The Stripe Forwarding API now migrates Apple Pay and Google Pay device payment account numbers as corresponding wallet resources, allowing merchants to move wallet credentials alongside card tokens without file exports or associated Stripe risk reviews. Network Token provisioning can now include expiration details inline when legacy card tokens lack them, while card data responses also provide product codes. In addition, Token Intents now accept client-side encrypted card payloads, enabling browser-based encryption, validation, and persistent token creation without exposing plaintext card data to backend systems.

Branded credit and debit cards enable airlines, retailers, and fintech companies to strengthen customer loyalty, gain a larger share of consumer spending, and create revenue through interchange fees, interest, annual fees, or the sale of loyalty points to issuing banks. Airlines commonly generate revenue by selling miles to banks, while retailers may share merchant fees and interest income; banks can still benefit because co-branded cards often carry higher interest rates and fees. Consumers can receive rewards such as miles, cash back, discounts, and targeted offers, though those carrying balances may face higher borrowing costs. Fintechs can provide cards linked to expense management, stored funds, or other financial services without becoming banks by relying on partner banks and card networks for processing, compliance, and account infrastructure. Card programs also yield detailed purchasing data that can support personalized marketing and, in anonymized form, advertising uses, but they require careful handling of personal information under PCI-DSS requirements. Many issuers reduce security obligations and PCI compliance scope by using third-party tokenization vaults to collect and store sensitive customer and card data.

BIN intelligence expands traditional card identification data, such as issuer, brand, country, and debit or credit classification, with operational attributes that help payment teams determine how a credential should be authenticated, routed, processed, and managed. These signals can include prepaid and reloadable status, Strong Customer Authentication and PSD2 requirements, Account Updater participation, alternative debit networks, co-badging, token versus PAN status, domestic restrictions, interchange characteristics, and Level 2 or Level 3 eligibility. Used before authorization, this information can support higher approval rates, fewer unnecessary authentication challenges, improved subscription retention, more effective retry and credential-lifecycle strategies, resilient multi-processor routing, and lower processing costs. Basis Theory presents its offering as BIN enrichment built for modern 8-digit BINs and integrated directly with vaulted payment credentials, allowing intelligence to remain available for payment routing, recurring billing, fraud decisions, reporting, reconciliation, and other optimization activities without separate lookups or infrastructure.

Chargebacks occur when a consumer asks a bank or card network to reverse a card purchase, forcing merchants to lose the transaction funds, processing fees, and often additional chargeback or dispute fees. They may result from genuine card fraud, “friendly fraud,” poor customer service, confusing billing practices, or transaction errors, and merchants generally have limited time and relatively low odds of successfully disputing them. Card networks and payment service providers monitor merchants’ monthly chargeback ratios, with penalties ranging from added fees and delayed payouts to account closure when thresholds are exceeded; maintaining a rate below 0.3% is presented as a prudent target. Merchants can reduce chargebacks through transparent pricing and descriptors, accessible refund and support processes, fraud-prevention tools, accurate billing, and local payment processing. To manage unavoidable disputes, businesses may maintain thorough records, diversify products and processors, use transaction-routing systems to balance risk across providers, and adopt payment vaults to reduce dependence on a single processor.

Basis Theory has updated its BIN data service to retain and aggregate BIN information observed over the past 18 months rather than relying solely on monthly card-network snapshots, reducing gaps when BINs are temporarily removed or re-added. The company says the change yields more complete BIN details, fewer missing-data responses, and response times of about 2 milliseconds instead of 10 milliseconds by querying databases directly rather than using an intermediate file. Real-time BIN details are now available during card vaulting, helping merchants assess card characteristics such as prepaid status, issuer country, and card type when making acceptance, fraud, subscription, and payment-routing decisions. The new architecture is also intended to support future regional and issuer-specific BIN intelligence, supplementing globally sourced network data with more localized card information.

Payment vaults are third-party tokenization systems that securely collect and store customer payment details as non-reversible tokens, helping SaaS businesses support recurring billing, saved payment methods, and multiple payment processors while reducing exposure to sensitive data and PCI-DSS compliance burdens. Merchants can alternatively rely on a single payment service provider’s proprietary vault, build their own vault, or use card-network tokens, but these approaches may create vendor lock-in, increase compliance scope, or limit flexibility across processors. Although an independent vault is not always necessary for early-stage businesses using one processor, it can become increasingly valuable as companies scale and seek to improve transaction success rates, manage costs, and reduce operational risk through multi-processor routing. Key considerations include implementation effort, ownership and portability of payment data, PCI-DSS security standards, integration capabilities, uptime guarantees, and contingency routing during outages. The source presents Basis Theory as a provider designed to give vertical SaaS and fintech platforms control over their credentials and processor connections.

Omnichannel tokenization is presented as a way for subscription merchants to reduce involuntary customer churn caused by failed recurring payments, such as expired cards, soft declines, or processor-specific approval issues. It stores payment credentials in a secure third-party, processor-agnostic vault while merchants retain non-reversible tokens that can be used only by the authorized merchant to initiate transactions, allowing them to route charges among payment processors without handling sensitive card data directly. Unlike payment service provider tokenization, which confines merchants to one provider, and card-network tokenization, which can require managing differing network standards, omnichannel tokenization is designed to support flexible processor selection, retries, and payment-partner changes. By keeping clear-text cardholder information outside their own systems, merchants can also reduce the scope, cost, and operational complexity of PCI-DSS compliance while limiting the potential exposure of customer payment data in a breach.