Salesive app billing works in three steps: the app asks for a charge, the store owner approves it in the dashboard, and the money moves from their wallet or card to the developer's payout store. Salesive keeps 5 percent, and the payout store's wallet is credited the price minus that fee, converted into the wallet's currency.
What does the merchant see when an app charges?
The app asks, and the store owner approves. Nothing moves before that approval. The request appears in the dashboard, where the owner can see what is being charged and decide whether to accept it. This is the important safety property: an app cannot quietly take money from a store because it holds an API token.
The owner can pay from the store wallet or from a card. Once the charge is approved, the money moves to the developer's payout store. If the owner declines, nothing happens. That keeps the consent in the same place as every other store decision, which is easier to supervise than a payment that appears on a card statement later.
One-time charges vs subscriptions
A one-time charge is a single payment for a single thing: a setup fee, a premium feature, a report, an onboarding service. It is the right shape when the value is delivered once. The app asks, the owner approves, and the charge is complete.
A subscription is a recurring charge for ongoing access. It suits an app that keeps doing work every month: syncing orders, monitoring stock, running a loyalty scheme. The owner approves the subscription once, and the app is paid on the recurring schedule rather than asking for a new approval every period. Both shapes use the same approval model, and both are reported back to the app by webhook.
How does the 5 percent fee work?
Salesive keeps 5 percent of the charge. The payout store's wallet is credited the price minus that fee, converted into that wallet's currency. If a charge is 10,000 naira and the payout wallet is in naira, the wallet is credited 9,500 naira. If the payout wallet is in another currency, the remaining amount is converted at the point of payout.
The fee is on the charge, not on the developer's costs, and it is deducted before the wallet is credited. That makes the number easy to reason about: whatever the app charges, the developer receives 95 percent of it in their payout currency. Price with that in mind rather than treating the gross figure as revenue.
Show the merchant the number before they approve. A charge request that says what the app does, how much it costs and whether it repeats is much easier to accept than one that only shows an amount. Clear pricing also avoids awkward conversations, because the owner knew what they were approving when they clicked. Keep a record of each charge in your own system as well, so a merchant who asks about a payment months later can be answered without guesswork.
Which scopes does billing need?
Billing uses two scopes: WRITE_CHARGES and READ_CHARGES. WRITE_CHARGES lets the app create a charge request. READ_CHARGES lets it read the state of the charges it created. An app that does not charge should not request either of them.
That separation matters at install. A merchant installing an app that only reads orders should not see a charge permission on the consent screen. If you add billing later, the app needs the scopes before it can ask for money, so plan the permission set before you publish rather than surprising existing installs with a new request.
Which webhooks tell you what happened?
Two webhooks carry the billing events: charges/paid and subscriptions/activated. charges/paid tells the app that a one-time charge has been paid. subscriptions/activated tells it that a subscription is active and the app can unlock the recurring features.
Use the webhook as the source of truth, not the browser redirect. A buyer can close the tab before the redirect lands, and a redirect can be replayed. The webhook is signed and tied to the actual payment event, which is what you want before you unlock a feature or send a receipt.
How do you enable billing?
Billing must be enabled per payout store by Salesive. It is not something an app can switch on for itself, and it is not automatic when the app is published. If you plan to charge, sort out the payout store and ask for billing to be enabled before you submit the app for review.
The payout store is also where the money lands, so it needs to be a store you control and can withdraw from. Decide the currency before you launch, because the conversion happens on the way in. An app priced in naira but paid out into a different currency will see a different number in the wallet, and that is easier to explain to buyers before the first charge than after it.
The merchant approves, the money moves, the platform takes its 5 percent. Everything else is bookkeeping.
Frequently asked questions
Who sets the price of an app?
The developer sets the price. The store owner sees the charge request in the dashboard and decides whether to approve it. Salesive does not set the price and does not approve it on the merchant's behalf.
Can a merchant pay by card?
Yes. The owner can pay from the store wallet or from a card. The charge is approved in the dashboard either way, and the money moves to the developer's payout store after approval.
When does the developer get paid?
When the charge is approved, the payout store's wallet is credited the price minus the 5 percent fee, converted into that wallet's currency. The developer withdraws from the payout store like any other wallet balance.
Is the 5 percent fee charged on every payment?
Yes. Salesive keeps 5 percent of each charge, whether it is a one-time payment or a subscription period. The fee is deducted before the payout wallet is credited.
Can I charge for an app without enabling billing?
No. Billing must be enabled per payout store by Salesive before an app can charge. It is a separate step from publishing the app, so plan for it before you launch rather than after your first merchant asks for a paid feature.
App billing is deliberately boring: an ask, an approval, a transfer and a 5 percent fee. That is the point. Keep the scopes narrow, use the webhooks as the source of truth, and set up the payout store before you publish. Start with what Salesive apps are, then read how to build and publish an app. For the platform, see features and pricing, or browse the Salesive blog.