Trusset Protocol - Infrastructure for Asset Tokenization

POST

customers

api

identity

pending

{id}

dismiss

curl -X POST "https://api.trusset.org/customers/api/identity/pending/cmg1u9q2m0007l80hc4t8z3wa/dismiss" \
  -H "X-API-Key: trusset_your_key_here"

const response = await fetch(
  'https://api.trusset.org/customers/api/identity/pending/cmg1u9q2m0007l80hc4t8z3wa/dismiss',
  {
    method: 'POST',
    headers: { 'X-API-Key': 'trusset_your_key_here' }
  }
);
const { success, error } = await response.json();

{
  "success": true,
  "data": {
    "message": "Pending verification dismissed"
  },
  "error": null,
  "metadata": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-09-30T10:00:00.000Z"
  }
}

{
  "success": false,
  "data": null,
  "error": {
    "code": "NOT_FOUND",
    "message": "Pending verification not found"
  },
  "metadata": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-09-30T10:00:00.000Z"
  }
}

A dismissal cannot be undone, and no endpoint restores the row. Build Pending Registration and Confirm Pending Registration act only on PENDING rows. The approval’s kycHash, expiries and residency claim therefore never reach the register from the queue.Verifying the wallet later with Verify Identity or Batch Verify settles only PENDING rows. The follow-ups of a confirmed row therefore never run for this one. Its hosted verification checkout does not turn VERIFIED, stock escrow deposits waiting on its ID link are not bound to the wallet, and the customer is not emailed.A new KYC approval for the customer queues a fresh row. The dismissed one stays as it is.

Closes one queued approval from List Pending Verifications without registering it. Use it for an approval you have decided not to put on chain. The row turns DISMISSED and stays listable under that status. Nothing else changes. No transaction is built, nothing on chain moves, and the customer record keeps its status. A REGISTER_SWITCH row’s customer therefore still reads verified, although nothing put the wallet on your new register. The dismissal is written to the customer audit log as ON_CHAIN_VERIFICATION_DISMISSED, with the row id and its source.

Path Parameters

string

required

The row id from List Pending Verifications. The row must still be PENDING.

Response Fields

object

Show child attributes

string

Pending verification dismissed.

curl -X POST "https://api.trusset.org/customers/api/identity/pending/cmg1u9q2m0007l80hc4t8z3wa/dismiss" \
  -H "X-API-Key: trusset_your_key_here"

const response = await fetch(
  'https://api.trusset.org/customers/api/identity/pending/cmg1u9q2m0007l80hc4t8z3wa/dismiss',
  {
    method: 'POST',
    headers: { 'X-API-Key': 'trusset_your_key_here' }
  }
);
const { success, error } = await response.json();

{
  "success": true,
  "data": {
    "message": "Pending verification dismissed"
  },
  "error": null,
  "metadata": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-09-30T10:00:00.000Z"
  }
}

{
  "success": false,
  "data": null,
  "error": {
    "code": "NOT_FOUND",
    "message": "Pending verification not found"
  },
  "metadata": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-09-30T10:00:00.000Z"
  }
}

Error Codes

Code	HTTP	Cause
`NOT_FOUND`	`404`	No `PENDING` row with this `id` on your instance, including one already confirmed or dismissed, or the instance no longer exists
`PENDING_DISMISS_FAILED`	`500`	The row could not be updated

curl -X POST "https://api.trusset.org/customers/api/identity/pending/cmg1u9q2m0007l80hc4t8z3wa/dismiss" \
  -H "X-API-Key: trusset_your_key_here"

const response = await fetch(
  'https://api.trusset.org/customers/api/identity/pending/cmg1u9q2m0007l80hc4t8z3wa/dismiss',
  {
    method: 'POST',
    headers: { 'X-API-Key': 'trusset_your_key_here' }
  }
);
const { success, error } = await response.json();

{
  "success": true,
  "data": {
    "message": "Pending verification dismissed"
  },
  "error": null,
  "metadata": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-09-30T10:00:00.000Z"
  }
}

{
  "success": false,
  "data": null,
  "error": {
    "code": "NOT_FOUND",
    "message": "Pending verification not found"
  },
  "metadata": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-09-30T10:00:00.000Z"
  }
}

Overview

MiCA Register

Customers

Tokenization

Trading

Lending

Operators

Asset Register

Vaults

Dismiss Pending Verification

Path Parameters

Response Fields

Error Codes

​Path Parameters

​Response Fields

​Error Codes

Path Parameters

Response Fields

Error Codes