October 2024 Summaries

Network tokenization replaces sensitive card details, including the primary account number, expiration date, and CVV, with merchant- and network-specific tokens that can be used for current and future payments without exposing underlying account data. Unlike physical cards, network tokens can remain valid after card replacement or expiration, improving authorization rates, reducing fraud exposure and chargeback liability, and preventing disruptions to recurring payments. PSP-issued tokens similarly reduce merchants’ PCI responsibilities but are restricted to the issuing provider, while universal tokens from payment vaults offer greater portability across payment service providers and card networks. Although network tokens can be more portable than PSP tokens in principle, routing requirements and PSP implementations may still create vendor lock-in, potentially requiring customers to re-enter card details if a merchant changes providers. A token orchestration provider can combine network tokens with universal vault tokens, allowing merchants to retain security and authorization benefits while supporting multiple PSPs, protecting customer data, and preserving payment flexibility.

Basis Theory reports significant improvements to token creation and read performance, aimed at supporting latency requirements and maintaining a highly available environment. Average and p90 token creation times have been reduced by half, while maximum creation time is reportedly 10 times faster, benefiting both managed and self-service large token migrations by reducing the need for prolonged processing and retries. Planned work for the following quarter includes faster token creation for Enrichments as well as improved search and list performance in the API and portal. The update also addresses issues involving Proxy and Transform 502 responses, CVC retention during token updates, Proxy response transforms, React Native version compatibility, recently created session reads, masked null token properties, and incorrect American Express BIN-detail responses.

Chargebacks occur when cardholders ask issuers to reverse payments because of third-party fraud, friendly fraud, or merchant errors such as undelivered goods, misleading descriptions, or difficult refund procedures. They cost merchants revenue, inventory, and fees, and rising chargeback rates can trigger withheld funds, monitoring programs, fines, account termination, and loss of card-network access, with a ratio above 1% of transactions posing particular risk. Merchants can reduce avoidable disputes through robust payment verification, recognizable billing descriptors, transparent transaction and subscription terms, accessible customer service and refunds, charging only after shipment or delivery, delivery signatures for valuable orders, and analysis of chargeback reason codes to identify recurring problems. Using multiple payment service providers may further lower exposure by supporting local currencies and preferred payment methods, assigning higher-risk transactions to specialized processors, and distributing transaction volume so individual accounts remain below chargeback thresholds.

Merchants seeking to improve approval rates, reduce processing costs, and limit dependence on a single payment service provider can use multiple processors and route transactions according to business rules. Front-end switching selects a provider’s payment form before payment details are entered, usually based on customer factors such as location, but it offers limited routing flexibility, does not share stored credentials across providers, and cannot easily retry failed transactions through another processor. Back-end switching routes payment information after collection through internal systems, often using a programmable token vault that provides a consistent checkout interface while allowing merchants to retain tokenized access to customer payment data. This approach can support more detailed routing decisions based on geography, transaction size, payment type, merchant category, or provider commitments, as well as retries after soft declines and fallback options during service disruptions. The source argues that back-end switching can improve conversion, customer experience, cost control, and PCI-DSS compliance management, although it requires more sophisticated payment infrastructure and data-vaulting arrangements.