PayButton March 2021 Update

5 347
Avatar for PayButton
3 years ago

The PayButton team has continued to work through the first few months of 2021 to deliver on some key features promised in the FlipStarter we ran in October.

For those who are not familiar with PayButton, our goal with this project is to make it as easy as possible for people to accept Bitcoin Cash on their website or web app. You can see some demos and learn more about it on our website.

Below is a summary of what has been accomplished so far as well as what is currently planned:

Dev Progress (v1.0.0 -> v1.1.0):

  • Created new website with proper documentation & examples in both English and Chinese.

  • Added option to set a goal/target (useful for fundraising), denominated in either BCH or fiat.

  • Added option to visibly disable the button / widget.

  • Added improved input handling (eg. allowing "50" where a number is expected).

  • Added visible error for missing or invalid BCH addresses.

  • Added option to hide toasts on payment detection.

  • Better support for filling the button with more text (longer strings).

  • Improved website dark mode.

  • Improved compatibility with web UI frameworks (eg. Boostrap-Material, Material-UI).

  • Misc other minor UI/UX improvements.

Existing Plans for 2021/2022:

  • Switch to an (optionally) self-hosted, open source payment detection server/API for improved reliability and capability for mission-critical applications.

  • Create 'Pay' page where websites can simply use a simple hyperlink to bring people to a full-page payment screen.

  • Add support for locking web content behind a paywall.

  • Support for displaying units in 'bits'.

  • Set up testing framework for long term development.

  • Ensure success toast matches the chosen button/widget theme.

  • Add option to open payment dialog without actually needing a button.

New Plans for 2021/2022:

  • Create new user-focused website where people can login to view/manage their PayButton income.

  • Add support for domain-based usernames & IDs to pay to as an alternative to simple addresses.

  • Add 'dev' mode that points to the BCH Testnet.

  • Allow passing arbitrary data through to server upon payment.

  • Introduce new "portrait" dialog layout for mobile devices.

  • Add option to allow live editing of the payment amount.

  • Allow goal amount to be based on either the total sent to the address or its current balance.

Other Items on Our Radar:

  • Support for BCH stable coins / post office protocol.

  • Support for BIP70.

  • Support for stealth addresses.

  • Support for CashAccounts.

  • Support for SLP tokens.

  • Create WooCommerce plugin.

  • Create WordPress plugin.

  • Option to send arbitrary BCH tokens upon payment.

  • Streamlined payments with support for in-browser non-custodial wallets.

As always, let us know if you have any feedback as we're continually refining priorities based on what people want to see next!

https://paybutton.org

https://twitter.com/thepaybutton

https://github.com/paybutton/paybutton

37
$ 3.38
$ 2.00 from @Ellie
$ 0.72 from @TheRandomRewarder
$ 0.50 from @Doramas89
+ 3
Avatar for PayButton
3 years ago

Comments

Hello Guys, When I was in my college and I had to complete my assignment on a topic essay. Then one of my friend suggested me about https://writinguniverse.com/free-essay-examples/steve-jobs/ for hiring the services of essay writers. On this website I found experts of each and every field and you can hire them as per your requirements.

$ 0.00
1 year ago

Ok good work.

$ 0.00
3 years ago

Am new here i need help

$ 0.00
3 years ago

Good article keep it up dear

$ 0.00
3 years ago

Please add a MEMO PROTOCOL SENDCASH message parameter resembling
https://memo.cash/send (see https://memo.cash/protocol)
The "message" could be added by javascript and/or editable by the sender.

  • You could either use the Memo format
    ( OP_RETURN 0x6d24 with legacy address + message )

  • or use an OP_RETURN with a new action code (0x6d??) with just the message.
    [the recipient(s) is(are) already known from the transaction outputs]

  • Using the MEMO format allows people to immediately easily confirm payments
    and would allow much further development built on your service.
    I have done this for ElectronCash OP_RETURN data strings and it is not too difficult.

  • The OP_RETURN function is one of BCH's greatest superpowers:
    the ability to annotate a transaction to give the transaction context for buyer and seller.

  • Thanks in advance. ( I can contribute to expedite this )

$ 0.00
3 years ago