Skip to main content
Belcenter AIHelp center
Administer the platform

Subscription and billing

Create a credit-based organisation or one with a reseller plan, then manage usage, payments, and invoices.

A client organisation directly attached to Beone or an authorised reseller can choose a plan. The reseller itself does not subscribe to a client offer. Existing organisations retain their current operation as long as no plan is assigned to them.

Plans and included items

Each plan belongs to a vendor. The client browses active public offers from their direct provider; a plan from another vendor cannot be assigned to them, even during an upgrade. The vendor and terms are preserved in the contract.

The following table illustrates the Beone catalogue; the offers actually displayed and the terms confirmed during subscription prevail. Authorised resellers have their own catalogue.

Plan Monthly fee excl. VAT Minutes per month Overage excl. VAT/min Bots
200 minutes 70 € 200 0,40 € 1
400 minutes 140 € 400 0,35 € 2
600 minutes 210 € 600 0,30 € 5

Your contract terms appear in Subscription and billing. A private plan assigned by an authorised vendor administrator remains visible to its beneficiary. Modifying the catalogue does not change the terms of existing contracts.

Each bot includes a BeAI number, AI usage, recording, and self-improvement. Minutes are shared across the organisation's authorised bots and voice models. The first minute of a call where the AI has started is non-divisible; the remainder is billed by the second. Minutes renew on the monthly billing anniversary, with no rollover. End-of-month dates retain their original day whenever the calendar permits.

Outbound call legs and transfers are billed separately against credit, at standard telephony rates. SMS and text usage continue to be billed according to their current rules.

Create an organisation with credit or a plan

An administrator with organisation creation rights opens Organisations → Create: a platform administrator, or an administrator of a reseller organisation within their scope. The standard form offers Prepaid credit by default. Enter the organisation and its direct provider; you can also fill in its billing details. The technical registration account for the Beone website retains its dedicated API; it does not acquire additional creation permissions.

For a provider authorised to sell subscriptions, choose Monthly subscription, select an offer from this vendor, review its terms, and tick the confirmation box. Then click Save. This creation requires no additional administrator user, no bot, and no pre-collected mandate. You create users and bots separately when needed.

The plan remains pending a payment method (awaiting_method). Open Subscription and billing to set up the payment method; only the first confirmed payment activates the minutes and starts the commitment. Saving the organisation does not trigger a direct debit or number reservation. Any change to the plan between viewing and confirming requires reviewing the new terms.

The legacy Register a website client links now open this standard form.

Authorise a reseller

Only a platform administrator can enable Enable online subscriptions for this reseller in a reseller organisation's record. Beone implicitly has this capability. The vendor must remain authorised and not archived; Picapp technical organisations do not sell subscriptions. Eligible clients are its direct, unarchived children that are not resellers themselves.

Disabling the capability blocks new subscriptions. It does not suspend contracts already signed or their management: plan upgrades remain possible within the same vendor's catalogue. The vendor administrator retains access to their offers. Each vendor keeps their own payment, billing, and sending settings; missing configuration for a reseller is not substituted with Beone credentials.

Registration from an external website

The legacy POST /api/v1/website-signups journey remains available for authorised integrations. It explicitly creates the organisation, its administrator, the initial bot, and a subscription using the Mollie references specified by this contract. It retains its checks and order tracking; it must not be confused with simple organisation creation.

The mandate is verified with Mollie. The references must belong to the same Mollie customer and to the vendor's payment account. Certain payment methods do not have an expiry date. A network issue must be resolved before confirmation; it does not mean the mandate is invalid.

The tracking distinguishes:

  • Payment pending: the initial direct debit is created, without early activation.
  • Number in preparation: payment is confirmed, the subscription is active, and number assignment is in progress.
  • Ready to receive: payment is confirmed, the number is assigned and routed to the bot, and telephony is available.

The registration can be viewed again without recreating the organisation or charging a new monthly fee. Any delayed telephony provisioning continues independently of the payment. A provider issue requiring verification appears in number tracking.

After Beone takes over a reservation, the former registration failure message is cleared once the new reservation is handled. The tracker then displays the current number status until telephony connection is confirmed. This recovery does not re-bill the first month.

Track your order

