We were looking for a way to accept crypto payments with no changes to the rest of our workflow. After reviewing payment gateways, 0xProcessing was deemed more feasible than others. The setup was simple and once it ran, never required day-to-day attention. The ability to create payment requests is hassle-free and clear for daily transaction uses; hence, there is no confusion.

Following numerous payment drops and unexpected compliance holds with BitPay, we switched our primary checkout flow to 0xProcessing. Our global clients rely on cross-border technology, services, and products. We needed a payment gateway that is used to handling payment processing and won’t raise flags about something this usual. Actually the onboarding as merchant was quite easy. The API integration into Vettrack’s custom billing stack has taken the dev team the best part of about two afternoons and the docs don’t leave much to the imagination.

To run its day-to-day operations, Stable is used. We rely heavily on this payment links feature, which is completely automated. The VRCS feature converts incoming volatile assets to stablecoins automatically. The latter aspect alone has given adequate protection to our margins during the dips which get tied up in the afternoon. The 18 supported networks includes nearly everything our clients use. The processing time in so minimal, and we have still yet to have our first chargeback or false fraud flag since we started using it. The interface is effective but has glitches.

Since we don't usually process such payments, we weren’t looking for one that was equipped with many sophisticated tools. The first things were reliability and setup that shouldn’t be hard to get used to.

After looking at a number of options Fireblocks included we found 0xProcessing easier to work with. The on-boarding process was simple and the documentation covered the majority of our needs. It has been doing its job with no additional work since implementation.