17 ms·
I'm curious how these aggregators (i.e. API routing layers) convince vendors to work with them. Is it just the promise of high transaction volume? For Segment
by scribu 6y ago
I'm curious how these aggregators (i.e. API routing layers) convince vendors to work with them. Is it just the promise of high transaction volume?
For Segment it was relative easy, I imagine, because most of the tools they integrated with had freely-available APIs.
- kunle 6y agoIn a lot of cases they don't want to deal with a small startup in the first place, and the aggregator is paying full freight anyway, so the vendors are happy to do it.
- tomasien 6y agoThe key - for us - is to be not just a routing layer, but a huge value add in addition to being a routing layer. We provide workflow management, decisioning, analytics, etc and those are things that all clients need. Underlying providers of various things know they will need to be integrated into something like that (whether homegrown or built by a vendor), so being part of an ecosystem like ours that ensures success is critical. Homegrown implementations of the same vendors vs. using those vendors in Alloy stops less fraud, causes more manual work, is more opaque, approves fewer good customers, takes longer to get live with, etc. Importantly, we don't pitch either side (vendors or our clients) on using Alloy to compare vendors - rather to make the most of them (now and as their needs change). It's not just "I can switch this at any point" it's "I will have a best in class system now and the peace of mind that I will have a best in class system tomorrow as my needs change, without needing to engage in 5 enterprise sales cycles to get there"