Decide which access you actually need
Start with the intended driver rather than the seller’s demonstration. List ordinary physical access, any phone-based access offered, remote status viewing and remote convenience functions separately. A buyer may accept the car without one optional online service but still require complete control over authorised access. State that distinction before agreeing the offer or paying for an additional service package.
For a dealer buying several cars, identify who will initially receive each vehicle and who will eventually become its user. A dealer account used during preparation is not automatically the right long-term arrangement. Record the responsible person for each handover stage without collecting passwords. The i60 software and support guide covers the broader question of which features are supported at the destination.
Ask for the supported transfer route
Request instructions from the service provider responsible for the vehicle’s account functions. Establish whether the current registered user must participate, which ownership evidence is required and whether the intended buyer can meet the applicable registration requirements. A seller’s general assurance that an account can be changed is incomplete until the relevant provider confirms the process for that particular situation.
Keep the procedure and the outcome separate. Receiving a list of instructions does not mean a previous association has been removed or that a new association has succeeded. Ask who completes each step, when it will happen and what evidence can be shared without exposing personal information. Do not accept a borrowed identity, someone else’s login or a continuing dependency on the seller’s private phone as an unexplained substitute.
Separate keys from account permissions
Count the physical keys and other explicitly included access devices, and demonstrate each supplied item on the selected car. Record anything missing. If additional digital permissions are offered, ask how their status can be checked and how previous permissions are revoked through the supported process. A pair of working physical keys does not, by itself, answer whether another person retains an online association.
Avoid inferring that every i60 has the same digital-key equipment or account controls. Specify only the functions actually fitted and supported. For a used car, distinguish removal of prior users from deletion of saved destinations, contacts or media. A general reset may affect preferences without completing every provider-side ownership change; ask for confirmation of the result that matters instead of treating a reset screen as sufficient proof.
Test with the receiving user’s arrangement
Where legitimately available, demonstrate agreed functions using the receiving user’s own supported account and device. Note the app version, vehicle reference, date and network context. Test a small set of agreed actions rather than relying on a successful login alone. Keep sensitive screens out of the inspection file, and let the account holder enter authentication details privately.
A source-market demonstration does not establish overseas service availability. If the destination cannot be tested before shipment, separate completed ownership steps from unverified regional services. The phone connection and language checks address another independent requirement: connecting a phone for media or navigation. Bluetooth or projection working in the cabin should not be recorded as proof that a remote vehicle app will also work.
Put unresolved access into the purchase terms
For each essential item, write a result and the action needed to close it. For example: two physical keys demonstrated; previous account release awaiting provider confirmation; destination remote status service not verified. Decide whether an unresolved item prevents acceptance, requires a different candidate or is an explicitly accepted limitation. This gives both parties a concrete decision rather than an open-ended promise to fix the app later.
For new vehicles, ask how first-user activation will be handled and whether any preparation account has already been associated. For used vehicles, ask about the prior-user release as well as the next-user setup. Neither the word new nor an empty-looking display proves the account state. Any paid support should identify its scope, responsible provider and terms instead of being described as permanent connectivity.
The physical-key supply assessment keeps physical access separate from app eligibility and authorised receiving-user setup.
Keep a useful handover record
A practical account handover record contains the vehicle reference, key count, completed provider steps, demonstration results and remaining limitations. Include a contact route for agreed support. Store confirmation references with the vehicle handover file, but leave passwords, recovery codes and unnecessary personal documents out of a shared inspection report. The buyer should retain control of their own credentials.
If the seller can show an app but cannot establish a legitimate transfer route, the unresolved issue is ownership and service access, not simply a missing tutorial. Compare another candidate or revise the accepted feature scope before purchase. A clear result protects the receiving dealer from promising customers functions that still depend on a previous owner’s cooperation after the vehicle has already arrived.