This project adds per-store Zcash configuration to the BTCPayServer Zcash plugin so that one BTCPay instance can support more than one store without their Zcash settings affecting each other. It improves an existing Zcash payment integration by fixing a clear missing capability instead of creating a new payment product.
Project Description
The BTCPayServer Zcash plugin already supports the basic ZEC payment flow, but it does not yet handle multi-store use properly on a single BTCPay instance. That makes it harder to use for operators who manage more than one store or more than one account on the same server.
This project fixes that gap. The work will move Zcash configuration to the store level, make invoice and payment handling follow the correct store’s settings, add an upgrade path for older installs, and include regression tests and reviewer documentation.
A working MVP of the core isolation path has already been built. This proposal is for finishing that work properly, testing it, documenting it, and preparing it for upstream review.
Not really sure what the purpose of this application is? Per-store configuration is already supported, no need for a new database key. Code appears to be fully AI generated and the demo doesn’t even have the plugin installed.
Thanks for your comment. Just to clarify, this application is not about adding multi-store support to BTCPay itself. BTCPay already supports multiple stores.
What this proposal is about is the Zcash plugin. The goal is to make sure each store on the same BTCPay instance keeps its own Zcash configuration, and that the plugin uses the correct store’s settings during invoice creation and payment handling.
So the scope is simple and specific, which is to complete and harden store-isolated Zcash support in the plugin, add a clear upgrade path for older setups, add regression tests, and prepare the work for upstream review.
On the MVP, the current branch and demo are the right materials to review. The plugin is installed in the current implementation, and the MVP shows Store-A and Store-B with separate Zcash configuration. The reviewer guide also shows how that behavior can be checked directly.
You can check the current review materials:
Branch:
Reviewer guide:
So to be precise, this is a proposal to finish and upstream per-store Zcash behavior inside the BTCPay plugin. It is not a proposal for a new BTCPay feature outside the plugin, and it is not based on a mock demo.
We would appreciate any review being based on the current branch, reviewer guide, and demo as they stand now. @ZCG , a thorough review of the current implementation would be appreciated before any funding decision is made.
Thank you for submitting your proposal. Following a thorough review by the ZCG and a period for community feedback on the forum, the committee has decided not to move forward with this proposal.
We sincerely appreciate the time and effort you invested in your application and encourage you to stay involved and continue contributing to the Zcash community. Further details will be available in the meeting minutes to be posted later this week.