Spreedly vs Basis Theory for Merchant Network Tokenization

When evaluating Spreedly vs Basis Theory network tokenization, the surface similarity hides a meaningful architectural difference. Both platforms sit in front of your card data and hand you a token, but Spreedly was built to route payments across processors and treats network token provisioning as part of that routing job. Basis Theory was built as a programmable PCI-scoped vault, and network tokens are one output you can configure from it. The decision turns on which problem you are actually solving.


What Is the Actual Difference Between a Vault Token and a Network Token?

A vault token is a pointer. It maps to a stored PAN inside a tokenization vault, and your processor receives the actual card number when it needs to charge the card. The PAN leaves your infrastructure but it still travels through the payment chain in its original form.

A network token is different in kind. Visa, Mastercard, and American Express issue network tokens directly. They replace the PAN with a scheme-level credential that is bound to a specific merchant or payment requestor. When a network token reaches an issuer, the issuer validates both the token and a cryptogram generated for that transaction. The raw PAN never travels.

This distinction has real consequences. Network tokens typically yield higher authorization rates on recurring transactions because issuers recognize the credential as lower risk. Card-on-file transactions using network tokens also benefit from automatic account updates when a card is reissued, reducing involuntary churn without requiring a separate account updater service. For a subscription business with meaningful card-on-file volume, the revenue impact of that lifecycle management is not abstract.


How Does Spreedly Approach Network Token Provisioning?

spreedly

Spreedly is primarily a payment orchestration platform. Its architecture centers on a universal card vault that lets merchants route a single stored credential across multiple payment processors without re-vaulting card data with each processor. Network token provisioning in Spreedly plugs into that routing layer. When Spreedly holds a PAN in its vault, it can provision a Visa or Mastercard network token on behalf of the merchant and use that token when routing to a supported gateway.

The practical advantage is tight coupling between token lifecycle and routing decisions. When a card is reissued and the network token updates, Spreedly’s routing layer sees the update and can pass the refreshed credential downstream without merchant-side intervention. For teams already using Spreedly for multi-gateway routing, this is a low-friction path to network token benefits.

The constraint is architectural lock-in by design. Spreedly’s vault is the linchpin. If you want to send a network token to a processor outside Spreedly’s supported gateway list, or pull raw card data to a new processor during a migration, you are working against the grain of the platform. Payment orchestration platform selection always involves trading portability in one dimension for convenience in another, and Spreedly is no different.


How Does Basis Theory Approach Network Token Provisioning?

basis theory

Basis Theory starts from the opposite architectural assumption. Its core product is a programmable vault that holds any sensitive data, PAN or otherwise, in a PCI-scoped environment and exposes that data through a token and a permissions model you define. Network token provisioning is a capability layered on top of that vault, not the reason the vault exists.

What that means operationally: Basis Theory can provision network tokens for Visa and Mastercard, and merchants can configure how and when those tokens are requested. But the platform also supports forwarding raw PANs to processors that do not accept network tokens, or mixing both credential types in the same workflow. The vault itself does not impose a routing model.

The architectural bet in Basis Theory is that the vault should be processor-agnostic, and that merchants should control how card data exits the vault on a per-transaction or per-processor basis. As covered in the adjacent comparison on Basis Theory versus Very Good Security, this programmability is the platform’s defining characteristic and also the source of its integration complexity.


What Does Token Lifecycle Management Actually Require?

Token lifecycle management covers four distinct jobs: initial provisioning, cryptogram generation for each transaction, account updater integration when a card is reissued, and token suspension or deletion when a cardholder removes a payment method. Each job has different latency and reliability requirements.

Spreedly handles cryptogram generation inline with its routing layer, which means the cryptogram is produced as part of the payment request rather than as a separate API call. For teams that want to minimize integration surface, this is a meaningful simplification. Basis Theory requires you to call their reactor or proxy layer to generate a cryptogram before passing the transaction to your processor, which adds an integration step but also gives you more control over how that credential is used.

Account updater behavior is worth examining directly with each vendor during evaluation. Both platforms can connect to network-level account updater services, but the degree to which updates propagate automatically versus requiring explicit polling or webhook handling differs. For subscription businesses processing recurring charges against card-on-file credentials, this detail directly affects involuntary churn rates.


Network Token Portability Matrix: Where Each Platform Stands

The FintechSpecs Network Token Portability Matrix below evaluates both platforms across five dimensions that matter most to merchant payments teams. These reflect the practical questions a team faces when choosing a vault architecture, not abstract feature checklists.

