Skip to main content
POST
Binds the wallet a customer will hold their identity with to a link. Your own app calls it when the customer connects a wallet, which can happen before or after the review. The wallet is recorded as bound by you, walletBoundBy: ISSUER, and the link accepts no other wallet from then on. The call binds a wallet only to a link that is not revoked, rejected or consumed. A link past expiresAt is refused unless its review was approved: the expiry closes the identity check, not your binding of an approved customer’s wallet.

Before or after the review

Bound before the review, nothing else happens yet, and the call answers registration: AFTER_REVIEW. An approval later finishes the link with this wallet. Bound after an approval that came without a wallet, awaitingWallet: true on Get ID Link, the link is finished now. From the approval on, this call is the only way to bind the wallet: the hosted page refuses the customer with 409 ISSUER_BINDS_WALLET and asks them to contact you. Finishing the link does this:
  • The customer record is written with the wallet, or created when there is none.
  • The wallet’s registration on your instance register is queued in the pending queue for your wallet to sign, registration: PENDING. When your register already verifies the wallet, nothing is queued and the answer is REGISTERED.
  • When the link’s profile has an eligibility register, the wallet’s admission to it is queued. See Eligibility registers.
Nothing is written on chain by this call.
An approved link stays bindable after expiresAt, so an approved customer never has to repeat the check. A revoked link is refused with EXPIRED at any time.

Path Parameters

The link id, not the token.

Body Parameters

string
required
The customer’s wallet, 0x followed by 40 hex characters. Stored and returned checksummed. Sending the wallet the link is already bound to is accepted.

Response Fields

object

Error Codes