Pending Approvals
Confirm Pending Registration
Check the signed registration and mark the queued approvals verified
POST
Checks the transactions your wallets broadcast for a set of queued rows, then closes every row whose wallet the register now reports as verified. A confirmed row marks its customer
verified, and creates the customer record when there is none.
Body Parameters
array
required
1 to 200 row ids, normally
ids from the build. Only rows still PENDING on your instance are checked, and any other id is dropped without an error.string
The registering transaction. On a Trusset register it is required: the batch, or a
verifyIdentity or updateIdentity call. On an ERC-3643 register it is the registerIdentity or batchRegisterIdentity step. Omit it there when every wallet was already registered.array
The claim steps you broadcast, as
[{ id, txHash }] with the row id each step carried. Entries are kept per id, so for a row with two claim steps only the last entry sent is checked. A claim that fails its check is left out of the record and fails nothing else.What the confirm checks
A failed check of
txHash refuses the whole call before any row changes. The per-row outcome comes back in results, and one row’s outcome does not affect another’s.
What a confirmed row changes
- The row turns
CONFIRMED, with the transaction, its signer and the time. - The customer record with this wallet becomes
verified, with thekycHashthe register holds and the transaction. Without a record, one is created from the row’s metadata. On an ERC-3643 register the record also getsmetadata.onchainId. - The customer audit log gets
ON_CHAIN_VERIFIED, with the queued and the registered hash. - A hosted verification checkout behind the row turns
VERIFIED, and stock escrow deposits waiting on its ID link are bound to the wallet. - When the row carries
notifyEmail, the customer is emailed that verification is complete.
PENDING, and its error says why. Build and confirm it again once the cause is fixed. A repeat call for rows that all confirmed answers NOT_FOUND, because none of them is PENDING any more.
The HTTP status is
200 and success is true even when no row confirmed. Read confirmed and each entry of results.Response Fields
object
array
