According to the financial regulations that we follow, only the crypto registrar can finalize the creation of the tokenized security. Once you have sent the token creation request successfully, the registrar employee will apply the four-eyes principle. If the entered data match the terms of issue, we will approve the request and the token will be minted (= created) on-chain.
ℹ️ On UAT – and UAT only – you can still simulate the approval of the token by calling the endpoint Finalize Tokenized Asset.
PUT Finalize Tokenized Asset /api/tokenization/{institutionId}/tokenized-assets/{tokenizedAssetId}/approve
Request Example
# UAT BASE_URL: https://uat.vault.nyala.de
# Production BASE_URL: https://vault.nyala.de
# The {institutionId} is 8c8f78bc-78e0-47a7-b4e0-a793343175f0
# The {tokenizedAssetId} is ef86ea3e-f46f-4274-aad8-e83b1a241360
curl -X PUT {{BASE_URL}}/api/tokenization/{institutionId}/tokenized-assets/{tokenizedAssetId}/approve \
-H "X-API-KEY: YOUR_API_KEY" \Once the token is minted, a few more steps are required to send all the legally required data to the blockchain.
ℹ️ Side note: If you select HADC as your custodian, the Smart Registry Operations team will notify HADC of the asset's public address following token approval and minting on-chain. HADC must then register this token in their system. Wallet requests cannot be routed to HADC's system for further approval without this token registration.