Simple and easy billing workflow
All applications come with a responsibility of improving the experience for merchant and for their customers. Let’s make sure users can actually pay for your app simply and easily and reward your hard work.
Table of Contents
Provide a clear and simple way to pay for your app
Paying for an application needs to be a simple and automated process: pay for everything in one place, know exactly what you pay in total. This allows merchants to keep up with all their spendings and subscriptions easily.
When you use your own billing model, the user pays in different places: in Ecwid Control Panel for the Ecwid plan subscription and somewhere else for your application. If there are more than one app installed, it can quickly become confusing. Luckily, Ecwid billing allows merchants to pay for their
Here is one of differences between billing models for the end merchant:
![]() | ![]() |
App prices listed and charged in a single place (Ecwid billing) | App can be free or paid. If it’s a paid app, where do I pay? (no Ecwid billing) |
Read also:
Charging users after they uninstall the app
When working with a large audience, there is always a chance there will be some users who don’t like the application or how it works after they use it. In that case, they will uninstall the app and will want to stop getting charged for its services. Make sure to handle that situation based on the type of services you provide.
If you use the Ecwid billing model, then it’s all set: user uninstalls an app and Ecwid will immediately stop their subscription for the application — simple and easy. However, it’s gets tricky when you have your own billing model: your app could provide the services not only for connected Ecwid store, but for other services, like ShipStation. For this situation, we advise to stop charges for any
Read also: