Skip to main content
GET
Lists the KYC approvals your instance has not yet put on chain. When a customer passes KYC through an ID link or a hosted verification service, Trusset computes the kycHash, investor type, expiries and residency claim, then queues a row here. Nothing is signed until your wallet signs it. Work the queue in two steps. Build Pending Registration returns the transactions, and Confirm Pending Registration records them once mined. Dismiss Pending Verification closes a row without registering it.

Where rows come from

A Sumsub approval from a country that the customer’s verification profile blocks is refused and never queued. REGISTER_SWITCH rows are not checked until the build. The expiries are fixed when the row is queued: 180 days soft and 365 days hard, unless a hosted verification service sets its own. They do not move while the row waits. A wallet has at most one PENDING row. A new approval for the same wallet refreshes that row, replacing its hash, expiries and metadata, instead of adding a second. A row also closes when its wallet is verified through Verify Identity or Batch Verify. It then reads CONFIRMED, with metadata.resolvedBy set to DIRECT_VERIFY or BATCH_VERIFY. Closed rows are kept and stay listable by status.

Query Parameters

string
default:"PENDING"
PENDING, CONFIRMED or DISMISSED, in any case. Any other value returns no rows, and no single value lists every status at once.
integer
default:"1"
Page number. Values below 1 read as 1. A value that is not a number fails with PENDING_LIST_FAILED.
integer
default:"50"
Rows per page, capped at 200. Values below 1 read as 1. A value that is not a number fails with PENDING_LIST_FAILED.

Response Fields

object
array
object
Other keys, such as applicantId, idLinkId, checkoutId and name, describe where the approval came from. A confirm uses them to fill in a customer record it creates, and to run its follow-ups.

Error Codes