Transfer a BYD Song Plus App Account Before Handover

Identify the account service that belongs to the candidate

Ask for original market, vehicle identity, official app name, publisher and supported registration route. A BYD European app reference provides regional context; it does not prove eligibility for a China-market Song Plus shipped elsewhere. Keep the applicable instructions with the candidate rather than choosing an app because its logo looks familiar. The Song Plus naming and version guide separates DM-i, EV and market records. Confirm where the seller demonstration takes place and which account is used. Mark regional access unknown until the intended buyer can establish it through a legitimate supported process.

Confirm former-user removal with the relevant provider

Ask how the original owner or supplying dealer releases the vehicle from the relevant account. Establish who must initiate the process, which proof is needed and whether the applicable distributor handles a change of ownership. Do not equate a local screen reset with removing every server-side or shared-user permission. Obtain a dated confirmation through the official service route without collecting passwords. If the seller cannot explain the procedure, keep the transfer unresolved before payment. A supplied account belonging to someone else is not an appropriate long-term ownership solution, even when the buyer can temporarily open the app and see the vehicle. BYD Europe explains that its service supports one bound owner with separately authorised users. Its FAQ also directs activation questions to the dealer rather than unsolicited activation-email links. Retain that regional context; do not convert it into universal China-car eligibility.

Test the buyer account without credential sharing

Where supported transfer is available, let the buyer use their own phone, contact details and credentials. Record whether registration, pairing and the required functions actually work, distinguishing a downloaded app from a paired vehicle. Protect personal information in screenshots and use an agreed secure channel where official identity verification is required. Do not send passports, passwords or one-time verification codes through the public sourcing form. The enquiry privacy policy explains that collection boundary. A successful origin-country test is still not proof of every destination function; state the location and conditions under which the result was obtained.

Keep physical access and phone projection independent

Demonstrate each supplied physical key without the other nearby, plus normal door access and vehicle operation through the supported procedure. App convenience, digital-key availability and smartphone projection are separate questions. The phone-projection checks assess in-car connection without promising remote services. Ask how the owner uses the vehicle if a phone is lost or connected service is unavailable. A failed app pairing does not automatically diagnose a vehicle hardware fault. Likewise, functioning physical keys do not prove that former-owner remote access was removed. Preserve a separate result for each acceptance item.

Check service availability after export

Ask the relevant market support provider which functions, subscriptions or connectivity arrangements apply to the actual VIN and destination. Do not assume a local distributor must activate a parallel-import vehicle, or that a seller workaround is a permanent supported route. Keep screen language, phone integration, navigation, remote control and data service in separate rows. The overseas warranty and support guide helps record who can assist when the vehicle and service regions differ. If the buyer accepts unavailable convenience features, state that explicitly instead of listing them as confirmed value in a quotation.

Retain a clear handover and privacy record

The final account record should identify the VIN, official service route, former-user removal status, buyer registration outcome and exceptions. Preserve version information and relevant test evidence before supported resets. Remove local phone pairings and personal destinations according to the applicable instructions, without losing important diagnostic or vehicle inspection records. Reopen the review if the candidate changes. Use the first-month ownership checks to compare arrival results with the accepted origin record. An app promise in an informal chat should not replace a written explanation of what works, where it was tested and who resolves any outstanding transfer.

Example: a dealer login works but buyer registration fails

Suppose the seller demonstrates remote functions using a dealer phone but the intended owner cannot complete registration. The demonstration establishes one account result, not buyer eligibility. Ask the supported provider to explain the candidate registration and transfer boundary before valuing the feature. If legitimate activation cannot be confirmed, compare the car on the functions that are actually usable and disclose the limitation. Do not inherit a dealer password as the permanent solution. Physical-key operation and local phone connection should still be inspected independently so a connected-service gap does not obscure an unrelated vehicle fault.

Buyer checklist

• Actual vehicle market and official app identified
• Supported former-user release confirmed
• Buyer registration and pairing result recorded
• Physical keys and projection tested separately
• Destination exceptions disclosed

Buyer questions