Still API-first, by design
I was looking back through some older blog posts from early 2014, when we first launched our next-generation online escrow payment service, and guess what we were talking about? Our API-first technical architecture. (APIs, or application programing interfaces, allow different technology platforms to interact and share services)
When we were first building our escrow service, we had the benefit of being able to evaluate the existing legacy escrow providers in the market, taking the best parts that work and jettisoning the parts that don’t. As a result, we were able to build an up-to-date escrow platform with a fully API-first architecture, designed from the ground up for a web 2.0 world.
Payoneer Escrow’s API-first architecture enables our partners to easily and seamlessly integrate our escrow payment service into a variety of platforms, such as online marketplaces and ecommerce sites. This includes partners as massive as UPS, as well as startups like BidSlate for purchasing global film distribution rights, and Efty for domain name transactions. By integrating with our escrow API, our partners are able to focus on creating a fantastic user experience for their customers, while leaving the heavy lifting of processing payments to us.
As the saying goes, we even eat our own dog food. The escrow service offered through Payoneer Escrow website, used by buyers and sellers from over 130 countries worldwide, is actually built on our own API. So, every day over the past 3 years, we have been living and breathing our escrow API, serving integrated partners and powering our own escrow website.