Skip to main content

Accepting Bitcoin payments for QuickBooks invoice


If you are interested in accepting Bitcoin payments for QuickBook invoices, follow the steps below to get started.
  1. Signup with Coinbase (https://coinbase.com). Coinbase is a Bitcoin payment processor.
  2. Link a bank account where you would like Coinbase to deposit payments from your customer. 
  3. Once the Coinbase account is setup, create a payment form at https://coinbase.com/merchant_tools?link_type=hosted as follows;
    • select Payment Type = Buy Now
    • Type a description in Item field. For example, Goods Sold, Service Charges etc.
    • Select a default amount. (Your customers will be able to change it.)
  4. Click "Show Advanced Options".
  5. Under "Variable Price" select checkbox - "Let the user change the amount" if you want customers to input a variable amount or "Add some suggested amounts" if you want customers to select from one of the pre-defined amounts.
  6. All other fields are optional.
  7. Click generate page code. 
  8. Scroll to the bottom of the page. Coinbase will create a href link for your payment form. Copy and save the link to your payment page in a text editor. 
  9. Sign in to your QuickBooks online. 
  10. Select the gear icon on top right and click Company Settings.
  11. Click Sales link in left navigation bar.
  12. Click "pencil" icon in Communication section.
  13. Append following text in email message field. Remember to replace the http url with the link to your payment page generated in step #8 above.
  14. Change Email options for invoices to "HTML email". 
  15. Click Save
  16. Click Done
That's it. Now when you create and send invoice QuickBooks email will include a link to your Bitcoin payment page. You can preview it by creating a new invoice and sending it your own email account.




Comments

Popular posts from this blog

Creating no-reply@domain.com account in Postfix

If you wanted to send emails to users but did not want to receive any replies to the email, you would need to setup a no-reply@domain.com email account. These kind of email ids are useful when sending emails containing forgotten passwords or activation code. Below are the steps for creating such account in Postfix. 1. Identify the file containing alias for Postfix First, make sure the following line in the ALIAS DATABASE section of the /etc/postfix/main.cf is NOT commented out: alias_maps = hash:/etc/aliases 2. Create an alias that redirects messages to /dev/null Edit /etc/aliases and add following entry devnull: /dev/null 3. Create a virtual email id Edit /etc/postfix/virtual and add following entry no-reply@domain.com devnull 4. refresh postfix alias and postfix cache Execute following commands. (You may require root privileges) > newaliases > postfix reload

jupyter notebook execution error: "http://localhost:8889/tree?token=xxx" doesn’t understand the “open location” message

I got this error when I tried to launch jupyter notebook on a mac. It is not a fatal error. I could still go to browser directly and copy/paste the url manually. The error indicates that when the command automatically tried to launch a browser, it couldn't find the default browser in jupyter configuration file. The easy fix is to specify the browser. Here are the steps to do so; 1.   Open ~/.jupyter/jupyter_notebook_config.py in an editor.       If the file does not exist then you can create a default config file by typing the following command;       jupyter notebook --generate-config 2. Search for a word "browser" to locate a following line.     #c.NotebookApp.browser = ''     By default it is commented. You can uncomment it and use one of the following values depending on your browser preference.     # set default browser to chrome     c.NotebookApp.browser = 'chrome'     # set default browser to safari     c.NotebookApp.browser = 

.ssh/config: “Bad configuration option: UseKeychain” on Mac OS

After upgrading Mac OS to Mojave I started seeing this error when doing "git pull". I was able to follow the steps below as described here ; 1. open ssh config vi ~/.ssh/config 2. Add the following lines to ssh config to keep your configuration compatible with both new and old versions of openssh. IgnoreUnknown UseKeychain UseKeychain yes That fixed the issue for me. Try running git pull again.    More details about the issue are available here .