Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Payment request web-form #4460

Open
xbtdev opened this issue Jun 20, 2016 · 2 comments
Open

Payment request web-form #4460

xbtdev opened this issue Jun 20, 2016 · 2 comments

Comments

@xbtdev
Copy link

xbtdev commented Jun 20, 2016

Wouldn't it be cool if I could give my employees/contractors/etc a URL to a web form where they could request a payment.... and it would generate a (non-input-locking) proposal in copay that I could approve or reject?

Seems like an easy thing to add to BWS. We could make this an option that could be enabled in settings. I think this would be awesome... Anyone else like the idea?

@dabura667
Copy link
Contributor

If you are going to make a webform anyways, why bother adding the proposals to the client and have a script that you would use to approve one of them, which would create a normal proposal on Copay to which you could sign. This would be totally doable and easy with bitcore-wallet-client and a google spreadsheet + google forms combo. The only time Copay would come to play is after clicking approve on your script, you will see a proposal on copay and you tap sign and you're done.

BWS does not currently support transaction proposals that don't lock funds.
(there are many race conditions which would cause other transaction proposals to fail even though the quorum hasn't finished voting on them yet... etc.)

@matiu
Copy link
Contributor

matiu commented Jun 20, 2016

Related: https://github.com/bitpay/copay/issues/3825

This kind of proposals would be more like a "ToDo" list. So far we considered ToDo items created by copayers, no 3rd parties, but It is an interesting idea. A copayer could "open" a payment URL for certain payer and close it when ever he want, enforced by the copayer's Copay App client, not BWS. There could be a shared secret to sign the requests by the 3rd party and not seen by BWS. I can see many use cases for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants