PLURIBUS V1 research path

Beyond processor-issued cards

A number made
for one moment.

The V1 Pluribus model derives a complete payment credential from two independent keys, an account identity, and a short time window. The consumer and virtual checkout are reunited below so the whole idea can be exercised on one page.

Open the cryptographic lab ↓
KEY AIdentity256-bit secret
KEY BPresentation256-bit secret
TIME WINDOW05:00PAN · EXP · CVC · ZIP

Interactive V1 demonstration

Generate here. Check out here.

Both sides use the same synthetic Pluribus processor. The wallet derives the fields; the processor independently recreates them and makes the authorization decision.

CRYPTOGRAPHIC WALLETPreparing research account…
PLURIBUS / CRYPTOSYNTHETIC
•••• •••• •••• ••••
VALID THRU--/-- CVC••• ZIP•••••
DEMO BIN 424242READY

Initializing a credential from the current five-minute nonce bucket…

VIRTUAL CHECKOUTNorthstar test merchant
Research notebookNetwork Futures, Vol. 1
$12.00
⌁

The checkout submits the synthetic PAN, expiry, CVC, and ZIP exactly as a merchant-side integration would. Never enter real card data here.

The proposed network path

Move the decision to the issuer edge.

The cryptographic credential becomes viable only when the assigned BIN range and issuer authorization system recognize the same construction.

  1. 01Derive

    The wallet derives PAN, expiry, CVC, and optional ZIP from independent keys plus a time bucket.

  2. 02Present

    The merchant submits an ordinary card-not-present authorization through its acquirer.

  3. 03Route

    The card network routes the approved BIN/account range to the sponsoring issuer processor.

  4. 04Recreate

    Pluribus recreates candidate values for the accepted time windows and applies account policy.

  5. 05Bind

    The first match is atomically bound to one transaction lineage; unrelated reuse declines.

What makes it real

A network program, not just an API call.

A future Visa path could use a licensed member or BIN sponsor, an issuer processor, and an approved authorization connection such as VisaNet Connect – Issuing. Visa states that non-member issuers require BIN sponsorship and that production endpoints undergo business, risk, security, and PCI review.

01

BIN sponsorship

A licensed issuing bank owns or sponsors the BIN and approved account range.

02

Issuer processing

The processor routes authorization messages to Pluribus and supports clearing, settlement, reversals, disputes, and stand-in behavior.

03

Security boundary

PCI Level 1 controls, HSM-backed key custody, rotation, audit, segmentation, incident response, and reviewed cryptography become mandatory.

04

Program operations

Cardholder onboarding, KYC/AML, consent, funding, fraud, reconciliation, customer support, and regulatory obligations must be operational.

Available today

Stripe Issuing path

Stripe allocates each virtual PAN, hosts its display, and asks the Pluribus real-time webhook for an issuer decision by Stripe card ID.

Open Stripe wallet →

Research direction

Cryptographic BIN path

Pluribus and a certified issuer authorization tier recognize a derived credential directly inside a sponsored network card program.

Demonstrated here on dummy rails only