Ching V2: In-person crypto payments as a service

Let’s think about what exactly can be provided as a service.

The flow discussed in part 1 doesn’t need any changes. Here is a diagram:

All the customer-side screens can be provided by the service and made customizable so no effort required from a POS provider. The seller-side integration should be as easy as:

Add an “accept a crypto payment” button

Show QR-code (provided by service the library/package/API)

Handle transaction received/completed/failed

This can be further simplified by using a modal provided by the service that shows QR-code, confirmation progress, status, possible errors and retries. This way, the POS provider needs to add one button and implement a transaction completion handler.

Sellers also need a way to specify where the incoming funds need to go. This is just a wallet address that can be set in the app UI or in the transaction modal on first use if look-and-feel customization is not a priority. Later advanced features like selecting accepted currencies, instant conversions, and multiple currency-specific wallets can be set up.

Lastly, there needs to be a web portal for POS providers where they can get API keys, see logs, and set up transactions fees. No effort, other than creating an account, is needed from POS providers.

Overall, this type of service will allow a single front-end developer with no prior crypto knowledge to add multi-currency, multi-chain crypto support to their product in a span of a sprint (or two)!

Support for xDai is already included and we are planning to work with as many layer-2 solutions as possible.