I can package the price, artwork and buyer questions in the same link instead of explaining the whole flow in messages.
SMALL LINKS. SHIELDED PAYMENTS.
A little link.
A lot of
possibility.
Your next release. A cause you care about. Something worth paying for. Put it in a Zipp.
Make your first Zipp ↗Built on Zcash · Explore the local preview
One link. Open possibilities.
A useful little connection.
01 / THE LINK IS JUST THE BEGINNING
01 / PUT SOMETHING GOOD BEHIND IT
Small format.
Real potential.
A payment is only the beginning.
Give your link a job to do.
THE INDEPENDENT COLLECTIONOff the
grid.ZIPP / 001
grid.ZIPP / 001
DIGITAL DOWNLOAD
Ideas worth taking offline.
A field guide for your next creative detour. One payment, then your download.
Create a download Zipp ↗ILLUSTRATIVE PREVIEW · MAKE IT YOURS IN STUDIO
02 / ONE LINK. MANY PLACES.
Made to show up
where people are.
Each Zipp keeps its purpose clear, whether it opens as a page, sits on your site, or travels in a message.
PAID RELEASEPut your next
MULTI-SURFACE PREVIEWSee it before
ZEC · SHIELDEDZIPP / 001Looks at home
Start from
Put your next
drop in motion.
Set a price. Share the link. Unlock the file after confirmed payment.
Make a release ↗See it before
you send it.
Check how your card reads across different sizes and contexts.
Open inspector ↗ZEC · SHIELDEDOne useful link.
Artwork, fields, payment and fulfilment in one shareable action.
Open Studio ↗FOR YOUR WEBSITELooks at home
in your interface.
Use the shared renderer or React components without rebuilding the flow.
View components ↗STANDARD RECIPESStart from
something proven.
Downloads, contributions and fixed payments, ready to adapt.
Browse examples ↗MOVE YOUR POINTER THROUGH THE CARDS
03 / BUILT AROUND REAL WORK
Useful to people
making things happen.
Different roles, one clear handoff: turn an idea into a link people can understand and act on.
Illustrative product perspectives. Replace with verified customer quotes before a public launch.
The shared renderer means the card can feel consistent on the hosted page and inside the product I already run.
A paid download makes more sense when the payment and delivery are clearly presented as one action.
Contribution choices are easier to share when the purpose, amount and next step stay together.
The preview catches cramped labels and awkward layouts before the link ever leaves the studio.
SWIPE, DRAG, OR USE THE ARROWS
04 / FROM AN IDEA TO A LINK
A few steps.
A new connection.
Explore the preview tools ↗Your thing.
Your details.
Set the artwork, price, fields and action. Start with a standard recipe, then make it yours.
A link that
goes with you.
Preview your card across layouts. Share its page or bring the component into your own website.
Payment meets
purpose.
The buyer authorizes a Zcash payment. Confirmed receipt unlocks the configured next step.
05 / LESS ON DISPLAY
Public invitation.
Shielded payment.
Share what you're offering. Zipp uses shielded Zcash payment flows to keep payment details off the public ledger.
Privacy has boundaries: the merchant and receipt scanner can see payment details. Wallet and network services may see metadata. Shielding isn't anonymity.
Understand the integration ↗06 / BUILT TO BE BUILT ON
Your interface.
Same possibility.
Bring Zipps into the places you build. Explore the API, TypeScript SDK, React renderer and standard action recipes.
Explore developer tools ↗THE ZIPP TOOLKIT↗
01 API & TypeScript SDK ↗02 React components ↗03 Standard action recipes ↗04 Multi-interface previews ↗Start locally. Connect deliberately.
Test before you take it live.
THE NEXT GOOD THING STARTS SMALL.