Accounts and merging

Credits, works and connected Agents all belong to one Beatra account. An Agent can only spend the credits of the account it is connected to, and two accounts cannot share credits.

One account can have several sign-in methods. Any of them opens that account; a method you have never bound to it opens a different account.

Bind your sign-in methods

Bind every method you use under Settings → Sign-in methods in the console, or Me → Settings → Sign-in methods on your phone. Once linked, signing in with any of these opens this account.

• An account has at most one of each kind: one WeChat, one phone number, one email address.
• A phone number, email address or WeChat that already signs in to another Beatra account cannot be bound directly. You can merge that account in instead.
• When an account has only one sign-in method, that method cannot be unlinked.

Reminders at sign-in

The sign-in page names the account you used before:

• "Last signed in: …" is the account this device last signed in to.
• Opened from a top-up link your Agent gave you, it shows "Your agent uses this account: …" and opens that account's sign-in method.

If the method you just verified has no Beatra account yet, and this device has signed in to another account before or you came from your Agent's link, the page does not create an account straight away. It asks first. For a phone number, the title reads "This phone number has no Beatra account yet", with two buttons:

• "Sign in to that account and bind this phone number": signs you in to your existing account and binds the phone number once you are in, with no second code. From then on, either method opens the same account. If that account cannot take this kind of method (it already has one, or it bound one within the last 30 days), the button reads "Sign in to that account" and only signs you in.
• "Create a new account": makes a new account. A new account keeps its own credits, works and connected Agents, separate from that account.

These pages name an account by its masked phone number or email, such as 138****0000 or a***@example.com. An account with only WeChat reads "WeChat account · joined Oct 7, 2026". The sign-in page never shows nicknames.

Reminders at top-up

Credits belong to the account they are added to, and only that account's Agents can spend them. So every top-up screen says which account that is:

• The wallet and the payment window show "Adding credits to: …". If that is the wrong account, use "Switch account": you sign out, sign in to the other account, and come back to the same top-up screen.
• Opened from your Agent's top-up link while you are signed in to the account it uses, the line adds "(the account your agent is connected to)".
• If you are signed in to a different account from the one your Agent uses, the top of the page says "The account your agent is connected to (…) does not match the signed-in account." You can:
  • Switch to the Agent's account and add credits there ("Switch to your agent's account", or "Sign in to that account"). After a one-tap switch the page notes which account you came from, and "Switch back" takes you back.
  • Choose "Add credits to this account instead". The payment window repeats: "Your agent cannot use credits added to this account."
  • Choose "Merge the two accounts". The credits end up together, and the Agent can use them.

The top-up page on your phone shows "Adding credits to: …" and "Switch account" too.

Merge two accounts

If you already have two accounts, merge them into one: credits, membership, works and connected Agents end up together, and every sign-in method of either account opens the merged account.

What comes over

Comes together

• Credits, paid and gifted, and membership
• Works, voices and presenters
• Invoices and invoiceable orders
• API keys, which stay valid
• Connected Agents. Those connected to the account that stays need no new authorization. Those connected to the other account reconnect once: next time you use one, open the link it gives you, sign in and choose Allow.

Doesn't come over

• The other account's unused sign-up gift credits (one sign-up gift per person)
• A second free first video (one per person)
• The other account's nickname and avatar
• The country or region setting: it follows the account that stays

When a merge has to wait

The preview says why a merge cannot go ahead yet. The usual reasons:

• Works are still being made, or results are still being sent to your callback URL. Merge once they finish.
• An order is still being paid, or a refund or invoice is being processed. Merge once it is done.
• An account can merge at most 3 accounts in 30 days, and two accounts that have both merged others before cannot be merged for now.
• The credits need a manual check, or the page asks you to contact support: email support@beatra.ai.

After a merge

• Every sign-in method of the other account now opens the account that stays.
• Pages still signed in to the other account ask you to sign in again: "Your two accounts were merged. Sign in again with any of your sign-in methods."
• Credits that moved over show in Billing → History as "Merged in from another account".

For Agents

• When credits run out, details.top_up_url on the insufficient_balance error and the topup_url returned by beatra.wallet.get open the top-up page of the account the Agent spends from. Hand the link to the user unchanged: do not rewrite it to another address or drop its query parameters. The page uses it to recognize the Agent's account and warns a user signed in to a different one. The account mark in the link is encrypted and carries no phone number, email address or other personal details.
• If the user says they added credits but the balance has not moved, they most likely added them to another account. Ask them to open the same top-up link again and check "Adding credits to: …", or suggest merging the two accounts.
• After a merge, an Agent connected to the other account must be authorized again once: as on first connection, give the user the authorization link, and they sign in and choose Allow (see Quickstart). API keys used for REST calls keep working and need no change.