In My subscription, select Track my order. The View progress button is also available at the top of Subscription and billing: it opens the same page displayed after your first login from the website. You can return to it without reusing the initial login link, even once the bot is ready.

During provisioning, a mini tracker remains visible in the top bar: current status, number of completed steps, and direct access to details. It distinguishes pending payment, number provisioning, final checks, and required action. On mobile, it occupies a dedicated row for readability. It is hidden once the bot is ready or the contract ends; access from the subscription page remains available.

The tracking reflects confirmed steps, without promising a timeframe. It updates automatically based on the order status and pauses polling when the tab is hidden. In the event of a network outage, the indicator signals that tracking is temporarily unavailable, without inventing progress. An expired session prompts you to log in again.

The bars in the mini tracker, the subscription page, and the detailed tracking view are animated during in-progress steps. Their fill level changes only once a step is confirmed. The animation stops if a check is required, if the tracking connection is lost, or when provisioning is complete. Your device's accessibility setting to reduce animations is respected.

Only authorised administrators of the organisation and Beone can view this tracker. It applies to the registration associated with the current contract of the organisation being viewed; a subscription without an initial website order does not display this section. Opening or refreshing the tracker creates no reservation, invoice, or direct debit.

View minutes and top up

A request explicitly rejected by Mollie appears as refused, along with the technical refusal reason. Contact Beone if the payment configuration needs to be corrected, then click Settle payment. An uncertain network response remains under verification and must not be retried with a new order.

The main counter displays remaining minutes. The page details consumed seconds, reservations for active calls, billing period dates, and additional credit. Multiple calls cannot consume the same minutes. A call spanning a renewal date is split between the periods.

Credit is used after the included minutes, at the plan's single rate, regardless of the technical setup. Calls remain possible with a zero balance as long as available minutes fund their admission. Creating, duplicating, importing, and transferring a bot comply with the quota. A detached number that is still reserved still counts towards the included numbers quota.

To top up, go to Credits, using your saved payment method. You can replace it in billing settings via the Mollie flow. The top-up only becomes usable once payment is confirmed. A declined top-up does not cancel the subscription.

Alerts at 80 %, 90 %, and 100 % indicate balance, credit, and auto-top-up status. Crossing multiple thresholds simultaneously generates a single message. Auto-top-up intended for AI out-of-plan usage triggers only once minutes are exhausted, based on the wallet threshold. At 100 %, continuity depends on available credit and payment confirmation: an interruption remains possible.

Unpaid balances and invoices

A payment in progress is not a declined payment. A definitively declined monthly instalment suspends service immediately, while preserving upcoming instalments and the contractual commitment. BeAI does not automatically retry this instalment. After updating your payment method, use Settle payment on each unpaid instalment. Service resumes once all overdue instalments are paid.

Once payment is confirmed, the seller’s billing workflow creates and posts the invoice in Odoo, registers the payment, and sends the invoice. The PDF appears in Subscription and billing. This workflow applies to monthly instalments, pro rata amounts, and top-ups. An invoice that is pending or encountering a synchronisation error is reprocessed independently: it never triggers a second direct debit.

Test mode exclusively uses Mollie test, staging Odoo, and the configured staging email recipient. No test payment generates a production invoice. Live mode uses Mollie live and production Odoo; invoices and notifications are sent to the customer’s billing email address. A missing billing address halts delivery with a visible error; it is not replaced with the staging address.

For Beone, platform administrators select the mode in Subscription settings → Payments and billing, or via PATCH /api/v1/platform/subscriptions/settings with mode: "test" or mode: "live". An authorised reseller administrator configures their own payments and invoices from their catalogue, or via GET/PATCH /api/v1/organisations/{id}/subscription-settings. Mollie and Odoo keys, companies, journals, and sending email addresses are specific to that seller. Live mode must be enabled on the environment; it remains unavailable on DEV. Keys and the Odoo instance must match the mode. Once the seller records a first subscription, changing modes is rejected to preserve the consistency of mandates, payments, and invoices. Stored keys are never displayed. Saving a configuration triggers no charges.

Upgrading plans

Select a higher plan and review the quote before confirming. The additional charge and minutes are calculated based on the remaining fraction of the billing period. Additional minutes, bot allowance, and the new out-of-plan rate take effect once payment is made. The full allowance applies from the following month. The change affects neither the billing anniversary, nor the commitment period, nor any registered cancellation.

