Looking for pilot merchants: free, self-hosted shielded ZEC checkout (I'll set it up for you)

Hi all,

I’ve been building Zcash Payment Service, a free, open-source (MIT) payment processor you run yourself. It already handles real payments as the backend for my app, MoneyStream, and now I’d like to get it running in a few more online stores.

How it works

  • Viewing key only. The service watches for incoming payments with a UIVK. Your spending keys never touch the server, so a compromised server can’t move your funds.
  • Shielded by default. Customers pay to a fresh shielded address for each order.
  • Self-hosted. Run it as a Docker container or embed the Rust crate. There are no fees, no middleman, and no account to open.
  • Simple integration. There’s a REST API with webhooks, plus an npm client (@nerdcash/zcash-payment-client) for JS/TS backends.

See it in action

What I’m offering pilot merchants

  • Free white-glove setup. I’ll do the integration myself if you can give me access to your store’s source (or work with your developer).
  • An early-adopter shout-out in the project README, linking to your store.

You can also add your store to ZEC merchant directories such as Cryptwerk, so ZEC holders can find you.

Who it’s a good fit for
Small or indie online stores and services where you control the site code: custom sites, WooCommerce, and digital goods or subscriptions. It’s especially handy if you already take ZEC by hand or through a processor and want shielded payments without fees.

If that sounds like you, or you know a shop that should take ZEC, reply here or DM me. Questions and critique are welcome too, since I’d like to hear what would stop you from adopting something like this.

Thanks!
Andrew

5 Likes

Hey! I came across your Zcash Payment Service project and thought there might be some interesting integration opportunities with something I’ve been building: ZADP (Zcash Agent Discovery Protocol).

ZADP is a decentralized discovery protocol where sellers can publish offers through Zcash shielded memos, and buyers or AI agents can discover them through independent indexers.

Looking at your project, I think the two could complement each other quite well. ZADP focuses on discovery and connecting buyers with sellers, while your Payment Service handles the actual payment processing, including payment sessions, shielded addresses, confirmation tracking, and webhooks.

One possible integration would be for a ZADP seller endpoint to use your Payment Service to generate payment requests and handle payment verification. This could also allow merchants already using your service to make their products or services discoverable through ZADP, including to AI agents.

I think there’s some interesting potential here without either project needing to change its core architecture.

Would love to hear your thoughts on this and whether you’d be interested in exploring interoperability!

Sounds potentially interesting. Let’s move the discussion over to nerdcash/zcash-payment-service Ideas · Discussions · GitHub so this post can stay focused on finding merchants.

1 Like