Recipient-based methods
Trades, gifts, mail, and player-ID top-ups direct an outcome to a named recipient. Verify spelling, server, platform, region, quantity, and in-game fees before the handover. These methods often avoid password sharing.
Code-based methods
A code is delivered first and redeemed separately through an official interface. Compatibility and unused status matter more than a screenshot of the code. Never expose a valid code publicly while seeking verification.
Participation and account-access methods
Coaching and self-play keep the customer involved. Account-play transfers control and adds credential, privacy, location, recovery, and publisher-policy risks. Choose the lowest-access method that meets the goal.
Sources and review note
This page is reviewed for clear risk language and beginner usefulness. Publisher rules can change; use primary rules for game-specific decisions.
Suggest a correction