Earlier quoted context omitted.
Thanks for reading! >Having checked Zestful's page out, I got a suggestion for you. How about building a client lib ready for developers for at least a few mainstream languages? This should be rather easily achievable if you type in the Swagger specs to your API. That allows you to generate (Swagger codegen) those libs with possibly just minimal tweaking left on your part. This is something I've thought about. I'd re…
As someone who has done quite a bit of shopping for various services, having a language-specific library ready to go is a major factor. I doubt that someone already paying you would still need one, though, so it should probably be considered a strictly "customer acquisition" feature. I understand your rule, but I don't think it should be that strict.
I mean wasn't Stripe known to become so successful exactly because of easiness of use, in other words a good user experience for developers with simple ready-made libraries. Making a new payment gateway is hardly innovative by itself after all.