Onboarding
Bind Wallet
Give the onboarded customer the wallet they will hold their identity with
POST
/
customers
/
api
/
onboarding
/
{customer}
/
wallet
curl -X POST "https://api.trusset.org/customers/api/onboarding/client-48213/wallet" \
-H "Content-Type: application/json" \
-H "X-API-Key: trusset_your_key_here" \
-d '{ "walletAddress": "0x96C5822784130360F904372b83E130be4A1894D6" }'
const response = await fetch(
'https://api.trusset.org/customers/api/onboarding/client-48213/wallet',
{
method: 'POST',
headers: { 'Content-Type': 'application/json', 'X-API-Key': 'trusset_your_key_here' },
body: JSON.stringify({ walletAddress: '0x96C5822784130360F904372b83E130be4A1894D6' })
}
);
const { data } = await response.json();
console.log(data.status);
{
"data": {}
}Binds a wallet to the customer and to the onboarding. Call it when the customer connects a wallet in your app, before or after the review. A wallet sent with Start Onboarding is bound the same way.
What the binding does depends on where the onboarding stands:
A customer holds one primary wallet. Binding the wallet the customer already holds is accepted and changes nothing. The register is read once to see whether your instance already verified the wallet, and nothing is written on chain.
| Onboarding | Effect |
|---|---|
TRUSSET, check still open | The wallet is recorded. An approval later finishes the onboarding with it |
TRUSSET, AWAITING_WALLET | The registration is queued now and the status turns AWAITING_SIGNATURE. When your register already verifies the wallet, it turns COMPLETED |
KYC_SOURCE, AWAITING_WALLET | The status turns AWAITING_RECORD. A record your source already delivered for the wallet is picked up at once |
Path Parameters
Body Parameters
Response Fields
The onboarding after the binding. Get Onboarding describes every field.
curl -X POST "https://api.trusset.org/customers/api/onboarding/client-48213/wallet" \
-H "Content-Type: application/json" \
-H "X-API-Key: trusset_your_key_here" \
-d '{ "walletAddress": "0x96C5822784130360F904372b83E130be4A1894D6" }'
const response = await fetch(
'https://api.trusset.org/customers/api/onboarding/client-48213/wallet',
{
method: 'POST',
headers: { 'Content-Type': 'application/json', 'X-API-Key': 'trusset_your_key_here' },
body: JSON.stringify({ walletAddress: '0x96C5822784130360F904372b83E130be4A1894D6' })
}
);
const { data } = await response.json();
console.log(data.status);
Error Codes
| Code | HTTP | Cause |
|---|---|---|
INVALID_ADDRESS | 400 | walletAddress is missing, malformed or the zero address |
COUNTRY_BLOCKED | 403 | The profile blocks the customer’s country, so nothing was bound or queued |
CUSTOMER_NOT_FOUND | 404 | No customer of your instance matches customer |
CUSTOMER_WALLET_MISMATCH | 409 | The customer already holds another wallet. Change it on the customer record first |
WALLET_MISMATCH | 409 | The identity check is bound to another wallet |
WALLET_IN_USE | 409 | The wallet belongs to another customer of your instance, an archived one included, as its primary or as a linked wallet |
RATE_LIMIT_EXCEEDED | 429 | More than 120 onboarding writes in the minute |
ONBOARDING_WALLET_FAILED | 500 | The binding failed on the server |
⌘I
curl -X POST "https://api.trusset.org/customers/api/onboarding/client-48213/wallet" \
-H "Content-Type: application/json" \
-H "X-API-Key: trusset_your_key_here" \
-d '{ "walletAddress": "0x96C5822784130360F904372b83E130be4A1894D6" }'
const response = await fetch(
'https://api.trusset.org/customers/api/onboarding/client-48213/wallet',
{
method: 'POST',
headers: { 'Content-Type': 'application/json', 'X-API-Key': 'trusset_your_key_here' },
body: JSON.stringify({ walletAddress: '0x96C5822784130360F904372b83E130be4A1894D6' })
}
);
const { data } = await response.json();
console.log(data.status);
{
"data": {}
}