5 Reasons for Developers to use QUID for Micropayments

QUID was built being developer-focused from the ground up.  After all, it’s in our DNA - we’re developers too.  We know that developers are the heart of everything online, and without them, the internet would be a much less interesting place.

Our goal for both users and developers using QUID is to get out of their way, provide some cool, reliable, and high performing technology, and to be amazed at the things everyone creates.

Enough with the manifesto, let’s get specific.

Photo by Clark Tibbs on Unsplash

#1. Simple, easy-to-use, APIs

As a developer, you know how complex APIs can be, both to learn and to use.  That’s why we focused our efforts on making our APIs easy and simple to use, completing most platform actions in one or two calls.  Our REST API allows you to use whatever programming language you choose, while our Javascript libraries let you embed QUID easily into your apps and websites.

We’ve gone through extensive effort to reduce the amount of learning required to use QUID so developers can integrate into their application, sites, and technology stacks, as quickly and easily as possible.

Photo by Philipp Katzenberger on Unsplash

#2. Security and Privacy

QUID collects only the bare minimum of information that is necessary to operate effectively and for regulatory compliance.  When a payment is made, QUID shares only a merchant-specific user ID with the seller.  This ID is unique to a  merchant, and strikes a balance between user privacy and developer utility.  This means purchases can’t be tracked across other web properties, something unique in the payments industry.

QUID was built from the ground up to be safe, secure, and reliable.  We use a number of industry standard tools, methods, and processes to protect your data, including TLS-secured endpoints, iterative hashing, privilege separation, public-key cryptography, and hardware security modules (HSMs) as needed.

Privacy and security were not an afterthought when we were building QUID.  They were a requirement and built in from the ground up.

Photo by Matthew Henry on Unsplash

#3. AutoPay

Unique to QUID, AutoPay allows your application or site to automatically charge users for previously agreed upon services, asynchronously, without requiring their explicit acknowledgement for each transaction.  

AutoPay is perfect for charging users a little, often, without nagging them to accept each charge at the time of use or consumption.  Users still have full control, of course -- they must approve your application for AutoPay and setup a daily budget (e.g., $2 per day)

Photo by Marc Schäfer on Unsplash

#4. Automatic Currency Localization

QUID shows your products and services in the currency of your users, regardless of what unit you’re charging.  We handle the conversion for you, automatically, and display prices in the unit preferred by your users - theirs.

This approach avoids the cognitive load associated with doing an on-the-fly currency conversion a buyer might do in their heads, and increases the likelihood of ad hoc, spontaneous purchases.  It also eliminates the need to create and maintain complex pricing tiers or matrices.

Photo by Slava Bowman on Unsplash

#5. High Throughput

The last thing you want, after putting time and effort into integrating technology into your app or website, is finding out that what you’ve integrated is unreliable, slow, or performs poorly.  We hate that too.  Rest assured, we built QUID to process thousands of simultaneous payments per second, using our custom high volume ledger, on rock-solid, globally distributed infrastructure.  In fact, we stopped testing after we exceeded the transactional volumes per second the global Visa network currently handles.  

That means we can support the types of volumes necessary for high transaction applications for IoT, SaaS, or anything you can think of.  The only limit is your imagination.

To demonstrate how easy and fast it is to build something using QUID, we decided to eat our own dog food.  We’ve been busy hacking away at some small fun ways to use QUID, and we’ve even written about some of our experiments on our blog.

We can’t wait to see all the cool ideas and applications that are built, and the innovative ways the developer community uses QUID!

Author image

About Derrick Mealiffe

Derrick is an approachable nerd and avid cyclist who knows far too much about things most people don't (and shouldn't) care about.