ZecLink — Making Zcash Payments Simple and Accessible | $40,000 ZCG Grant Proposal

ZecLink — Making Zcash Payments Simple and Accessible

Hello Zcash Community!

I’m @kinkin74, founder and lead developer of ZecLink.

I’m excited to share our application for $40,000 in funding from Zcash Community Grants (ZCG).

GitHub Grant Application:

Project Website:
https://zeclink.io

What is ZecLink?

ZecLink is an existing web application designed to simplify sending and receiving Zcash (ZEC) through shareable payment links.

The goal is to make Zcash payments easier for everyday users, including people who are new to cryptocurrency.

The project has been independently developed and self-funded so far.

What Will the Grant Support?

1. ZEC-to-USD Cash Out Integration

ZecLink already includes an initial, temporarily disabled integration designed around the conversion flow:

ZEC → USDC → Fiat → US Bank Account

We aim to further develop and validate this integration, allowing a sender to fund a link with ZEC and a verified recipient to receive USD in their own eligible US bank account.

Production availability will depend on suitable provider support, regulatory feasibility, and KYB/KYC approval.

2. Android and iOS Applications

Develop testable mobile applications for creating, sharing, tracking, and claiming ZEC payment links.

3. Zcash Wallet Integration

Improve interoperability with compatible Zcash wallets to simplify funding and claiming.

4. Infrastructure and Security

Improve transaction monitoring, reliability, credential handling, recovery procedures, testing, and hosting infrastructure.

5. Education and Adoption

Create tutorials, video demonstrations, documentation, and opportunities for community testing.

Funding Breakdown

  • Startup Funding: $5,000

  • Milestone 1 — Zcash Core & Wallet Integration: $8,000

  • Milestone 2 — Cash Out Integration & KYB: $10,000

  • Milestone 3 — Android & iOS Mobile Applications: $9,000

  • Milestone 4 — Security, Infrastructure & Education: $8,000

Total Requested: $40,000 USD

Grant-funded software components will be released under the MIT license, with technical documentation and verifiable milestone deliverables.

Community Feedback

I would greatly appreciate feedback from Zcash users and developers, particularly on payment-link security, wallet compatibility, mobile usability, and the proposed Cash Out workflow.

Thank you for taking the time to review ZecLink and its grant application!

@kinkin74
Founder & Lead Developer — ZecLink

This is an interesting idea! Given that ZecLink is already working and the proposal includes more community testing, I’m curious what you’ve learned from users so far, especially what recipients want to do with the ZEC after they receive it.

For the wallet integration work, which wallets are you planning to test? It would be interesting to see the experience across wallets like Zingo, ZODL, and Vizor.

I would also be interested in how the security review evolves as you move toward mobile and cash-out.

Thank you for the thoughtful questions and for taking the time to look at ZecLink!

User feedback and what happens after receiving ZEC

ZecLink is already functional, but broader, structured community testing is still an important part of the proposed work. I don’t want to overstate the amount of user feedback collected so far.

One of the key questions we want to validate is what recipients actually need after claiming a payment link: keeping the ZEC, transferring it to their preferred wallet, spending it, or converting it into fiat.

This is also why we’ve been exploring a cash-out experience. There is an initial integration in the codebase, but it is currently disabled. Enabling it would depend on finding a suitable provider and completing the necessary compliance and security work, particularly because the recipient may be different from the person who funded the payment link.

Wallet integration

Zingo, ZODL, and Vizor are all wallets we’d like to include in our compatibility testing, subject to their supported workflows.

Our focus will be on testing the full recipient experience, including claiming a payment link, transferring or withdrawing ZEC, handling errors, and understanding where users encounter friction.

I also want to document the results openly rather than simply claiming wallet compatibility before it has been verified.

Security review

Security is a major priority, especially as ZecLink expands toward mobile and potentially cash-out.

The review will focus on payment-link secrets and claim flows, wallet and key handling, backend authorization, mobile storage, and the additional risks associated with third-party payout integrations.

We plan to combine automated testing, manual review, and an independent security assessment scoped to the available grant budget. Any cash-out functionality would remain disabled until the relevant technical, provider, and compliance requirements have been satisfied.

I appreciate these suggestions.

Production availability will depend on suitable provider support, regulatory feasibility, and KYB/KYC approval

This seems vague and likely the Achilles heel of this proposal.

How exactly do you plan on collecting the necessary KYC information for fiat cash out?

If a user would have to provide you with their personal information to get payment then what is the advantage of using your service rather than simply cashing out at an exchange which can already wire directly to a bank account?

1 Like

Thank you for raising this concern. I agree that the fiat payout component is one of the most important aspects of the proposal, and I would like to clarify the intended user experience.

The key distinction is that the recipient does not need to interact with cryptocurrency at all when choosing Cash Out.

The flow is designed as follows:

  1. A sender funds a ZecLink payment link with ZEC.

  2. The recipient opens the link and selects Cash Out.

  3. Behind the scenes, the system handles the ZEC-to-USDC conversion automatically.

  4. The USDC is then used to initiate a USD payout to the recipient’s bank account through a supported payment provider.

From the recipient’s perspective, there is no need to create or connect a cryptocurrency wallet, handle ZEC, perform a swap, or interact with an exchange.

The recipient simply receives a payment link and chooses to receive the funds in USD.

This is the main advantage over a traditional exchange.

With an exchange, the recipient typically needs to open an account, receive cryptocurrency, convert it, and request a withdrawal.

With ZecLink, these technical steps are handled by the payment infrastructure rather than by the recipient. The recipient is not required to understand which cryptocurrency funded the payment or how the conversion is performed.

The sender and the final bank account beneficiary can also be different individuals, which is essential to the payment-link use case.

Regarding KYC and compliance:

