Skip to main content

[Transact] - Requirements (TAP)

Written by Emanuel
Updated over a week ago

Define your TAP policies for sending and receiving transactions before granting authorization.
​
For incoming transactions:

  • Require Travel Rule information for all transactions above threshold: Authorization is held until the originator VASP provides Travel Rule information for transactions above your jurisdiction's threshold.

  • Require beneficiary name matching on provided Travel Rule information: Authorization is held until your team confirms name matching via API callback.

  • Require internal compliance screening on provided Travel Rule information: Authorization is held until your team confirms sanctions/AML checks via API callback.

  • Require authorization from all transaction participants: Authorization is held until all other transaction participants (originator, intermediaries) have approved the transfer.


For outgoing transactions

  • Require settlement address confirmation: Authorization is held until the beneficiary confirms they control the destination blockchain address.

  • Require authorization from all transaction participants: Authorization is held until all other transaction participants (beneficiary, intermediaries) have approved the transfer.

  • Automatically send Travel Rule information to beneficiary VASPs: Travel rule data is sent to beneficiary VASPs according to your jurisdiction as soon as all policy conditions are met.

​

Contact us at support@notabene.id if you have any questions or need our assistance.

Did this answer your question?