Page 28 - GS181201

Spotlight Innovators

SAePay is a family-owned business based in Los
Angeles, CA. For over 15 years, the company has
been assisting merchants with payment solu-
U tions to fit their needs. USAePay's payment gate-
way supports most of the major platforms in the credit card
industry and works with some of the leading check plat-
forms. USAePay is pleased to work with most of the larger
merchant service banks in the US and Canada.

What’s New:
Anatomy of friendly code

n today’s technology world, the application program interface – better known as the API – has become the standard
way of connecting functionality from one application to another to enable data to flow seamlessly between the two
programs. APIs in payment technology have been common for nearly twenty years. Simple integrations, such as
I linking transaction information captured through a gateway to a merchant’s accounting application is an example
of the earliest API written in payments. However, over time, more complicated payment-centric APIs have emerged that
feed many kinds of payment and cardholder details to enterprise resource management (ERP) applications and vertical-
specific Software-as-a-Service (SaaS) programs such as inventory or sales management applications used for business.

“Software APIs have evolved drastically over the past two decades and are now a standard practice in the payments
industry for integrating complex transaction detail with other data-driven applications used by the merchant,” stated
Vlad Galyuz, Vice President of Product Development at USAePay
Easy-to-implement APIs

Ironically, not all gateway APIs are easy to work with right off the shelf. Some only fit a certain purpose and will lack
the scaling needed to cover a broader integration use. Others may not be fully tested ahead of implementation and could
still have unresolved data flow issues. It is even common for some APIs to be so complex, they can’t be easily repurposed.
These unanticipated situations can cause headaches and delays for development teams that work to pair applications
and functionality together so data can flow seamlessly to and from the right places. “Nothing is more frustrating for
a developer than receiving an API that either doesn’t work properly or is not inclusive of all the expected features and
functionality,” continued Galyuz.

28