Your requirements set what must happen before your organization can authorize a transaction, such as sending your Travel Rule data or hearing back from the counterparty. Your policies decide whether a transaction is allowed, and your requirements decide what has to happen first. You choose them under Authorization Rules › Requirements, starting from a preset.
Choose a preset
Go to Authorization Rules › Requirements.
On the Presets tab, select Straight-through processing or Counterparty coordination.
Set the Skip after time for each requirement that has one.
Click Save.
The two presets differ in whether your side waits for the counterparty:
Straight-through processing: three requirements. Your side is authorized as soon as it is complete, without waiting on the counterparty.
Counterparty coordination: five requirements. It adds two confirmations from the counterparty, and each one is skipped after its timeout, so no transaction waits forever.
A change applies only to transactions created after you save. A transaction already in progress keeps the requirements and timeouts it started with.
The requirements
Both presets include the first three:
Send Travel Rule data: your Travel Rule data satisfies your presentation requirements, the data your Travel Rule settings say you must send. If some is missing, nothing is sent and the requirement stays Pending until your team adds it.
Transmit Travel Rule data: your Travel Rule data reaches a counterparty institution on the Notabene network.
Receive Travel Rule data: the counterparty's Travel Rule data satisfies your presentation requirements. It doesn't apply to a transaction below your own threshold.
Counterparty coordination adds two more:
Require wallet ownership confirmation: the counterparty confirms that it controls the receiving wallet address.
Require counterparty authorization: the counterparty authorizes the transaction. When both institutions wait for each other's authorization and nothing else is open on either side, both are authorized automatically.
Whatever the preset, on a transfer you send to another institution, Notabene asks it to confirm the receiving address before your customer's personal data leaves. You can't turn this confirmation off and it is never skipped, and an address already confirmed isn't asked about again.
Your presentation requirements come from your Travel Rule Settings.
Skip after
Receive Travel Rule data and the two counterparty confirmations each have a Skip after time, 1 minute by default. When the time runs out and the counterparty hasn't answered, the requirement reads Skipped and the transaction moves on. Every skip is recorded in your audit trail.
If the counterparty's Travel Rule data arrives after Receive Travel Rule data was skipped, the requirement becomes Satisfied.
Options for Receive Travel Rule data
Select custom requirements: your team judges the counterparty's data against a specific rule set, instead of the presentation requirements that come from your jurisdiction.
If skipped, submit the data myself: when Receive Travel Rule data is skipped, a Submit Travel Rule data requirement asks your team to add the sender's data. It holds your authorization until you do. This option is off by default.
Confirm beneficiary name match
This check sits on top of either preset, and you turn it on only if your compliance workflow includes it. With Match beneficiary name against internal records on, your organization doesn't authorize an incoming transaction until your team confirms the beneficiary name. The name must match the account owner in your own systems.
The check appears on the transaction once the originator's data has arrived. Your team answers Match or Mismatch, and a Mismatch rejects the transaction and tells the sender why.
Advanced
For finer control than the presets give, the Advanced tab sets each requirement on its own.
Each requirement on a transaction has its own status, such as Pending, Satisfied or Skipped, as described in Statuses. For the requirements in the API, see Requirements in the developer docs.