Downgrades are not permitted, including when assigning a private plan. A declined upgrade leaves the previous plan intact. If a pro rata payment is confirmed only after the end of its period, the previous plan is retained and the amount ex. VAT is credited as additional balance; the page flags this occurrence.

Cancellation

Cancelling during the first month stops the service at the end of that billing month, with no pro rata refund and no subsequent monthly instalment. After this first month, monthly instalments remain due until the end of the twelve-month commitment period. The request prevents renewal.

After the commitment period, notice is one calendar month: service ends on the first billing date occurring at least one month after the request. For example: subscribed on 17/09/2026 and requested on 20/11/2027, final direct debit on 17/12/2027, service ends on 17/01/2028.

The end date appears on the subscription page. On that date, calls cease and included numbers are released. History, invoices, and remaining credit are preserved, with no automatic refund.

Equivalent API

The same permissions and validations apply to both the portal and the API. Connected OpenAPI documentation details the fields and examples:

  • POST /api/v1/organisations: standard creation on prepaid, or with the confirmed subscription selection.
  • /api/v1/subscription-plans: seller catalogue and management by their authorised administrator; seller_id selects a seller within the account's scope.
  • /api/v1/website-signups: sign-up and tracking by ID.
  • /api/v1/organisations/{id}/payment-method/import: verified import restricted to the seller’s authorised administrators.
  • /api/v1/organisations/{id}/subscription: contract and assignment; sub-routes upgrade-quote, upgrade, cancel, undo-cancellation, retry-payment, and invoices/{invoiceId}/pdf.
  • /api/v1/credits: credit, minutes, contract, and invoices.

To create an organisation with a plan, pass an Idempotency-Key key and standard organisation fields, along with:

{"name":"Exemple client","parent_id":1,"subscription":{"plan_id":1,"plan_revision":1,"confirmed":true}}

IDs and revisions originate from the chosen provider's catalogue. Without subscription, creation defaults to prepaid. A request cannot select an offer from another seller. A reseller’s website_subscriptions_enabled option is managed in the organisation API with the same platform administrator permissions as in the GUI.

A consistent Idempotency-Key key is required when creating with a plan, registering from the site, upgrading, settling an unpaid balance, and processing a subscriber top-up. Following an indeterminate response, reuse the same key and the same payload. A different operation must use a new key. A payment still undergoing verification must not be re-initiated under a different key.

Links to top-ups and the payment method open the displayed organisation's file, including for a Beone administrator. The top-up status distinguishes between disabled, available, awaiting payment, locked after an attempt, invalid mandate, and unavailable configuration. Payment confirmation is always required before new credit can be used.

If payment for an upgrade is declined, the previous plan remains active. Calculate a new quote to try again: the earlier pro rata amount cannot be settled like an overdue monthly instalment.

Subscribing from an existing BeAI account

An administrator of an eligible client organisation under Beone or an authorised reseller can open Subscription and billing, then My plan, from the Admin menu or the credit counter. The external website is not required. Review the terms and tick the confirmation for the selected plan. Private plans remain reserved for assignment by an authorised administrator of the seller.

Subscribing keeps the organisation, its users, bots, technical configuration, existing rates, and remaining credit. No new bots or numbers are ordered automatically for an existing customer. Already reserved BeAI numbers become included upon activation, with no retrospective refund of their rental fees. The total count of bots and reserved numbers, including detached ones, must comply with the plan. An old credit subscription must be closed by Beone before subscribing: the two subscriptions cannot be combined.

First, complete the billing details. The registered mandate is verified with Mollie. If missing or unsuitable, subscription waits for a payment method: open Set up my payment method and complete Mollie verification. The first direct debit is then triggered automatically. In DEV, this verification exclusively uses the Mollie test account; copied live references cannot be reused in this mode.

Until the first payment is confirmed, your calls continue using your current credit and rates. Included minutes and commitment dates start upon confirmation. A declined initial monthly instalment can be settled directly from the subscription page. No existing organisation is migrated without an explicit subscription.

