Five steps at a glance
| Step | What you do | Output |
|---|---|---|
| 1 Write a spec | Entity, country, fresh or aged, empty or apps, category | A verifiable spec |
| 2 Match a sheet | Other side states account fields and transfer eligibility | A written account sheet |
| 3 Verify on your device | You log into Console and compare item by item | Check records and screenshots |
| 4 Pay and hand over | Official owner transfer or written agreed handover | Permissions and recovery in your hands |
| 5 One-week follow-up | Review permissions, payments, keys and policy status | Acceptance record |
Each step has a clear output; without one, do not move on.
Step one: write a spec, not a price question
A good spec includes account type, country, required create date, whether apps are needed, app category, preferred handover and timeline. For restricted categories confirm the account type first; see the finance, health and VPN guide. The first message carries no passwords, ID or codes.
Also useful in this topic cluster:
Steps two and three: sheet and verification
An account sheet turns the account into fields: entity type, create date, app list, policy record, member permissions, payments profile and recovery routes; see the buyer checklist. After getting it, do not rely on screenshots — log into Console yourself and tick items off against the sheet.
- Verify on your own device and network
- Do not do critical steps in the other side's remote desktop or screen share
- Pause on any difference and ask for a written explanation
Step four: order of payment and handover
Agree the order after verification passes and write it down. Prefer official owner transfer; where impossible, understand the credential-handover risk and align the six fields.
- Verification passes; confirm the route
- Agree payment milestones, cool-off, verification and timeline
- Start the official transfer or agreed handover
- You take over recovery info, two-step and member permissions
- After handover is confirmed, settle any balance as agreed
Step five: one-week follow-up
Use the first-week guide for hardening and review: permissions, payments, policy status, upload keys and a test upload. If anything disagrees with the sheet, report it in writing immediately.
Register yourself or buy?
| Dimension | Register yourself | Buy an account |
|---|---|---|
| Cost makeup | Official fee plus your time | Terms discussed by spec, plus verification time |
| Timing | Personal needs closed testing; organization needs verification | Depends on spec; may shorten some steps |
| Control | You own the whole history | You must verify history and handover |
| Best for | Time available, no restricted category, willing to follow the process | Need a specific entity or country or taking over apps |
| Main risk | Verification rejected, too few testers | Improper handover, inherited history |
If you have time and no special need, registering yourself is often safer. See the fees guide for the official fee.
When to stop
Pause if they refuse written statements, rush you to pay, ask for ID or passwords or cannot explain recovery routes. See the guide on guaranteed-approval pitches for more signals. The process exists so you have chances to stop.
Related reading:
Related
Related desks