Skip to main content
No. Billing only starts counting from the first connection of a WhatsApp on the instance. An instance created and never connected produces no cost and does not consume the trial.
The instance becomes billable automatically, with nothing for you to do. At the moment of the switch, the API emits the enterprise.instance.billable event with reason: trial_converted. About 24 hours earlier, you receive enterprise.trial.ending so you can warn your customer.
Yes. Call PATCH /api/instance/billing/:instance with {"billingMode": "billable"}. The instance starts being billed from that point, with no free days.
The trial is granted once per number. A number that already trialed goes straight to billing when it connects again, without blocking instance creation. The waiting period to trial again, if any, depends on your contract.
One invoice per month, summing the usage of all your instances. You pay at least your plan’s monthly credit, and you pay for the usage when it exceeds that credit. See How billing works.
It commits the amount proportional to the days remaining until renewal. An instance that became billable on the 20th of a 30-day cycle commits about 10 days, not the full cycle.
That instance’s committed amount is not refunded, it runs until renewal. Deleting frees the slot to create another instance, but does not reduce the current cycle’s invoice. See How billing works.

Next

How billing works

The full model, with examples.

Billing control

Force billing or keep an instance on trial.