When you offer pay as you go pricing as an API provider, your potential customers are often concerned about the danger of accidentally using much more resources than planned and huge invoices as a result of that.
This can happen due to a bug in customer’s application, malicious user, oversight, lack of monitoring, cat stepping on the “Refresh” button, and thousand other reasons.
Things like that have happened before:
- AfterShip charged us 26K USD and refused to refund
- How I Accidentally Spent Over £1500 Using Google’s Map API
- OpenAI just charged me $120 overnight with zero explanation.
Even the possibility of accidental overages makes users more hesitant to finish a purchase and can significantly lower conversion rates.
Nadles has a built-in solution to that.
Since yesterday, you can set a maximum usage limit for your pay per use products on Nadles and API users can adjust the limits as necessary, in order to protect themselves from sudden overages.
If the limit is reached, the API gateway will simply cut access. And, since the limit can be changed by the user at any time, it allows users to flexibly manage their maximum spend limit.
Nadles will also conveniently calculate the maximum amount the customer will be able to spend with the current limit.
It’s a nice way to protect your customers and give them a feel of safety. And when customers feel safe, they can complete purchase faster and with greater confidence.
