Chainpay. Payment infrastructure
being built the careful way.
Chainpay is Honeycomb's future merchant payment layer: fiat-denominated invoices, price-locked quotes, and settlement that goes straight to the merchant's own wallet — verified against the blockchain itself. It is not live. What follows is a preview of what is being built, including exactly how far along it is.
Percentages are internal engineering estimates, not certifications. An internal production-assurance review of the full system was completed in June 2026 with a 63-test matrix passing; mainnet remains a deliberate NO-GO until an independent external audit is complete. That is a feature, not a delay.
One load-bearing idea: only the chain can say "paid."
Most payment failures are bookkeeping failures. Chainpay is designed so an invoice can only become paid when an on-chain settlement event exactly matches a quote the system locked — verified by a database role the public API does not even possess. No optimistic statuses. No trust-me dashboards.
Your wallet, your funds
Settlement goes directly to the merchant's own wallet in a single transaction. Chainpay never custodies merchant funds.
A price that holds still
Invoices are priced in dollars; a quote locks the token amount for a fixed window, so nobody pays a moving target.
Reconciliation-grade records
Every settled invoice ties to a transaction hash, a locked quote, and a receipt. Clean inputs for accountants, not screenshots.
Five steps from invoice to clean books.
Create a fiat-denominated invoice
"$120.00 for order #1042" — priced in dollars, payable in approved tokens. Sharable as a hosted checkout link.
PREVIEW STATE: simulatedCustomer opens checkout, locks a quote
The hosted checkout shows the exact token amount, locked for a fixed window with a visible countdown. Server expiry stays authoritative.
PREVIEW STATE: simulatedPayment settles on-chain, directly to you
One transaction through the Chainpay router moves funds to the merchant wallet, minus a 1% platform fee to treasury (tips included in the fee base — tips can't bypass it).
PREVIEW STATE: simulated · no real fundsVerification matches chain truth to the locked quote
An indexer watches for the settlement event; the invoice becomes paid only on an exact match — amounts, merchant, quote ID. Mismatches raise alerts, never credits.
PREVIEW STATE: simulated lifecycle: PENDING → CONFIRMING → SETTLEDReceipt, webhook, reconciliation
A receipt with the transaction hash, a webhook to your systems, and records your bookkeeper will actually thank you for.
PREVIEW STATE: simulatedEvery step above runs as a simulation in the dashboard preview. No real payments are processed anywhere on this site.
What V1 is designed to be.
| Network posture | Polygon-first. Built and tested against the Amoy testnet; mainnet is hard-gated behind environment checks and remains NO-GO until external audit completes. |
|---|---|
| Assets | A curated, merchant-scoped token allowlist — only tokens with exact-amount transfer semantics. No open listing. Final supported set published at launch. |
| Custody model | Non-custodial settlement: funds move directly to the merchant's wallet through the router contract. Chainpay never holds merchant funds and never asks for seed phrases. |
| Pricing | Fiat-denominated invoices; quote-locked token amounts with a fixed TTL and an on-chain inclusion grace window. |
| Fee posture | 1% of subtotal plus tip, taken in the settlement transaction. Mirrored and parity-tested between contract and backend. Final published terms at launch. |
| Integrity model | Role-split database: the public API role cannot mark invoices paid. Only the verification pipeline, fed by on-chain events, can. |
| Status | PREVIEW — PENDING TESTING & EXTERNAL AUDIT |
Where it stands, honestly.
Architecture & contractsDONE
Router contract, quote-lock model, verification pipeline, dashboard, hosted checkout widget.
Internal assurance reviewDONE · JUNE 2026
Full-system misuse-case review; 63-test matrix passing; one launch-blocking defect found and fixed.
Public previewYOU ARE HERE
This page and the dashboard preview. Simulated flows only.
Testnet hardeningIN PROGRESS
End-to-end checkout runs on Polygon Amoy; operational runbooks exercised.
External auditPENDING
Independent review of contracts and backend. Mainnet stays locked until this completes.
Limited merchant launchFUTURE
Only after audit, with published terms, supported assets, and final fees.
Merchant interest list
One email when Chainpay completes testing and audit and opens to its first merchants. Nothing before that, nothing else after.
Honeycomb's education stays free, and Chainpay's testing and audit preparation are funded independently. If the careful approach resonates, optional support goes toward exactly that. Support never unlocks unaudited features — for anyone.