Simulated · no real card data is processed

The customer journey

From merchant sign up to a tapped payment, secured, settled to the acquiring bank, and refundable. Press play and watch the full lifecycle run end to end, every step proven.

press play to walk the full lifecycle
01
Onboard
📝

Sign up

Merchant self-onboards, no paperwork.

02
Onboard
🪪

KYC and KYB

Identity and business verified.

03
Onboard
🔑

Go live

MID, API keys, and terminal ready.

04
Pay
👆

Tap

Card tapped on the PAX terminal.

05
Secure
🔒

Tokenize

PAN replaced with a token at the edge.

06
Pay
⚙️

Gateway

PaychainX normalizes and routes.

07
Pay
🛡️

Risk and AVS/CVV

allow, score 20, match.

08
Pay
🏦

Authorize

To the network and issuer, approved.

09
Pay
💳

Capture

The charge is confirmed.

10
Secure
🔐

Quantum proof

ML-DSA-65 signed receipt, valid.

11
Settle
🏛️

Acquiring bank

Settled to the ISO acquiring bank.

12
Settle
🪝

Webhook

Merchant notified, reconciled.

13
Refund
↩️

Refund

Reverse anytime, with a signed proof.

Each phase is colored: onboard, pay, secure, settle, refund. Everything below this band is the same lifecycle, hands on, with the real gateway response shape and a tamper-evident receipt chain.

Pay $42.00

PaychainX Demo Merchant · order #PCX-1042

No production credentials. The card above is a non-routable test PAN; nothing is sent to a real processor.

Transaction lifecycle

1
Tokenize

PAN → token at the edge

2
Authorize

Funds held on issuer

3
Capture

Charge confirmed

4
Settle

Batched for funding

press Pay to begin

Signed webhook events

HMAC-SHA256

Each event carries a signature header so your endpoint can verify it really came from PaychainX.

[idle] waiting for a transaction…

Gateway response

production response shape

This mirrors the real gateway sale response: AVS and CVV results, a risk decision with score, transparent fees, and the pq_proof. All values here are simulated for the demo.

run a payment to see the response

Tamper-evident receipt ledger

SHA-256 hash chain

Every settled payment posts a cryptographic receipt to this page. The proof_hash is computed in your browser as SHA-256(receipt || prev_hash). Each receipt is mathematically chained to the one before it, so a single altered field breaks every hash after it.

no receipts yet, run a payment