The equivalent API is POST /api/v1/organisations/{id}/subscription, with Idempotency-Key and body {"plan_id":1,"plan_revision":1,"confirmed":true}. Retrieve the current revision from the catalogue. Reuse the same key and body after an indeterminate response. Status awaiting_method indicates that the payment method must be configured using the existing billing API, followed by checking subscription status.

Managing your subscription on a single page

Subscription and billing displays your current plan and remaining minutes under My plan. The Top-ups and alerts and Payment and invoices tabs provide access to other settings without leaving this page. Details of the three views are described below.

During the first month, a banner titled You can still cancel free of charge displays the cut-off date and time, in Belgian time. This represents an option to cancel without extra fees, not a free month: the month paid remains due. Cancel during my first month displays a summary showing the termination date, the cancellation of future monthly payments, and what happens to numbers, credit, and history. Only Confirm cancellation records the request. Leaving a page open past the cut-off date does not silently apply new terms: refresh it to confirm the revised end date. Once confirmed, the banner shows the registered cancellation.

Plans are displayed side by side, with their price ex. VAT, minutes, bots, and out-of-plan rate. Switch to this plan displays the amount incl. VAT due now, the additional minutes, and the price at the next renewal, with no charge taken at this stage. Payment requires separate confirmation. The contract dates remain unchanged.

Add or replace payment method

The Payment method card displays its actual availability, its expiry date where applicable, and any pending validation. An authorised administrator can add or replace the card directly from this page. Bank details entry and validation at 0,00 € take place on Mollie, then returning reopens the subscription page. The existing mandate remains available during replacement; only the result confirmed by Mollie validates the new one. A pending status allows you to Resume validation or Cancel this validation. If billing details are incomplete, a link allows you to complete them before continuing.

Remove this payment method requests confirmation and disables auto top-up. This does not terminate the contract: monthly payments remain due, and an unpaid balance may suspend the service. Replacing the payment method is preferred when the subscription is to continue. Users without administrative privileges do not see orders or payment configuration details.

Payments and PDF invoices are consolidated in the same table. A declined, pending, or confirmed direct debit remains clearly distinct. Technical details for a decline can be expanded if required.

Corresponding API data and actions

GET /api/v1/organisations/{id}/subscription exposes first_month_ends_at and cancellation_phase (pending, first_month, commitment, monthly, scheduled, ended). Cancellation accepts {"expected_effective_at":"valeur exacte de cancellation_effective_at"}: if the date has changed, it responds 409 without recording a request. An empty body remains compatible with existing clients.

Payment operations reuse /api/v1/organisations/{id}/payment-method: GET returns in particular usable, expires_at, payments_available, billing_complete, and setup.checkout_url; DELETE removes the mandate. On /payment-method/setup, POST starts validation and DELETE cancels it. These operations retain the same services and permissions as the interface. No secret references or card details are exposed.

A single workspace: plan, top-ups, and billing

The /credits/ page, titled Subscription and billing, replaces the two former separate pages. Former /subscriptions/{id} links redirect to this area for the same organisation. For an administrator managing multiple clients, the organisation name remains visible, and all actions explicitly target that client. Buttons, links, tabs, and cards automatically adopt the active branding, in both light and dark themes. Payment statuses retain the standard application colours for success, pending, or error.

  • My plan: current package, usage, contract dates, and plan comparison. An eligible prepaid customer can choose an active public plan from their vendor without losing their bots or credit. A reseller does not see a customer package for themselves; their eligible customers see only their catalogue.
  • Top-ups and alerts: manual top-up, total incl. VAT and confirmation before payment, auto top-up (activation, threshold and amount), low credit alert, email recipients. Saving a setting does not trigger a payment. Without an explicit alert recipient, organisation owners are notified via the existing workflow. In DEV, subscriber emails are always routed to the configured staging recipient.
  • Usage history: transactions in euros and included minutes, filters, search, and pagination.
  • Payment and invoices: add or replace payment method, resume or cancel its validation, billing details, direct debits, and invoices. Credit orders placed prior to a subscription remain accessible.

My organisation retains identity details and settings specific to the organisation; a link leads to the unified billing area. Editing identity details resets neither top-ups nor alerts.

Auto top-up requires a strictly positive threshold and amount to be enabled. A setting saved with a missing mandate or an unavailable configuration remains flagged as non-operational. Minute alerts at 80/90/100 % are independent of the configurable low credit alert.

