iap_buy_more_credits

Odoo's pay-per-use services, SMS, lead mining, partner autocomplete, snailmail, all bill against IAP credit accounts, and every one of their settings panels needs the same two links: one to the service's account where credits are bought, one to the list of all IAP services. Rather than duplicating buttons, core ships this widget in the iap module and reuses it seven times.

Because it is a view widget, it attaches to no field and carries no record data. The component reads two attributes: service_name, which it passes to a silent iap.account.get_account_id ORM call when the first button is clicked, then opens that account's form view; and hide_service, which suppresses the second button. The second button simply fires the iap.iap_account_action window action.

One template detail with real-world consequences: both buttons carry the o-hidden-ios class, so these purchase entry points do not render inside Odoo's iOS app, in line with Apple's in-app purchase rules.

If you operate Odoo with SMS notifications, lead enrichment or document digitization, credits are a consumable your admins occasionally top up under time pressure, usually when messages stop sending. This widget is the door they walk through, so it is worth knowing two operational facts about it.

First, the button does not buy anything; it opens the right iap.account record, and the purchase flow starts there. If your users report "the buy button does nothing", the account lookup is the thing to debug, not a payment issue. Second, because the widget resolves the account by service name at click time, multi-company setups where IAP accounts differ per company behave correctly without any per-view configuration.

For custom modules that consume IAP services of your own, reusing this widget in your settings view gives users the exact pattern they already know from SMS settings, one attribute and zero custom JavaScript.

Standard usage in a settings view

<widget name="iap_buy_more_credits"
        service_name="sms"/>

Renders both links for the SMS service account.

Credits link only

<widget name="iap_buy_more_credits"
        service_name="partner_autocomplete"
        hide_service="1"/>

Only Manage Service & Buy Credits renders; the services overview link is hidden, the pattern core uses inside focused dialogs.

Reading the click handlers precisely prevents the two standard misdiagnoses.

The credits button is a lookup plus a navigation. It calls iap.account.get_account_id with the service name through the silent ORM (no error dialog on failure), then opens the returned id as a form view. Server-side, that method finds or creates the account for the current company; the widget itself has no idea whether credits exist, so it never shows balances.

The services button is a plain action. It executes the iap.iap_account_action window action, the same list you reach through Settings. Nothing about the current record is involved, which is consistent with the widget being a view widget: give it standardWidgetProps and it renders anywhere a form renders.

The name oversells it. No credit purchase happens in this component; naming aside, it is two navigation buttons with an account resolver. The purchase itself is handled by the IAP account form and Odoo's hosted flow from there.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The development branch is unstable until release, and we re-verify this page against the shipped version.

For this widget the branch currently shows no change whatsoever: the 19.0 file is byte-identical on master, attributes, handlers, template reference and registration included. Custom views using it should carry into Odoo 20 without edits, subject to the usual re-verification when the release ships.