Rate this page:

Child accounts

Learn how to understand user and account management to design your application properly.

Account users

Copy URL

Voximplant application users are the end users of the application, and Voximplant developers can control each user account balance by setting the parent_accounting parameter to false (via the AddUser and SetUserInfo methods) or specifying this setting in the control panel (the Separate account balance checkbox) while creating/editing the app user.

User creation

It is possible to transfer funds from the developer account to an app user account and back via the TransferMoneyToUser method.

Independent child accounts

Copy URL

Let us imagine that a developer is building a Cloud PBX service where every company has its own account balance and controls users account balance (if required). The developer has their account balance where they put funds to divide them up among the companies.

For this type of service, Voximplant offers child accounts that are created by the developer with the help of their parent account credentials. To create a child account, use the AddAccount method.

Please note

This functionality is disabled by default, and developers need to ask Voximplant team to enable it.

Purpose

Copy URL

Child Accounts operates as standalone entities, they do not share applications, scenarios, and balance with each other. They, however, have access to the parent's scenarios. Creating a child account is handy when you need to separate your customers, so each child account can represent each customer, but there is only one parent account "to rule them all".

In terms of balance, transfer funds to child accounts' users via the aforementioned TransferMoneyToUser method.

Thus, the chain of events for adding the funds looks like this: Developer's card / wire → Child account balance → App user account balance.