GET/PATCH /api/v1/organisations/{id}/billing-preferences exposes and updates sections billing, auto_recharge, and low_credit_alert. Omitted sections are preserved. Example: {"auto_recharge":{"enabled":true,"threshold":10,"credits":50},"low_credit_alert":{"enabled":true,"threshold":20,"emails":["compta@example.be"]}}. Only authorised administrators for this organisation can view or update these settings. Validation is shared with the existing organisation update.

Change your mind after cancellation

As long as the effective end date and time have not been reached, My plan displays Cancel my termination in the scheduled cancellation card. Open the summary, then select Confirm continuation of my subscription. This action is restricted to authorised administrators for the organisation.

You keep your plan, minutes, bots, numbers, and commitment and renewal dates. No immediate charge is triggered. Any suspension for non-payment remains in effect until overdue monthly payments are settled. Once the effective end date is reached, the cancellation can no longer be withdrawn: a new subscription is required and former numbers may have been released.

An email confirms the cancellation, its end date, and any monthly payments still due. It contains Keep my subscription for customers who change their mind. The button opens BeAI and prompts for sign-in and confirmation; opening the email or its link never alters the contract. An outdated link cannot withdraw a more recent cancellation. A second email confirms that the subscription continues after the request is withdrawn.

Confirmations, minute alerts, unpaid balances, and number notifications use the colours, name, and support contact of the organisation's branding. Messages remain readable in plain text. Odoo invoice emails reflect the identity of the vendor's issuing company. In DEV, subscriber communications are sent solely to the configured staging recipient. Delivery downtime does not invalidate the recorded decision: the notification remains queued to be retried.

Cancellation withdrawal via API

GET /api/v1/organisations/{id}/subscription provides can_undo_cancellation and cancellation_revision. Call POST /api/v1/organisations/{id}/subscription/undo-cancellation with {"expected_cancellation_revision":1} using the received revision. The updated contract is returned. A duplicate call after success has no effect and generates no new confirmation. An obsolete revision or an effective end date that has already passed returns 409; a missing or invalid revision returns 422. The same permissions are required as in the GUI.

When submitting a new cancellation, /cancel also accepts expected_cancellation_revision with expected_effective_at to prevent an outdated page from confirming an obsolete decision.

Welcome clients registered from the website

The marketing website can create the account, its administrator, a customised AI assistant, and its subscription in a single operation. After the first payment is confirmed, BeAI automatically reserves the included number and processes the invoice. The website developer has access to the complete integration guide, with JSON bodies, idempotency, errors, and staging acceptance criteria.

The welcome page displays four live steps and updates automatically. It announces Your bot is ready! once the number is active and telephony is available, then offers to call the number, Edit my bot, or open Subscription and billing. Any required vendor verification remains visible without prompting you to restart registration. The invoice may arrive after the number and never triggers an additional charge.

For a registration created via the website integration, the overview, opening hours, and website fields populate the bot preset. Tracking offers Create customer login link: this initial link is single-use, expires in ten minutes, and can only be issued during the first 24 hours of registration, by its creator or a platform admin. A new link invalidates the previous one. The client can then use their usual sign-in method. The link is confidential: provide it solely to the client concerned.

Usage history: euros and minutes

In Subscription and billing → Usage history, authorised organisation administrators can view transactions from newest to oldest. The Unit filter lets you choose euros, included minutes, or both. The Movement filter distinguishes debits from credits; search covers the description or the assistant name. Results are paginated, from 25 to 100 rows per page.

Euros include confirmed top-ups, adjustments, and billed usage (calls, SMS, text conversations, etc.). Amounts are excluding VAT (excl. VAT); small debits show additional precision. A reseller transfer appears once, as a credit or debit depending on the organisation viewed. Minutes include allocations for each period, paid plan add-ons, finalised usage, and the expiry of unused minutes. Their duration is displayed in minutes and seconds, along with the relevant period and the assistant where available. Usage with overage may generate both a movement in minutes and a movement in euros.

Reservations for ongoing calls are not final debits: they continue to be tracked in the plan counter. The history updates once the call or processing has ended. Expiry is displayed when all calls for the period have finalised. Viewing this history does not trigger any charges and does not alter balances. Payments and invoices remain on their separate tab. A search with no results displays an empty state; reset filters to view available movements again. Non-admin users and accounts outside the scope do not have access to this history.

