---
title: Stop Paying for the Same Features Twice
description: When Account Updater, Network Tokens, 3DS, and BIN data live at the processor level, you're paying for them multiple times. Here's how to fix that.
image: https://blog.basistheory.com/hubfs/Stablecoins%20Narrowbanks.webp
---

[Skip to content](https://blog.basistheory.com/enrichments-native-to-vault#main-content)

![Basis Theory logo](https://blog.basistheory.com/hs-fs/hubfs/BTLogo%20(1).png?width=365&height=122&name=BTLogo%20(1).png)

- [Use Cases](https://basistheory.com/)
  
  Show submenu for Use Cases 
  
    - [Creator Economy](https://basistheory.com/use-cases/creator-economy)
    - [Digital Health](https://basistheory.com/use-cases/health)
    - [E-Commerce](https://basistheory.com/use-cases/ecommerce)
    - [Fintech](https://basistheory.com/use-cases/fintech)
    - [Gaming](https://basistheory.com/use-cases/gaming)
    - [Subscription Merchants](https://basistheory.com/use-cases/subscriptions)
    - [Travel](https://basistheory.com/use-cases/travel)
    - [VSaaS](https://basistheory.com/use-cases/vsaas)
- Solutions
  
  Show submenu for Solutions 
  
    - [Agentic Commerce](https://basistheory.com/solution/agentic-commerce)
    - [Data Consolidation](https://basistheory.com/solution/data-consolidation)
    - [Monetize Payments](https://basistheory.com/solution/monetize-payments)
    - [Multi PSP](https://basistheory.com/solution/multi-psp)
    - [Payment Method Discovery](https://basistheory.com/solution/payment-method-discovery)
    - [Payment Vault](https://basistheory.com/solution/payment-vault)
- [Platform](https://basistheory.com/platform)
  
  Show submenu for Platform 
  
    - [Enrichments & Add-Ons](https://basistheory.com/add-ons)
    - [Partners](https://basistheory.com/partnerships)
    - [Why Basis Theory](https://basistheory.com/why-basis-theory)
- [Pricing](https://basistheory.com/pricing)
- Resources
  
  Show submenu for Resources 
  
    - [Blog](https://blog.basistheory.com)
    - [Case Studies](https://blog.basistheory.com/case-studies)
- [Docs](https://developers.basistheory.com/)

Open main navigation

Close main navigation

- [Use Cases](https://basistheory.com/)
  
  Show submenu for Use Cases 
  
    - [Creator Economy](https://basistheory.com/use-cases/creator-economy)
    - [Digital Health](https://basistheory.com/use-cases/health)
    - [E-Commerce](https://basistheory.com/use-cases/ecommerce)
    - [Fintech](https://basistheory.com/use-cases/fintech)
    - [Gaming](https://basistheory.com/use-cases/gaming)
    - [Subscription Merchants](https://basistheory.com/use-cases/subscriptions)
    - [Travel](https://basistheory.com/use-cases/travel)
    - [VSaaS](https://basistheory.com/use-cases/vsaas)
- Solutions
  
  Show submenu for Solutions 
  
    - [Agentic Commerce](https://basistheory.com/solution/agentic-commerce)
    - [Data Consolidation](https://basistheory.com/solution/data-consolidation)
    - [Monetize Payments](https://basistheory.com/solution/monetize-payments)
    - [Multi PSP](https://basistheory.com/solution/multi-psp)
    - [Payment Method Discovery](https://basistheory.com/solution/payment-method-discovery)
    - [Payment Vault](https://basistheory.com/solution/payment-vault)
- [Platform](https://basistheory.com/platform)
  
  Show submenu for Platform 
  
    - [Enrichments & Add-Ons](https://basistheory.com/add-ons)
    - [Partners](https://basistheory.com/partnerships)
    - [Why Basis Theory](https://basistheory.com/why-basis-theory)
- [Pricing](https://basistheory.com/pricing)
- Resources
  
  Show submenu for Resources 
  
    - [Blog](https://blog.basistheory.com)
    - [Case Studies](https://blog.basistheory.com/case-studies)
- [Docs](https://developers.basistheory.com/)
- [Get a demo](https://basistheory.com/contact)

[Login](https://portal.basistheory.com/)

[Get a demo](https://basistheory.com/contact)

 April 21, 2026

![Picture of Basis Theory](https://blog.basistheory.com/hs-fs/hubfs/bt-favicon-new.png?width=50&name=bt-favicon-new.png) [Basis Theory](https://blog.basistheory.com/author/basis-theory-team) ·

[Payments](https://blog.basistheory.com/tag/payments)

# Stop Paying for the Same Features Twice

![Explaining features at the vault level](https://blog.basistheory.com/hubfs/Stablecoins%20Narrowbanks.webp)

 

## Table of Contents

- [Account Updater](https://blog.basistheory.com/enrichments-native-to-vault#AU)
- [Network Tokens](https://blog.basistheory.com/enrichments-native-to-vault#Network)
- [3DS Authentication](https://blog.basistheory.com/enrichments-native-to-vault#Auth)
- [BIN Data](https://blog.basistheory.com/enrichments-native-to-vault#BIN)
- [Taking Ownership](https://blog.basistheory.com/enrichments-native-to-vault#Ownership)

Running [multiple PSPs](https://blog.basistheory.com/using-multi-processor-payment-strategy)is smart. Paying for the same features across each of them isn't.

Apply some wholesale shopping logic to your payments stack.

While [97% of global enterprise retailers](https://investor.aciworldwide.com/news-releases/news-release-details/nearly-two-thirds-global-retailers-say-payment-method#:~:text=OMAHA%2C%20Neb.,report%20an%20increase%20in%20revenue.) operate with multiple payment service providers (PSPs), service duplication (meaning you are paying multiple providers for an identical feature) is often a byproduct. With features such as [3D Secure](https://blog.basistheory.com/3ds-implementation-learnings) (3DS), Account Updater, and Network Tokens bundled into a contract, merchants often pay for these services multiple times across their integrations.

Be a wholesale shopper instead.

Here’s what going wholesale shopping looks like for Account Updater, 3DS, Network Tokens, and even Bank Identification Number ([BIN](https://blog.basistheory.com/what-is-bank-identification-number)) Details.

## Account Updater 

For merchants running subscriptions, memberships, or any model with cards on file, [Account Updater](https://blog.basistheory.com/doing-more-with-personal-account-numbers) is the difference between a payment that clears quietly in the background, and a failed transaction that triggers an email, support ticket, or at worst, a cancellation. The question isn’t whether your PSP offers the service, it’s how they offer it.

At the processor level, a merchant doesn’t control which cards are being updated. Different logic can’t be applied across customer segments. You may not want an account updater running on every card type in your database—but if your PSP is handling it, that decision is not yours to make.

At the [vault](https://blog.basistheory.com/vaulted-or-vaultless-tokens) level, you provision account updater once under your own [Token Requestor ID](https://blog.basistheory.com/token-requestor-id) (TRID) and own the relationship directly with the[card network](https://blog.basistheory.com/card-network-introduction). You decide which cards receive updates, what you want changed, and when.

These updates can then be applied to any of your PSPs.

[Return to Top](https://blog.basistheory.com/enrichments-native-to-vault#TOC)

## Network Tokens 

The[authorization rate](https://blog.basistheory.com/challenges-in-migrating-payment-processor) lift alone makes network tokens worth the conversation.

Visa reports a 4.6% uplift for card-not-present (CNP) transactions and roughly 28% fraud reduction. Mastercard reports approximately 2.1% authorization rate improvement for CNP. These are not marginal gains for a high-volume merchant—they compound at scale.

But here is a question most merchants do not think to ask: who owns the [Token Requestor ID](https://blog.basistheory.com/token-requestor-id)?

When your PSP provisions [Network Tokens](https://blog.basistheory.com/network-token-deep-dive) on your behalf, the TRID is theirs, not yours. The tokens live under their umbrella. If you switch processors, add a new one, or want to route a specific transaction differently, you may not be able to bring those tokens with you. The portability you thought you had doesn't exist.

When Network Tokens are provisioned at the vault level, the TRID is registered in your name. You own the tokens. You see exactly when a Network Token is being used in a transaction versus a raw [PAN](https://blog.basistheory.com/credit-card-anatomy). You can route the same token across any processor in your stack, and you provision it once.

Not once per processor. Once, total.

For merchants running two or three PSPs, the cost math is straightforward: a feature you're currently buying multiple times becomes a single line item. And with wholesale pricing, that single line item costs less than any one of those individual PSP fees.

[Return to Top](https://blog.basistheory.com/enrichments-native-to-vault#TOC)

## 3DS Authentication 

The challenge for multi-processor merchants with [3DS](https://blog.basistheory.com/3d-secure-in-the-americas) is consistency. When 3DS is managed at the processor level, each PSP handles authentication independently. You have limited visibility into [frictionless](https://blog.basistheory.com/understanding-frictionless-payments) throughput rates, limited ability to tune which contextual data fields are being sent, and no unified view across your full transaction volume.

At the vault level, 3DS authentication is centralized. You enroll, you gain direct access to your own authentication data—frictionless rates, step-up rates, regional performance—and you can work to tune the parameters that maximize frictionless approvals. The result is higher frictionless approval rates and fewer unnecessary step-up challenges.

BIN data from the vault can inform which transactions even need 3DS to begin with, using issuer preference data to [route](https://blog.basistheory.com/can-chatgpt-route-payments) authentication decisions intelligently. And when a [soft decline](https://blog.basistheory.com/hard-soft-card-declines) comes back from an issuer indicating 3DS is required, the vault is already positioned to handle the retry without bouncing the request across multiple systems.

[Return to Top](https://blog.basistheory.com/enrichments-native-to-vault#TOC)

## BIN Data 

BIN data is the intelligence layer beneath every card transaction.

That data drives [fraud prevention](https://blog.basistheory.com/multi-processor-routing-payment-security), transaction routing, surcharge logic, dynamic risk thresholds, and customer segmentation. It's fundamental.

The problem is consistency. PSPs return BIN data in different formats, with different field names, and with varying levels of completeness. If you're running multiple processors, you don't have one BIN dataset, you have several, and someone on your team is responsible for maintaining the mapping between them. That's engineering time and operational overhead spent on a problem that shouldn't exist.

Basis Theory maintains a single, enriched BIN dataset at the vault level. Regardless of which processor a transaction flows through, the BIN data your team works with is standardized, consistent, and enriched card type, [issuer](https://blog.basistheory.com/issuer-processor), region, authentication preferences, and more. There's one source of truth, and it's always current.

For merchants using BIN data to power surcharging, regional compliance, or processor routing logic, consolidating this at the vault level removes the mapping problem entirely. You build the logic once, and it works everywhere.

[Return to Top](https://blog.basistheory.com/enrichments-native-to-vault#TOC)

## Taking Ownership 

![Card Enrichments at Vault Level](https://blog.basistheory.com/hs-fs/hubfs/Card%20Enrichments%20at%20Vault%20Level.webp?width=2505&height=1065&name=Card%20Enrichments%20at%20Vault%20Level.webp)

The theme running through every one of these features is the same: when they live at the processor level, you get opacity. When they live at the vault level, you get ownership.

Opacity means you don't know exactly what you're paying. It means your Account Updater runs on cards it shouldn't. It means your [network tokens](https://blog.basistheory.com/network-token-deep-dive) belong to someone else. It means your 3DS data is siloed. It means your BIN logic breaks every time you add a new processor.

Ownership means you provision once, pay once, and use everywhere. It means your TRID is yours.

If you're running more than one PSP and haven't audited what you're paying for Account Updater, Network Tokens, and 3DS across each of them, the answer is almost certainly: more than you should be.

Ready to audit what you’re actually paying for? Schedule time with our team and we can walk through your use case to see where consolidation makes sense.

[Return to Top](https://blog.basistheory.com/enrichments-native-to-vault#TOC)

 

[![View an Interactive Demo   See how the Basis Theory platform secures payment data and significantly reduces PCI compliance burden from day 1.  ](https://no-cache.hubspot.com/cta/default/22332934/interactive-171495116167.png)](https://blog.basistheory.com/hs/cta/wi/redirect?encryptedPayload=AVxigLLkU4wYjgQ5%2BRLbJYC9qWy8AUTnAokGhWoHNVjOeQJQ%2BtjU596jR%2BtDXdl1lAVFcCeVXTCl5%2FLpJnhe0nsF4vyp4qxLli749wTl8AdgDQKDep6WUBJHyoCCrCbgQNvfklPhx3FqcsE1UcOaj2PA91gnJzj2anLh2yPYcBrOJkyy%2FChq91gOJTcAIE%2Bx2zW2YG%2FYLcfICve3pYuga2wRnem%2F0kg%3D&webInteractiveContentId=171495116167&portalId=22332934)

## Related posts

[![Network tokens](https://blog.basistheory.com/hubfs/Making%20Dollars%20and%20Cents%20of%20Network%20Tokens.png)](https://blog.basistheory.com/network-token-deep-dive)

[Data Tokenization](https://blog.basistheory.com/tag/data-tokenization)

### [Making Dollars and Cents of Network Tokens](https://blog.basistheory.com/network-token-deep-dive)

![Picture of Basis Theory](https://blog.basistheory.com/hs-fs/hubfs/bt-favicon-new.png?width=50&name=bt-favicon-new.png) [Basis Theory](https://blog.basistheory.com/author/basis-theory-team) 

 September 25, 2025

[Read more](https://blog.basistheory.com/network-token-deep-dive)

[![Network token types](https://blog.basistheory.com/hubfs/network%20tokens.png)](https://blog.basistheory.com/network-tokens-power-agentic-commerce)

[Payments](https://blog.basistheory.com/tag/payments)

### [How Network Tokens Can Power Agentic Commerce](https://blog.basistheory.com/network-tokens-power-agentic-commerce)

![Picture of Basis Theory](https://blog.basistheory.com/hs-fs/hubfs/bt-favicon-new.png?width=50&name=bt-favicon-new.png) [Basis Theory](https://blog.basistheory.com/author/basis-theory-team) 

 September 23, 2025

[Read more](https://blog.basistheory.com/network-tokens-power-agentic-commerce)

[![Learn about the card networks and payment systems](https://blog.basistheory.com/hubfs/An%20introduction%20to%20card%20networks.png)](https://blog.basistheory.com/card-network-introduction)

[Payments](https://blog.basistheory.com/tag/payments)

### [Get to Know the Card Networks](https://blog.basistheory.com/card-network-introduction)

![Picture of Basis Theory](https://blog.basistheory.com/hs-fs/hubfs/bt-favicon-new.png?width=50&name=bt-favicon-new.png) [Basis Theory](https://blog.basistheory.com/author/basis-theory-team) 

 June 17, 2025

[Read more](https://blog.basistheory.com/card-network-introduction)

## Stay Connected

### Receive the latest updates straight to your inbox

### Follow on Social

<https://www.linkedin.com/comm/mynetwork/discovery-see-all?usecase=PEOPLE_FOLLOWS&followMember=colinthomasluce>

[![BTLogo (1)](https://blog.basistheory.com/hs-fs/hubfs/BTLogo%20(1).png?width=138&height=46&name=BTLogo%20(1).png "BTLogo (1)")](https://basistheory.com)

- Use Cases 
    - [Creator Economy](https://basistheory.com/use-cases/creator-economy)
    - [Digital Health](https://basistheory.com/use-cases/health)
    - [E-Commerce](https://basistheory.com/use-cases/ecommerce)
    - [Fintech](https://basistheory.com/use-cases/fintech)
    - [Gaming](https://basistheory.com/use-cases/gaming)
    - [Remittance](https://basistheory.com/use-cases/remittance)
    - [Subscription Platforms](https://basistheory.com/use-cases/subscriptions)
    - [Online Travel Agencies](https://basistheory.com/use-cases/travel)
    - [Vertical SaaS](https://basistheory.com/use-cases/vsaas)
- Developers 
    - [Quickstart](https://developers.basistheory.com/getting-started)
    - [Elements](https://developers.basistheory.com/docs/sdks/web/javascript)
    - [Documentation](https://developers.basistheory.com/)
- Basis Theory 
    - [Pricing](https://basistheory.com/pricing)
    - [Add-Ons](https://basistheory.com/add-ons)
    - [ROI Calculator](https://go.basistheory.com/roi)
    - [Case Studies](https://blog.basistheory.com/case-studies)
    - [Blog](https://blog.basistheory.com)
    - [Contact](https://basistheory.com/contact)
- Other 
    - [Terms and Conditions](https://basistheory.com/resources/terms-of-service)
    - [Privacy Policy](https://basistheory.com/resources/privacy-policy)
    - [Cookie Policy](https://basistheory.com/resources/cookie-policy)
    - [Security](https://basistheory.com/security)
    - [System Status](https://status.basistheory.com/)
- Compare 
    - [Basis Theory Vs. Evervault](https://go.basistheory.com/evervault-alternative)
    - [Basis Theory Vs. IXOPAY](https://go.basistheory.com/alternative-to-ixopay)
    - [Basis Theory Vs. VGS](https://go.basistheory.com/compare/very-good-security)

---

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Basis Theory",
    "url" : "https://blog.basistheory.com/author/basis-theory-team"
  },
  "dateModified" : "2026-04-21T13:20:54.528Z",
  "datePublished" : "2026-04-21T13:20:39.000Z",
  "headline" : "Stop Paying for the Same Features Twice",
  "image" : [ "https://blog.basistheory.com/hubfs/Stablecoins%20Narrowbanks.webp" ],
  "mainEntityOfPage" : {
    "@id" : "https://blog.basistheory.com/enrichments-native-to-vault",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://blog.basistheory.com/hubfs/BTLogo%20(1).png"
    },
    "name" : "Basis Theory"
  }
}
```