Authorization requirements

Your Authorization requirements

Define your Transaction Authorization Policies to specify what you need from other Agents, such as blockchain address confirmation or a travel rule message with personal information.

Setting Default Policies

• Via Notabene Platform: Go to Policies -> Transactions -> Requirements tab and enable them. These will apply automatically to relevant transfers.
• Via API: Use entity/:entityDID/policy. Contact support for custom policies.

Updating Specific Transfers

• Use PATCH /entity/:entityDID/tx/:tx/policies. Contact support for custom policies.

Counterparty Authorization requirements

After initiating a transfer, counterparties may request data or actions. For Travel Rule compliance, subscribe to the webhook event tap.requirePresentationRequested.

• Example where the transfer is above your USA threshold and the Beneficiary Agent, in Japan, requested Travel Rule data according to their local jurisdiction:

{
  "message": "tap.requirePresentationRequested",
  "payload": {
    "beneficiaryAgentID": "did:web:vasps.id:vasp-beneficiary-jp-local:jp",
    "beneficiaryPresentationDefinition": "https://pd.notabene.id/ivms101/v1/JP-0.json",  //the Japan presentation definition send to you by the Japanese beneficiary VASP. Its up to you to fulfil or ignore
    "callbackUrl": "/vasp/did:web:vasps.id:vasp-originator-us-local:us/tx/e2c4caa3-5094-4284-9fac-665628cce938/append",
    "for": "did:web:vasps.id:vasp-originator-us-local:us",
    "id": "e2c4caa3-5094-4284-9fac-665628cce938",
    "originatorAgentID": "did:web:vasps.id:vasp-originator-us-local:us",
    "originatorPresentationDefinition": "https://pd.notabene.id/ivms101/v1/US-3000.json" //your local presentation definition. Only requested when above threshold.
  },
}

The callback URL ensures data is routed correctly. Use /append for Notabene encryption or /presentation for self-encryption.