Skip to article
ecomservices.io
Payment orchestration · How to run this
RoutingCalculatorCascadeCalculatorRetriesCalculator3DS placementCalculatorDeclinesCalculatorAffinityNot on this page yetOptimisationCalculator

Library · Payment orchestration · How to run this

Network tokens are not the whole vault

How to run thisPayment orchestration3 steps
CalculatorNetwork token coverage · Calculator lives in the articleOpen

Vault payment methods split between network tokens and PAN-only. Type both counts. Coverage % = network tokens / (network tokens + PAN-only) x 100.

Pair: Network token coverage on Orchestration. Fail path: network token fallback. Vault move: vault token migration.

What you type

Network tokens - payment methods stored with a network token in the vault window.

PAN-only - payment methods that still have PAN (or clear-PAN) only - no network token.

Vault total = network tokens + PAN-only. Coverage % = network tokens / total x 100. Push enrollment or re-token when coverage is weak - do not invent a coverage chip.

What not to do

Do not invent a coverage percent. Do not mix fallback attempt counts into vault coverage. Do not treat a migrated vault as covered without counting. Do not average MIDs when one vault owns the hole.

Related: Orchestration, network token fallback, vault token migration, token kill vs updater.

Procedure

  1. Type network-token and PAN-only vault counts.
  2. Read coverage % of the vault.
  3. Push enrollment or re-token when coverage is weak.

Failure modes

  • Inventing a coverage percent.
  • Mixing fallback attempt counts into vault coverage.
  • Treating a migrated vault as covered without counting.

Worked example

None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.

Glossary

Network token coverage %
Network-token payment methods ÷ (network tokens + PAN-only) × 100.

Work with us — We run this job on your accounts. Services

FAQ

Is this network token fallback?
Related Spreedly job. [Network token fallback](/manuals/spreedly-network-token-fallback) is fail then PAN on an attempt. This page is vault share with network tokens vs PAN-only.
Is this vault token migration?
Related vault move. [Vault token migration](/manuals/vault-token-migration) is leaving a vault. This page is coverage inside the vault you already use.
What coverage % should I invent?
None. Type network-token and PAN-only payment method counts from the vault export.