Merchant cockpit · sample storefront “Aurelia Goods”

Good evening, operator.

Settled (sample, 30d)

$4,820.00

Open invoices

3

Avg. settlement

2m 41s sample

Processing

DISABLED

Live rail status

Component	State	Note
Invoice engine	Preview	Sample data only
Settlement watcher	Preview	Simulated confirmations
Payment processing	Disabled	Locked until testing & audit complete
Webhook delivery	Disabled	Placeholder endpoints only

Why everything says previewThis dashboard exists so merchants can see exactly what's being built. Real payment paths stay disabled until independent testing and audit are complete — that's a launch gate, not a toggle.

Invoices · create & track

Invoices

Create a sample invoice

Amount (USD)

Reference

Asset

Network

Preview behaviorInvoices live only in this browser tab. The simulated lifecycle walks PENDING → CONFIRMING → SETTLED. In the live design, a customer locks a fiat-denominated quote for a fixed window, settlement lands directly in your wallet minus a 1% platform fee, and only the matching on-chain event can mark the invoice paid.

Invoice ledger

ID	Reference	Amount	Token	Status

Payments · settlement visibility

Payment status

Most recent invoice lifecycle

Created

Pending

Confirming

Settled

Receipt

Chain confirmations (simulated)0 / 5

What this meansIn the live design, this view watches the network itself — settlement is something you can see, not something you take on faith. Here, confirmations are simulated.

Sample payment feed

Time	Reference	Amount	Network	Status
18:42:07	ORDER-1041	$86.00	AMOY	Settled
18:31:55	ORDER-1040	$240.00	AMOY	Confirming
17:58:12	INV-SAMPLE-09	$54.50	AMOY	Pending
16:20:48	INV-SAMPLE-08	$310.00	AMOY	Expired

Receipts · reconciliation-grade records

Receipts

RECEIPTCP-PREV-000184

MERCHANTAurelia Goods (sample)

REFERENCEORDER-1041

ASSET / NETWORK[TOKEN] · AMOY

TX HASH0xPREVIEW…d34d

CONFIRMATIONS5 / 5

CREATED2026-06-12 18:39:02 UTC

SETTLED2026-06-12 18:42:07 UTC

AMOUNT$86.00

STATUSSETTLED · SAMPLE DATA

Built for your bookkeeper

Every receipt carries the fields reconciliation actually needs: reference, asset, network, transaction hash, confirmation count, and both timestamps. Export targets (CSV, accounting webhooks) are part of the design — placeholders today.

Honest labelHash and amounts above are sample data. Nothing here represents a real transaction.

Storefront · wallet & identity

Storefront settings

Settlement destination

Merchant wallet address (placeholder)

Storefront name

Display currency

Design direction: your keys stay yoursChainpay's current design points payments at a destination you control. The dashboard never asks for seed phrases or private keys — at preview, at launch, or ever. Anything that does ask is an attack.

Integrations · webhooks & redirects

Webhooks & success URLs

Endpoints (placeholders)

Webhook URL

Signing secret

Success redirect

Event	Delivery
invoice.created	Disabled in preview
payment.confirming	Disabled in preview
payment.settled	Disabled in preview

Security postureWebhook payloads will be signed; secrets live in environment configuration only. Fields here are intentionally read-only — there is nothing live to configure yet.

Admin · recovery states

Recovery & admin

If something goes wrong, the path back is visible

Scenario	Planned response	State
Lost dashboard access	Verified re-authentication flow; settlement destination unaffected (you hold the keys)	Designed
Wrong webhook endpoint	Pause deliveries, replay queue after correction	Designed
Stuck "confirming" payment	Network status surfaced inline with guided next steps	Designed
Suspected compromise	One-switch freeze of invoice creation + audit-trail export	Designed

What this meansRecovery is being designed before launch, not after the first incident. Each row becomes a tested, audited flow before any merchant relies on it.

Onboarding · preview walkthrough

Merchant onboarding, previewed

1 · Identity

2 · Storefront

3 · Destination

4 · Test invoice

5 · Go-live check

Step 3 — Choose where value settles

At launch, you'll point Chainpay at a settlement destination you control, verify it with a tiny test, and confirm it twice. The flow is deliberately slow here — this is the step where mistakes are expensive, so the interface makes you certain, not fast.

Go-live checkStep 5 will refuse to complete until Chainpay itself has completed testing and audit — the product holds itself to the same checklist it holds merchants to.

Trust · testing & audit status

Audit & testing status

Internal assurance

63/63 TESTS

Independent audit

PENDING

Live processing

LOCKED

The launch gate

Chainpay goes live only after independent testing and audit complete, with results we can stand behind publicly. Until then, this page is the source of truth — if it doesn't say live here, it isn't live anywhere. An internal production-assurance review (June 2026) passed a 63-test matrix and deliberately holds mainnet at NO-GO until external audit completes.

Support the work, optionallyTesting and audit are funded directly, without sponsors. If you'd like to help them happen sooner, you can support Honeycomb. Support never unlocks early access to unaudited payment features.