0xProcessing Reviews

1. Barrie Grubb

   · Branch Manager at J & W Carpets · about 2 months ago
   Easy to fit into our existing process

   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.

   🏁 Competitors: CoinGate, RIZON

   👍 Pros:    Quick to get started|Supports multiple cryptocurrencies|Simple payment request|Clear transaction status

   👎 Cons:    More detailed reporting would be useful|Dashboard customization is limited
2. Cimin Cohen

   · Founder and CEO at Idea Peddler · about 2 months ago
   The goal is to move BitPay in order to utilize it globally.

   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.

   🏁 Competitors: BitPay, CoinGate, RIZON, Coinbase

   👍 Pros:    Vrcs effectively mitigates market volatility risk|Supports a wide range of native tokens and|Transparent fee structure with no hidden billing surprises

   👎 Cons:    Ui dashboard feels overly basic for complex financial analysis|No native fiat payout options available
3. Ahsanul Hasan Amit

   · CEO and Founder at Dream Workers Tech · about 2 months ago
   A practical option for making crypto payments on occasion.

   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.

   🏁 Competitors: CoinGate, Fireblocks, BitPay

   👍 Pros:    Straightforward on-boarding|Supports several networks|Easy to understand pricing

   👎 Cons:    Limited analytics|Few dashboard customization options

Apache Thrift Reviews

0xProcessing mentions (0)

Apache Thrift mentions (13)

• Show HN: TypeSchema – A JSON specification to describe data models

  I once read a paper about Apache/Meta Thrift [1,2]. It allows you to define data types/interfaces in a definition file and generate code for many programming languages. It was specifically designed for RPCs and microservices. [1]: https://thrift.apache.org/. - Source: Hacker News / almost 2 years ago

• Delving Deeper: Enriching Microservices with Golang with CloudWeGo

  While gRPC and Apache Thrift have served the microservice architecture well, CloudWeGo's advanced features and performance metrics set it apart as a promising open source solution for the future. - Source: dev.to / over 2 years ago

• Reddit System Design/Architecture

  Services in general communicate via Thrift (and in some cases HTTP). Source: over 3 years ago

• Universal type language!

  Protocol Buffers is the most popular one, but there are many others such as Apache Thrift and my own Typical. Source: over 3 years ago

• You worked on it? Why is it slow then?

  RPC is not strictly OO, but you can think of RPC calls like method calls. In general it will reflect your interface design and doesn't have to be top-down, although a good project usually will look that way. A good contrast to REST where you use POST/PUT/GET/DELETE pattern on resources where as a procedure call could be a lot more flexible and potentially lighter weight. Think of it like defining methods in code... Source: almost 4 years ago