Skip to main content
If the same person ends up with two Agentcard accounts (one under an old email, one under a phone number), linking joins them into a single account. You prove you control the other identifier with a one-time code, then one of two things happens:
  • The identifier belongs to another Agentcard account: the two accounts merge. Cards, balance, identity verification, and history all end up on one account, and both identifiers sign in to it afterwards.
  • Nothing uses the identifier yet: it is simply added to your current account as a second email or phone.

​
When you need this

  • Identity verification was rejected as a duplicate. Your documents are already verified on another Agentcard account, so re-submitting them can never succeed. Linking that account is the fix: after the merge your verification carries over, with no new documents needed.
  • You want one account. You signed up twice (a different email, or email vs. phone) and want your cards, balance, and history in one place.
When verification is rejected as a duplicate, the verification page at app.agentcard.sh/dashboard/verify shows a Link that account flow inline: enter the other account’s email or phone, then the one-time code it receives.

​
Merge semantics

  • The identity-verified account survives; the other folds into it.
  • Cards, cash balance, verification, and history all live on the surviving account. Nothing is lost.
  • Both identifiers sign in to the merged account, so your current login keeps working.

​
If both accounts are verified

A merge between two accounts that have both completed identity verification is refused (both_kyc_approved). That one is a support case: email support@agentcard.sh.