How do you compare yourself to Spreedly? How would you compete with their offering?
I think these solutions are really neat, but I wonder how you can handle some edge cases which I think are really difficult. For example, let's say I want to use credit cards with Adyen. Now after a year of this, I have a lot of customers with their credit cards connected to my business via Inai so recurring payments go smoothly. Now, Stripe comes knocking and will give me a much better price on credit cards. Can I just switch the backend to start routing card payments to Stripe? Will all the customers need to re-enroll their credit cards when trying to pay now? If not, then I guess you're managing the card data on you side?
I think this and Spreedly are interesting, but I can imagine that for large companies, you want more control over your payments flow even than what's provided here, which is why when compared to Spreedly, we personally went with VGS and do the PSP routing in our own system.
IF my assumption about that is true, then that leaves you with the smaller merchant market. Of those users, I think just sticking with one of the reliable PSPs with global coverage (Stripe/Adyen) might be simpler.
I'm (among other things) a fintech consultant specializing in payments; my company primarily works with Stripe, sometimes with Adyen/Worldpay/Xsolla.
Like you said, payments orchestration is nothing new. What differentiates you from any other middleman in the field?
I'll give you one example as a test scenario: A current client of mine is a small business incorporated in the US, doing business in both the US and South Korea with $10/mo subscriptions. They want to offer native South Korean payment methods in SK such as KakaoPay and Samsung Pay. I've had to set them up with Smart2pay (Nuvei) because, after months of negotiations, Adyen wouldn't take a contract with them because they're too small a fish to care about. In the US, they offer Paypal and Stripe but their current gateway middleman (Uscreen) takes an obscene cut and doesn't offer good subscription management features to make up for it.
Their current payment stack is inconsistent, hard to manage, lacks lots of admin features and costs them more than it should. If you can do something for them, I'll be super impressed :) (Email in my profile!)
Setting up and maintaining a payment stack, especially if you operate in multiple regions, takes months of developer time. Most merchants set up their stacks ad hoc, leading to loss of revenue (e.g. if you don't display Apple Pay in a certain way at checkout, Apple will penalize; same for Paypal) and wasted admin time (multiple dashboards for refunds, coupons etc). Working with a single payment provider locks the merchant in, as customer data is vaulted with the Payment Service Provider (PSP) making switching difficult. Meanwhile customer payment methods are exploding with newer rails like BNPLs (Buy Now Pay Later), open banking, QR code based and even crypto emerging rapidly
Karthik and I previously ran a DTC fitness business. Tailoring the payment stack to each market that we expanded into was a big pain. We spent weeks on every payment integration and our payment stack was a mess. We were after all running a fitness business and not a payments one.
At Inai, we provide a single unified API that connects to multiple payment providers (Stripe, Braintree), alternate payment methods (wallets, BNPLs etc). We make it easy to launch into new markets and to keep your service agnostic of PSP. For B2B companies, we make it easy to allow your customers to send invoice links and accept payments across cards and ACH.
We plan to give merchants a IFTTT dashboard to set up custom business logic (e.g. show Klarna, SOFORT, and cards in Germany but cards, Paypal, and Apple Pay in US). Merchants can view all transactions across providers, and very shortly will be able to manage chargebacks, refunds, and coupons, and get analytics on transactions (e.g. success rates by card/PSP, insights on why transactions were declined).
Payment orchestration as a concept is not new, but medium sized merchants were not being served well with the existing solutions. We found that many merchants in this category had a knowledge gap with respect to payments and therefore needed someone to hand-hold and deliver outcomes for them, so fixing this is what we are focussed on.
We are building this product for merchants so if you have a use case that is currently not being served by our product, we would love to hear from you. Your problems and pain points will drive our roadmap.