Open scaspers opened 6 years ago
Authorize.NET. Enjoy both Accept.JS approach or the Accept Hosted with callback url approach.
At this moment, both seem like similar effort. This gives us the most flexibility of approaches, and isolates us from any one approach being removes.
Clearant - API looks very simple, Modal option is functional but not ideal.
The "Sale Transaction" with a single authorize + post looks really simple too.
The modal implementation has dependencies on Bootstrap, is difficult to provide data to like first-name, last-name etc to prefill known fields, and ultimately will feel like a separate page experience while having all the headaches of being hosted on our own site.
(ABM/FirstData/CardConnect) - IFrame only for the credit card field only, Would not recommend.
Do-able but not exciting. Not a portable solution unless we switch to another provider with IFrame for CC field only, which this is the first example we saw of this. They have no other options to switch to if the IFrame is declared a security risk, thereby obsoleting our provider from the digital experience side.
@scaspers will create a payment micro-app with the vendor of his choice. Since the usage is intended to be internal, user experience is a secondary concern to capturing the transaction.
The micro-app will implement some form of a callback URL pattern after showing the transaction receipt so that the user can continue what they were doing.
I will advise on the API and participate in design review.s
Links to possible providers integration methods.
Top contenders PaymentDepot - Authorize.net and others (list saved in email) Clearent - Multiple options ABM(FirstData) - Multiple options
These two are not as desirable for reason not relating to API/SDK Cayan - Multiple options Dharma - MXMerchant Dharma can also work with other 3rd party services such as Authorize.Net but with additional charges.