Choose the workflow and prepare your information

Choose the correct page

Use /register for a new account invitation, /recharge to add cloud credit and /transfer to move credit between accounts of the same provider. The floating SMS and Telegram entries serve different tasks; they do not replace account registration or the recharge form.

What each workflow requires

Invitation — Prepare: Provider, accessible email; Alibaba also requires PH or HK region. Successful hand-off: An invitation result/link, followed by provider-side registration

Recharge — Prepare: Provider, registered email or account ID, positive whole-number recharge amount; optional referral/promo code. Successful hand-off: A payment order and its verification value

Transfer — Prepare: Provider, distinct source/target IDs or emails, applicant, amount and both email holders. Successful hand-off: Application ID, verification value and dual-email verification

SMS service — Prepare: An enabled cloud platform/country, cloud account ID and sufficient credit. Successful hand-off: A charged task with number, expiry and status

Provider support and account association

Invitations have Tencent Cloud International, Alibaba Cloud International and Volcengine International paths. Recharge currently accepts Tencent and Alibaba; the Volcengine recharge path is explicitly disabled. Transfers accept Tencent-to-Tencent or Alibaba-to-Alibaba. An account must be registered and associated correctly on the provider side before verification can find it. If one email matches several accounts, use the exact account ID.

Separate the identifiers

Tencent uses an account UIN and Alibaba uses a UID. These identify the cloud account, not a recharge order. A recharge lookup needs the verification value returned with that order. A transfer lookup needs its 8-digit application ID plus verification value. Email codes authorize the transfer and expire; they are not a replacement for the persistent lookup value.

Keep a private operation record

After submission, copy the provider, account ID, requested amount, order/application number, time and verification value to a private record. The browser may retain some active-task information, but do not rely on a tab staying open or local storage surviving cleanup. Keep verification values and email codes out of group messages and public screenshots.

Read the result before repeating an action

An invitation sent, payment received, email verified and credit allocated are separate stages. A spinner or pending state is not an instruction to submit or pay again. Use the original lookup result; retry only the failed or expired step shown by the page.