DimensionSpreedlyBasis Theory
Network token provisioning (Visa, Mastercard)Supported, coupled to routing layerSupported, configured per reactor/proxy
Processor portability with same network tokenLimited to Spreedly-supported gatewaysBroad, processor-agnostic forwarding
PAN fallback for non-supporting processorsSupported within Spreedly routingSupported via proxy forwarding rules
Cryptogram generation modelInline with payment routing requestExplicit call to reactor/proxy layer
Vault portability (export or migrate PANs)Restricted by designPermitted with appropriate permissions, per Basis Theory’s documentation
Integration complexity for first network tokenLower for teams already on SpreedlyHigher initial setup, more flexible long-term
Public pricing disclosure (as of this writing)Not publicly disclosedNot publicly disclosed

Which Merchants Should Choose Spreedly for Network Tokenization?

Spreedly fits best when multi-gateway routing is the primary infrastructure problem and network token support is a secondary requirement. A merchant that processes across Braintree, Stripe, and an acquiring bank for redundancy or cost optimization already needs a vault layer to avoid re-vaulting card data per processor. Adding network token provisioning inside that same layer is a natural extension, not an added integration.

Consider a Series B e-commerce company processing across two or three gateways with a mix of one-time and recurring billing. Their engineering team wants to route by cost and availability without touching stored card credentials. Spreedly’s coupling of vault, routing, and network token provisioning gives them all three in a single vendor relationship. The trade-off is that if they later want to move processors entirely, the vault portability question becomes a migration challenge rather than a configuration change.

Spreedly also suits teams that want a managed experience over a programmable one. The platform makes opinionated decisions about how tokens are provisioned and used. For many teams, that is a feature.


Which Merchants Should Choose Basis Theory for Network Tokenization?

Basis Theory fits best when vault architecture flexibility and long-term processor independence matter more than out-of-the-box routing convenience. A platform that expects to change processors, add new payment methods, or build custom payment logic on top of its vault benefits from Basis Theory’s separation of concerns.

Say a growth-stage payments infrastructure company needs to store card data for multiple downstream merchants, each of whom uses different processors. Basis Theory’s vault can hold those credentials and forward them to any processor endpoint using configurable proxy rules. Network tokens can be provisioned and routed to supported processors. For processors that do not support network tokens, the same vault can forward the raw PAN through an isolated proxy path. No single processor or routing model owns the vault.

The cost of that flexibility is real integration work. Basis Theory’s reactor and proxy model requires engineering time to configure, test, and maintain. Teams without dedicated payments infrastructure engineers often find the initial setup more demanding than expected. This is the same trade-off that appears across programmable infrastructure choices throughout the fintech infrastructure stack: more control requires more implementation work.


How Does Merchant Card Vault Portability Differ Between the Two?

Vault portability, meaning your ability to retrieve or export stored PANs if you leave the platform, is one of the most consequential and least-discussed differences between the two products.

Spreedly’s vault is designed to decouple card data from processor relationships, which is valuable. But retrieving raw PANs from Spreedly to migrate to a new vault or processor is not a self-service operation. This is by design: a vault that makes raw PANs easy to export is also a vault that creates PCI scope exposure. Teams that sign with Spreedly are implicitly accepting that the vault relationship has switching costs.

Basis Theory takes a different position. The platform is built on the premise that you own your data, and it supports programmatic access to vault contents, subject to PCI-compliant access controls and audit logging. Exporting PANs for a processor migration, or using vault data in a new context, is a permissions configuration rather than a vendor negotiation. For teams worried about infrastructure lock-in, this matters. Picking the wrong vault architecture early is one of the critical mistakes in fintech infrastructure decisions that becomes expensive only when you need to undo it.


What Are the PCI Scope Implications of Each Approach?

Both platforms reduce PCI scope for merchants by holding PANs in a compliant vault and returning a token. The scope implications diverge when you look at how each platform exits data from the vault.

Spreedly’s proxy model routes payment credentials to processors without PANs transiting the merchant’s servers. This is a standard tokenization architecture and results in a reduced SAQ-D or SAQ-A-EP scope depending on your integration method. Basis Theory takes a similar approach with its proxy and reactor model, and both platforms publish documentation supporting PCI DSS compliance assertions.

The nuance is in custom integrations. Basis Theory’s programmability means that a misconfigured reactor could inadvertently route PAN data through an endpoint that expands scope. Spreedly’s more constrained routing model reduces the surface area for that kind of configuration error. Teams with less PCI experience may find Spreedly’s guardrails protective rather than limiting. For a full review of PCI tooling considerations, the PCI DSS compliance tools comparison covers the broader tooling considerations.


