PLURIBUS Test mode · V3

A quieter way to pay online

Your real account
never checks out.

Pluribus creates one transaction lineage from a disposable credential. The merchant sees a short-lived number; authorization, capture, and refund stay connected behind it.

01 Short-lived02 Single lineage03 Provider-neutral
PLURIBUSONE LINEAGE
VALID THRU--/-- SECURITY••• ZIP•••••
DEMO ACCOUNT)))
Current credential--:--

Start the demo

Open a synthetic account.

Choose a ledger-backed demo balance or, when configured, Stripe test funding. Pluribus stores provider tokens—not underlying card data.

1

Authorize

The processor adapter normalizes the request; cryptographic validation and policy run independently of its source.

2

Reserve

The selected funding provider reserves integer minor units while the gateway records an append-oriented event.

3

Settle

Capture, reversal, and refund remain on the original transaction lineage; unrelated credential reuse declines.

Issuer-style lifecycle simulator · synthetic data only
LIFECYCLE / V3

Transaction laboratory

Test the whole payment, not just approval.

Authorize now; capture, adjust, reverse, and refund separately. Each action stays linked to one transaction.

Explicit scenarios

Choose a scenario or submit the configured checkout directly.

Authorization request

Payment

$48.23

The dummy processor submits a normalized POST /v1/authorizations. Never enter a real card.

Consumer ledger

Transactions

Open gateway dashboard ↗
TimeMerchantAuthorizedCapturedRefundedStatus
No activity yet.