Skip to main content
Version: Current guides

Manage your account, contacts and wallets

Identify what you are managing​

An InvisiPay account, its blockchain wallets and the addresses within a wallet are different objects. Changing an email does not move wallet assets; renaming a wallet does not change its address. Sign-out, local reset, wallet deletion and account closure are also different operations. See Local unlock for local password rules.

Bind a phone or email for the first time​

If your current version provides this entry, open the phone/email item in security or two-factor settings.

  1. Check the signed-in account. Enter an email you control, or select the correct dialing code and enter your phone number.
  2. Read the verification instructions after submitting. Look for a code sent to the target email or phone only when the screen explicitly says one was sent. If it requests an authenticator code, use the authenticator already linked to this account.
  3. Enter it only in the current app verification screen. Do not mix codes from sign-in, contact changes or other actions. Not every binding attempt sends a target-contact code; do not repeatedly request SMS during an authenticator step.
  4. Wait for explicit success, return to settings, refresh and check the masked contact. Follow errors for an already-used contact, delivery failure or expired verification rather than creating another account as a substitute.

The relationship between contact binding and enabled verification methods depends on the current screen. A visible switch does not establish that SMS verification can be disabled independently.

Change an existing contact​

If your version provides Change phone/email:

  1. Open Change on the original contact, check the masked information and follow the instructions to verify control of the existing contact first.
  2. Once verified, enter the new email or phone number. Do not unlink the original method first and then try adding another.
  3. Complete verification of the new contact and any additional checks requested, then wait for confirmed success.
  4. Return to settings and verify the new information. For a card application, return to the original application and use its offered correction/resubmission action. Changing account contacts does not automatically update an old application snapshot or exempt it from another review.

If the original phone or email is inaccessible, use an alternative verification or official support route actually offered by the app. There is no promise that verification of the old contact can be skipped. If the new contact is already used, verification expires, connectivity fails or the result is unknown, refresh the current binding before continuing rather than repeatedly unlinking. A failed screen does not prove the old method was removed.

Two-factor verification and account sign-in password​

If your version provides authenticator setup, choose Bind in security settings, scan the QR code or enter the setup key in an authenticator app, then submit its generated code in InvisiPay. The setup key and QR code are sensitive; do not send them to support or anyone else. Seeing a QR code alone does not complete binding. Return to settings to check the actual status.

Before unbinding an authenticator, check that a usable sign-in method remains and complete the checks on the current screen. Deleting the authenticator from your phone does not disable account verification. If a code fails, check the chosen account, whether the code has changed and device time settings, then follow any lockout instructions. Disabling security should not be the first troubleshooting step. Do not assume recovery codes work for every binding or contact-change check.

If your version provides Change account sign-in password, verify the current sign-in password, follow the requested new-password rules and wait for success. If forgotten, use account recovery with verification methods you control. Changing the sign-in password does not reset the local wallet unlock password or recover private keys.

Switch, name and add wallet accounts​

If your current version provides this entry, open the wallet from the selector or wallet management.

  1. After switching wallets, select the account you actually use within it. Check its full address, network and signing capability. Read-only accounts and externally connected wallets have different capabilities.
  2. If renaming is available, choose a recognizable wallet or account name and check that the address is unchanged after saving. Names can repeat and do not prove identity.
  3. If a seed-phrase wallet offers Add account, complete local verification and the requested association/signature. Wait until the account appears in the list before using it. Resolve a failed association in the original flow rather than repeatedly adding accounts to recover an old address.
  4. Before receiving at a new account, copy and verify its full address and check recovery material using Backup and recovery. The primary account and later derived accounts may offer different removal actions.

View a private key or remove a wallet​

If your version provides View private key/Export, use it only when needed for backup or migration. Open the correct account details, verify the full address, read the warnings and complete app identity verification. View it without observers or recording and leave the screen immediately afterward. A private key usually covers one account and does not replace the whole wallet's seed-phrase backup. External or read-only accounts may not allow export here.

Perform any necessary import only inside a destination wallet you have verified. Do not paste keys into websites, support chats, ordinary notes or shared clipboards. Automatic hiding, screenshot protection and clipboard clearing are not guarantees that a secret remains safe.

ActionCheck before proceeding
Remove a derived accountIf offered, check assets and future receiving needs first. Unlinking and hiding do not destroy on-chain assets, and Add account does not guarantee the same address returns
Delete an entire walletVerify an independent backup restores every account still needed, check pending settlement, read the actual deletion scope and verify. You may lose the only local signing material
Disconnect an external walletIf offered, follow the prompt and check the connection status. This does not revoke on-chain permissions already signed in the original wallet

If an action is blocked because it is the last sign-in credential, verification failed or unlinking failed, retain a usable sign-in method and resolve the original operation. Do not clear local data to bypass the restriction.

Delete one cloud backup​

If your version provides this entry, select the correct wallet's cloud-backup status, check its address and cloud account, request deletion, complete app identity verification and wait for the result. Verify another independent recoverable backup first. Do not delete the last recovery copy as troubleshooting.

This removes the selected wallet's cloud backup, not its local wallet, other wallets' backups or on-chain assets. After failure or timeout, refresh the status before continuing. See Backup and recovery for passwords and recovery methods.

Sign-out, local reset and account closure​

NeedDifference
Leave temporarily or switch accountsSign out; this is neither account closure nor cloud-backup deletion
Clear this installation's dataFollow Full local reset only; it may affect all local accounts and does not close the remote account
Close the InvisiPay accountRequires the service's account-closure process, not wallet deletion or uninstalling

If your current version provides Close account, read its current deletion scope, potentially retained data and formal privacy policy first. If no entry is available, ask verified official support about account closure or personal-data requests.

Before proceeding, create and verify independent backups, retain necessary non-secret order information and address active cards, in-progress payments and pending settlements. If the screen identifies these as blockers, resolve them in the relevant service rather than repeatedly submitting. Complete the requested checks only inside the app and wait for an explicit result. A timeout or failure does not establish that closure completed.

Account closure does not reverse broadcast transactions or erase blockchain records. Do not assume local keys, every cloud backup and card, KYC or billing records are all deleted simultaneously. Actual deletion, retention scope and processing time must follow the formal privacy policy and confirmed handling information. Closure does not recover lost seed phrases or passwords.