Clyus Create · brand directions · 2026-08-07

FOIL

The invoicing layer for onchain payments. Paste a transaction hash and it writes the invoice, with the exchange rate frozen to the second the payment cleared.

01

What we are actually solving

Companies already move real money onchain. Contractors invoice in USDC, agencies get paid in USDT on Tron, teams settle in ETH. The payment works fine. The paperwork does not exist.

What the payer has

A 66 character hash and a wallet address. Nothing a bookkeeper can file.

What accounting needs

A numbered document with a date, a counterparty, line items, a tax field, and a defensible fiat value at the moment the money moved.

What happens today

Someone rebuilds it by hand in a spreadsheet weeks later, at whatever rate they googled. That rate is the part that does not survive an audit.

02

The name

A counterfoil is the half of a document you keep when the other half is torn away and issued. Cheque books, receipt books, bills of lading. It is the retained proof of a transaction that already happened, which is exactly what this product makes. The chain keeps one half. You keep the other.

ReadingWhat it buys
counterfoilthe retained stub, the proof half of a torn document
foil stampthe authentication mark on certificates, seals and banknotes
to foilto defeat a forgery

Four letters, hard consonants, no chain / block / ledger / verse suffix. It reads as a finance tool, not a token.
Rejected: REMIT (sits under Remitly), VELLUM (collides with Vellum AI), STAMPED (collides with stamped.io), CARBON (collides with carbon credits in web3), BLOCKBILL (descriptive, no soul).

03

One device, three registers

A circle split by a perforation. Left half solid, right half outline. One payment, two records. It survives at 16px and at 2 metres, and each direction re-materialises it differently: extruded, machined, engraved. The same perforation runs through every document, separating the invoice from the part the chain wrote.

04

Why 03

The product's whole claim is that this document is real and you can prove it. Security printing is a two-hundred-year-old visual grammar built to make exactly that claim, and it is unclaimed in this category.

It also earns us something the other two cannot. The guilloché rosette is generated from the invoice's own transaction hash, so the ornament is a function of the payment. Change one character and the pattern visibly changes. That is a verification feature wearing a decoration's clothes, and it costs about 3 kB of canvas code with no image assets and no network request.

CLAY is the strong second and the better choice if the target buyer is the freelancer rather than the finance department. PLANT is the safest and the least differentiated. All three are built on the same tokens, so the switch is a theme change rather than a rebuild.