Skip to main content
POST
Returns the transactions your wallet has to sign while the onboarding reads AWAITING_SIGNATURE. Nothing is submitted for you: a wallet of your instance signs and broadcasts them, and Confirm Transactions records the result. The call can be repeated and builds the same step again until it is confirmed. kind says what is signed, and matches nextAction.kind of the onboarding: On an ERC-3643 register a registration is built in phases, as Verify Identity sets out. Send the claim signatures of the previous phase back as claimSignatures, and confirm a deployed ONCHAINID with Confirm ONCHAINID.

Path Parameters

string
required
The customer id, your externalId, the reference key or a wallet address of the customer.

Body Parameters

string
The wallet of your instance that will sign. Required for ELIGIBILITY_ADMISSION.
array
For an ERC-3643 registration: { walletAddress, signature, claimType } for each claim message the previous phase asked you to sign. At most 400 entries.

Response Fields

object
The example shortens onboarding and the calldata. plan also carries the confirmWith of the pending queue, which names the same confirmation on its own endpoint.

Error Codes

The builders behind each kind refuse with their own codes as well. Build Pending Registration, Build Admission and Approve KYC Record list them.