The equivalent API endpoint is GET /api/v1/credits/movements?organisation_id=42&unit=all&direction=all&page=1&limit=25. Parameters: unit=all|eur|minutes, direction=all|credit|debit, search (up to 150 characters), page starting from 1, and limit from 1 to 100. Without organisation_id, it uses the API account's organisation. The same permissions apply to both the portal and the API.

Each movement returns occurred_at, type, direction, amount_eur (signed string with six decimal places, or null), amount_seconds (signed number of included seconds, or null), description, the period, and the assistant if known. meta contains pagination and filters. An invalid filter returns 400; unauthorised access is rejected with 403/404. The legacy response GET /api/v1/credits remains compatible; use /credits/movements for unified history.

Get guided setup help

Choose Create with assistant, or Customise with the assistant after signing up. BeAI prepares a draft through a live text or voice conversation, with interruptions supported. The first session for a new bot is offered free of charge by Beone within the stated limits; any paid repeat use requires your agreement. You review and confirm before changes are applied. See Configure by conversation.

Return to ordinary prepaid billing

An administrator authorised to manage the organisation’s billing opens Subscription and billing → Return to prepaid and history. The same workflow covers the 70 / 140 / 210 EUR plans and the seller’s other plans. It does not recreate the customer, bots or numbers.

Choose End of the current period (the default for a started contract), or Immediately after confirmation for an approved commercial correction. A request that has never been paid is withdrawn immediately; it may already use prepaid without its enrolment request being withdrawn. Withdrawal prevents automatic resumption after a mandate is added. If the contract has already ended or its end date has passed, the preview proposes an immediate return; it does not invent a new period end.

Review the preview: current mode, plan, payment, period, used and remaining minutes, next billing date, wallet, prepaid rates excluding VAT and top-up settings. The prepaid rate is the organisation’s configured rate; it is never copied from the plan’s overage rate. A missing voice rate or insufficient balance is highlighted: normal rules may refuse new calls. Number rentals keep their usual rules and dates.

Enter a reason, approve the commercial consequences and confirm. The signed preview expires after 10 minutes; changes to displayed information require a fresh preview. The paid month and unused minutes do not create an automatic refund, credit note or cash conversion. Outstanding payments and historical commitments must be reviewed with the seller; the change neither settles nor cancels an earlier debt. The transition triggers no payment or top-up and does not remove the mandate.

A scheduled transition remains visible and can be cancelled before its effective date. If a payment is open or uncertain, an immediate return is refused; at the scheduled date, tracking shows Payment reconciliation required. It does not present prepaid as confirmed before resolution. No new subscription payment or allowance for a new period is created after the cutoff. Once the normal payment processing reconciles it, local application resumes without duplicating the operation.

Calls already admitted retain their contract, rate and reservations. They can finish using minutes from their original period and the previously accepted overage rate; no new allowance period is granted after the cutoff. New calls switch to prepaid once application is confirmed. Admissions and the transition are serialised to prevent duplicate charges. Past conversations and invoices are never recalculated.

The history shows the actor, reason, requested date, local confirmation date and status of each transition, along with previous contracts, payments and invoices. Another subscription can be taken out later without deleting the previous contract. The wallet, top-up settings, bots and their configurations are retained.

The API uses POST /api/v1/organisations/{id}/subscription/prepaid-preview with timing: "period_end" or timing: "immediate", then POST /api/v1/organisations/{id}/subscription/prepaid-transitions with the full preview, reason, confirmed: true and Idempotency-Key. After an uncertain response, resend exactly the same object and key. GET /api/v1/organisations/{id}/subscription/prepaid-transitions reads the mode and history; POST /api/v1/organisations/{id}/subscription/prepaid-transitions/{transitionId}/cancel with {} cancels a future transition. Permissions and scope match the console; changed conditions, an elapsed date or an unreconciled payment returns 409, invalid input 422.

An older top-up that had not yet been sent for payment must be reviewed separately with the seller. It is not started automatically after the transition. A top-up whose payment is already in progress must first be reconciled; new prepaid top-ups then follow their usual workflow.

Documentation updated with the application