Frequently Asked Questions

Can you use network tokens on Basis Theory without also using Spreedly?

Yes. Basis Theory provisions network tokens independently of Spreedly. The two platforms are not related and do not share infrastructure. Basis Theory connects to Visa Token Service and Mastercard Digital Enablement Service directly, and merchants configure network token provisioning through Basis Theory’s vault and proxy layer. Spreedly is a separate company with its own vault and network token provisioning pipeline. Teams should evaluate them as independent options, not as complementary products.

Does Spreedly support network token provisioning for all major card networks?

According to Spreedly’s public documentation, the platform supports network token provisioning for Visa and Mastercard. American Express operates a separate tokenization program with different provisioning requirements and not all vault providers support it on the same timeline. Teams processing significant American Express volume should confirm current coverage directly with each vendor before selecting a platform, as network support can expand over time.

What happens to network tokens if you switch processors?

Network tokens are bound to a payment requestor token, which is tied to the entity that provisioned the token. If you switch processors, the original network token may not be transferable to the new processor without reprovisioning. This is a network-level constraint, not a Spreedly or Basis Theory constraint. The practical implication is that a vault migration and a network token reprovisioning event often coincide, creating a window of potential authorization friction. Planning this sequence is part of any serious processor migration.

How does network tokenization affect authorization rates for recurring billing?

Network tokens on recurring card-on-file transactions typically see higher authorization rates than raw PAN transactions because issuers treat the scheme-issued credential as a lower-risk signal. The token also benefits from automatic updates when a card is reissued, reducing declines from expired card data. The exact authorization rate improvement varies by issuer, card type, and transaction history. Neither Spreedly nor Basis Theory publishes proprietary authorization rate benchmarks for network token versus PAN transactions.

Is Basis Theory or Spreedly better for a SaaS platform with multiple sub-merchants?

Basis Theory is generally better suited to multi-merchant architectures because its vault permissions model can isolate card data by tenant, and its proxy forwarding can route to different processors per merchant without shared vault contamination. Spreedly’s routing model is designed around a single merchant relationship with multiple gateways, not a multi-merchant hierarchy. Platforms building embedded payments for sub-merchants should evaluate Basis Theory’s multi-tenant vault model and also look at PayFac-as-a-service infrastructure, as the vault layer is only one component of that architecture.

Do either Spreedly or Basis Theory publish their network token provisioning pricing?

Neither Spreedly nor Basis Theory publicly discloses network token provisioning pricing as of their current pricing pages. Both platforms operate on enterprise or usage-based contracts that require direct engagement for pricing details. Teams should request itemized pricing for vault tokens, network token provisioning per card, cryptogram generation volume, and account updater calls separately, as these are typically billed as distinct line items in the contract.


Conclusion

The choice between Spreedly and Basis Theory for network tokenization is not about which platform provisions better tokens. At the network token level, both connect to Visa Token Service and Mastercard’s tokenization infrastructure. The real decision is about what sits around the token: a managed routing layer that owns the vault lifecycle, or a programmable vault where you define how token credentials flow to any processor.

Spreedly wins when the goal is simpler integration and your payment stack is already routing-centric. Basis Theory wins when you need vault portability, multi-processor flexibility, or the ability to control token usage logic at the code level. The teams most likely to regret their choice are those that pick Spreedly for its convenience and later discover they need vault portability, or those that pick Basis Theory for its flexibility and then underestimate the engineering investment required to realize it. Both failure modes are preventable with an honest scoping conversation before contract signature.

One last framing worth carrying into your evaluation: a vault token and a network token do not solve the same problem, and the platform that serves you best depends on which of those problems you are optimizing for first. If reducing PCI scope and gaining processor flexibility are the priorities, the vault architecture matters most. If improving authorization rates and reducing card-on-file churn are the priorities, the network token lifecycle management matters most. Most teams need both, but knowing which one is load-bearing in your architecture is the question that determines the right vendor. Teams building recurring payment infrastructure should also review the broader set of payment infrastructure tools for SaaS founders before narrowing to vault-layer decisions alone.

Sarah Whitmore
Sarah Whitmore

Sarah covers payment processing platforms and PayFac-as-a-service providers for FintechSpecs, digging into the residual splits and underwriting speed most vendors bury in the footnotes. She got interested in the space after watching a vertical SaaS company lose a deal over a five-day merchant onboarding delay, and she hasn't stopped asking vendors how fast is fast since.