Here you will find everything you need to know about the hardware and software used to build featherPay, being open source is at the core of featherPay there are no secrets all we want is to enable the adoption of crypto currency.


Most if not all of the software required to get your featherPay up and running can be found on the GitHub Repository and that is the only place it will get updated. In addition to all the code being available there is also a Step-by-Step Guide to setting it all up!

I will at some point introduce some form of version control on the software and will document the features and bug fixes accordingly but again this will all be carried out on the GitHub Repository


featherPay is based on a bunch of everyday off the shelf open source hardware!

I have specifically used main brand manufacture components here, so you shouldn't have to much problem getting your hands on the components required to build a featherPay regardless of where you are in the world.

I’m not going to go into immense amounts of detail on all of the components as being open source there is plenty of information out there on the internet for you to get your eyes on but here’s the list.

Raspberry Pi 2

Sorry guys and gals it has to be a Pi 2! I tried with a Pi B and it just didn't have enough grunt to run featherPay, partly because I'm now using a Ubuntu distribution to get round another problem the surfaced during development, and partly because the generation of QR codes takes a bit of CPU power.

But there are advantages to using the Pi 2 that I’m already planning to exploit in a future release of featherPay

Adafruit PiTFT 2.8″ Touch Screen

Now this little thing has to be the cutest little screen I have every used 🙂 its size, power consumption and resolution lend well to the featherPay project and touch screen to boot so didn’t have to worry about reprogramming GPIO buttons as the code runs through.


This is a package of awesomeness in its own right, and without it I’m sure I would still be scratching my head on the longest running problem of the whole project (how to get the keypad reliable) used in featherPay to make the Pi think the keypad is a USB number pad, but I have no doubt that I’ll be using them again for something else and real soon

SanDisk Ultra MicroSD

I went with an 8GB card, for no other reason than the pricing point. But and it’s a big BUT make sure it’s fast, as fast as you can afford. Don’t get sticking anything less than a Class 10 in and expecting to get good results because you won’t I tried a Class 4 for fun and it quite simply wasn’t

N150 Nano USB WiFi Adapter

featherPay needs to be able to talk (or at least this version does) the N150 adapter is not only cheap it's really simple to use as the required drivers are already installed on all the distro's I have used throughout the development process. 3G was being considered as an option and may still well be, but for now WiFi is all that has been added.

3×4 KeyPad

Used on featherPay for entering the local currency transaction amount, * is used as the decimal place and # is used for backspace to correct any entry errors

Power Supply

As a handheld terminal it stands to reason that the device wants to be portable, not connected to the mains outlet all of the time.

Power for the device comes from a Adafruit PowerBoost 500C and a 3.7v @ 3000 mA/h battery pack, and there's a little bit of a circuit to make the shutdown and power off work. The scripts required to make the power supply work are included in the GitHub repo and there is a bit on the GithHub Wiki Getting Started Page that will get it all up and running for you.


In true Open Source style why would we be using anything else other than a 3D printer (well at least for the prototypes)?

The casing was draw in SolidWorks and the files can be found via the following links, I have also exported the as .STL files so you can import the into your favorite slicing application to prepare your Gcode for the printer.

If you don't have access to a 3D printer, have a quick google around as there are plenty of people out there offering it as a service.

Casing Top

The top of the casing is made up of three parts, primarly done to make it much easier when wanting to change the Screen or KeyPad components that are mounted to the underside of the top

SolidWorks Files

[sdm-download id="262" fancy="0" button_text="KeyPad Surround"] [sdm_download_counter id="262"]

[sdm-download id="271" fancy="0" button_text="Screen Surround"] [sdm_download_counter id="271"]

[sdm-download id="273" fancy="0" button_text="Casing Top"] [sdm_download_counter id="273"]

[sdm-download id="275" fancy="0" button_text="Compete Casing Top"] [sdm_download_counter id="275"]

.STL Files

[sdm-download id="281" fancy="0" button_text="KeyPad Surround"] [sdm_download_counter id="281"]

[sdm-download id="280" fancy="0" button_text="Screen Surround"] [sdm_download_counter id="280"]

[sdm-download id="279" fancy="0" button_text="Casing Top"] [sdm_download_counter id="279"]

[sdm-download id="277" fancy="0" button_text="Compete Casing Top"] [sdm_download_counter id="277"]

Casing Bottom

The bottom of the case provides storage for the battery and charging circuit, as well as mounting points for the power in and external USB connection.

Its a simpler design than the top and has to be printed on a raft with supports to enable the narrowing of the case under the keypad to make it easier to hold.

I am currently making a few changes to this drawing and will upload the new one when complete

SolidWorks Files
.STL Files