Our objective is to make the recipient experience as simple as possible, ideally without requiring a separate exchange account or identity-document onboarding where a payment provider can legally support that model.

We are evaluating providers that facilitate third-party payouts and may handle the required verification and compliance checks without putting the entire onboarding burden on the recipient.

The beneficiary may still need to provide basic information, such as their name and bank account details. The payment provider may also require additional identity verification depending on the transaction and applicable regulations.

Importantly, the recipient not interacting with ZEC does not mean the source of funds is concealed from the payment provider or exempt from compliance checks.

Current development status:

The initial automated ZEC-to-USDC Cash Out integration has already been developed, but the feature is currently disabled.

The remaining challenge is identifying and validating a provider that can compliantly support the final USDC-to-USD bank payout, particularly when the recipient is not the original sender.

That is precisely what we intend to investigate and validate through the proposed Cash Out milestone.

We will evaluate provider requirements, fees, payout times, recipient experience, and compliance feasibility before enabling the feature in production.

Ultimately, ZecLink is not intended to be another cryptocurrency exchange. It is intended to make receiving a Zcash-funded payment feel as simple as receiving an ordinary payment link, even for someone who has never used cryptocurrency.

So you are requesting $5k for startup funding then $8k for wallet integration, then finally $10k before you investigate if the user will ever be able cash out??

The cash out step is where this project is most likely to fail, if it was easy to convert cryptocurrency (USDC or otherwise) to USD sent to a users real world bank account then wallets like ZODL and Cake would already be doing it. They already offer Swaps to USDC via Near so why not the extra step?

I personally don’t think this project should be funded but if it is then milestones are backwards; step 1 should be figuring out cash out.

4 Likes

Thank you for the honest feedback. I understand your concern, and I agree that Cash Out is one of the highest-risk parts of the proposal.

However, there is an important practical challenge I would like to clarify.

Most payment providers offering fiat bank payouts through business APIs require KYB (Know Your Business). This generally means having a registered legal entity, providing company documentation, completing beneficial-owner verification, and potentially maintaining a business bank account.

As an independent developer who has self-funded ZecLink so far, these requirements involve real upfront costs.

This is one of the main reasons I included startup funding in the proposal. It is not simply a request for funding before investigating Cash Out; it is intended to help establish the business and compliance infrastructure needed to validate the integration properly.

I also want to clarify that ZecLink already has a working payment-link application and an initial automated ZEC-to-USDC conversion integration. The missing and most challenging component is the compliant USD payout to the recipient’s bank account, particularly when the recipient is different from the original sender.

I believe the most responsible approach would be to:

  1. Start with preliminary provider research and obtain written feedback on whether our intended payout model is supported.

  2. Only proceed with business registration and KYB expenses if a provider confirms that the model is potentially eligible.

  3. Use a limited portion of the initial funding to complete onboarding and validate the payout integration.

  4. Proceed with the larger Cash Out development milestone only if feasibility has been demonstrated.

I am open to restructuring the milestones so that Cash Out feasibility is addressed first, while retaining a clearly defined and justified initial budget for the business setup and KYB requirements.

If no suitable provider can support the model, I would document the findings rather than proceed with an unsupported Cash Out implementation.

Finally, Cash Out is not the only value ZecLink provides. The existing ZEC payment-link functionality, wallet interoperability, security improvements, and mobile accessibility remain useful independently of fiat payouts.

I appreciate the criticism. My goal is not to ask the community to take an unnecessary risk, but to establish a realistic, measurable development plan that accounts for both the technical and regulatory challenges.

I really like the direction of this proposal because it starts to address a practical question: how do we make it easier for ordinary people and merchants to accept Zcash?

If I sell chocolate, I may be happy to accept ZEC as long as there is a simple, trustworthy way for me to receive it and convert it into the currency I actually need. I should not have to become a crypto expert first.

This connects with the earlier discussion, “What Is Stopping Zcash From Reaching More People in the Real World?” especially around merchant acceptance, on/off ramps, usability, and education.

A couple of things made me curious.

Given the cash-out piece seems central to what makes this different, I also wonder if it makes sense to test that early, along with the security and legal/compliance questions. I imagine there will be a lot of iteration along the way, which is part of the design process.

I was also curious about the development history. The GitHub account linked to the proposal was created on October 22, the same day the grant was submitted, and currently has no public repositories. That may have a simple explanation, but it would be helpful to hear a little more about where ZecLink has been developed and the team’s previous work.

I like the idea and hope it continues to develop. Trust seems important on both sides: for the person receiving the payment and for the community supporting the work.

As I’ve mentioned previously, the initial Cash Out integration has already been developed and is present in the ZecLink codebase, but it is currently disabled.

The intended flow is to allow a recipient to convert ZEC into USD and receive the funds in their own bank account. However, this involves additional technical, security, and regulatory considerations, particularly when the recipient is different from the person who originally funded the payment link.

This is why early feasibility testing, finding a suitable payout provider, and evaluating compliance requirements are important parts of the proposal. I don’t want to enable this functionality until we can establish that it is both technically reliable and compliant.

Regarding GitHub, I wasn’t aware that having an older GitHub account or an established public repository history was a requirement for applying for a community grant.

ZecLink was developed independently and self-funded before this application, and the platform is already live at https://zeclink.io.

That said, I understand why the community would want greater visibility into the development history. I’m committed to making the project’s technical progress, source code, documentation, and grant-funded deliverables transparent and verifiable.

Thank you for your grant application. After ZCG reviewed it and the community had the opportunity to share thoughts on the forum, the committee reached a decision not to advance the proposal. We value your work and invite you to remain part of the Zcash community.

See the meeting minutes for details: Zcash Community Grants Meeting Minutes 11/9/2026