Skip to main content
POST
Queues a wallet for admission to the eligibility register of one verification profile. Nothing is written on chain here: the admission waits as PENDING until your wallet signs it through Build Admission and Confirm Admission. See Eligibility registers. Most admissions need no request. Trusset queues one when a customer of the profile passes an ID link review or is registered on your instance register. Use this endpoint for a customer onboarded before the profile had a register, or under a different profile.

Who can be admitted

The wallet must belong to a customer record on your instance that is not archived. A wallet no customer holds is refused with CUSTOMER_NOT_FOUND, so onboard the customer first. The customer must also meet the profile:
  • The customer’s status is not rejected or revoked.
  • The customer’s country is not on the profile’s blockedCountries.
  • The customer’s customerType matches the profile’s entityType: INDIVIDUAL or COMPANY.
Whether the wallet is verified on your instance register is checked when the admission is built, not here.

Admitting under another profile

A customer onboarded under one profile, whose investorType names that profile, does not automatically meet another. To admit them anyway, send confirmEligibility: true. That records your decision that the customer meets this profile’s requirements, together with the profile they were onboarded under, on the admission and in the customer audit log. Without it the request is refused with ELIGIBILITY_CONFIRMATION_REQUIRED. The investorType is compared with the profile key in any letter case. Admissions Trusset queues on its own never need the confirmation, because they follow the profile the customer was verified under.

Registers that take no request

The profile’s register mode, recorded when the register was bound, is checked before the customer. See Which registers can be signed here. When the profile’s register is your instance register itself, registering a wallet there is its admission. Nothing is queued, and the call answers 201 with admission: null, mode: INSTANCE_REGISTER and a message. Register the wallet through Verify Identity or the pending queue instead. When the profile’s register is managed outside your instance, in the EXTERNAL mode, its owner admits wallets with its own tools. The call is refused with 409 ADMISSIONS_MANAGED_EXTERNALLY.

A wallet waiting for removal

An admission in REMOVAL_PENDING has a removal waiting to be signed. A request for that wallet withdraws the removal instead of queuing a new admission. Whether it can depends on why the removal was queued: The customer must meet the profile again first. A customer record still revoked or rejected is refused with CUSTOMER_NOT_ELIGIBLE, and a country still blocked with COUNTRY_BLOCKED. After an archive or a wallet change no customer of your instance holds the wallet any more, so the request is refused with CUSTOMER_NOT_FOUND. A customer onboarded under another profile still needs confirmEligibility: true for the withdrawal, as for any admission under that profile. A fresh verification of the customer, through an ID link or a registration on your instance register, withdraws a LAPSED, REVOKED, REJECTED or REQUIREMENTS_CHANGED removal on its own. It never withdraws a MANUAL, COUNTRY_BLOCKED, ARCHIVED or WALLET_CHANGED removal. Only a request from you, here or in the Issuer Portal, does. The register is read before anything changes, and the outcome follows what it holds:
  • The wallet is still on the register. The removal is cancelled and the admission is ADMITTED again: 200 with alreadyAdmitted: true and removalCancelled: true. An eligibility.removal_cancelled event goes to your customer webhooks.
  • The wallet is already off the register, for example because a removal was signed but not yet confirmed. The admission goes back to PENDING and waits to be built like a new one: 201 with alreadyAdmitted: false.

Re-verification

When the profile sets reverifyDays, an admission is due again that many days after it was admitted, and a lapsed admission is queued for removal with reason LAPSED. The period restarts only on a verification of the customer, through an ID link or a registration on your instance register, or on a request sent with reverifiedOutsideTrusset: true that withdraws a LAPSED, REVOKED, REJECTED or REQUIREMENTS_CHANGED removal while the wallet is still on the register. The response then carries renewed: true, and dueAt counts from now. confirmEligibility never restarts it, and a request never renews an admission that is already ADMITTED.
An admission made ADMITTED again without a verification or an attestation keeps its dueAt. When that date has already passed, the admission lapses again at once, and its new LAPSED removal then needs reverifiedOutsideTrusset: true.

Body Parameters

string
The profile, by key. Matched exactly, then in upper and lower case. Send this or profileId.
string
The profile, by id. Used instead of profileKey when both are sent.
string
required
The wallet to admit, 0x followed by 40 hex characters. Stored and returned checksummed.
boolean
true to admit a customer onboarded under another profile. It records your decision that the customer meets this profile’s requirements. Only the boolean true counts.
boolean
true to withdraw a LAPSED, REVOKED, REJECTED or REQUIREMENTS_CHANGED removal after you re-verified the customer outside Trusset. It is recorded on the admission and restarts the re-verification period. Only the boolean true counts.
string
A note kept with the admission and in the audit log, up to 300 characters. Longer text is cut.

What comes back

Response Fields

object

Error Codes