When a counterparty institution sends funds to one of your customers, the transfer appears under Transactions › Incoming, usually before the funds arrive. Most incoming transfers need nothing from your team, because Notabene checks the deposit address, receives the sender's data and runs your policies.
What happens by itself
Notabene confirms that the deposit address belongs to your customer. It does this by itself when the address is in My Wallets or was confirmed on an earlier transfer, and otherwise your developers answer through the API.
The originator's personal data arrives once the address is confirmed.
Your policies approve, flag or reject the transfer. When they approve it and nothing else is open on your side, your status becomes Authorized by itself.
Registering your customers' deposit addresses in advance, as described in My Wallets, means an address rarely waits for confirmation.
Review the transfer
Open the transfer from Incoming. Under Participants, the Originator side shows the counterparty customer, the address the funds come from and the sending institution. PII data shows how many of the originator's Travel Rule fields arrived, such as 5/6, and opens them.
The Review panel lists anything that holds your authorization. When your policies flagged the transfer, approve or reject the flags as described in Reviewing Flagged Transactions.
Answer what is asked
Depending on your requirements and the counterparty's, the transfer can ask your team for one of these:
Confirm beneficiary name match: click Confirm match, then Match or Mismatch. It appears once the originator's data has arrived. A mismatch rejects the transfer and tells the sending institution why.
Complete internal compliance checks: once your own checks are done, mark it Satisfied or Rejected.
Authorization required: the sending institution waits for your decision. Click Authorize or Reject.
Receive Travel Rule data: this waits on the sending institution. You can wait, or Skip it, and it is skipped by itself after its time-out.
The name match and the compliance checks apply only when you turned them on under Authorization Rules › Requirements, as described in Requirements.
Authorize or reject
When something is still open and your team has decided, click Authorize or Reject at the top of the transfer. Authorizing over an open flag or requirement asks for a reason first. Rejecting tells the sending institution, so it doesn't send the funds if it hasn't yet.
Request a revert
After the funds have arrived, Request revert asks to send them back, with a reason the sending institution sees. The revert is a new transfer linked to the original, and the sending institution authorizes it like any other. It appears in the Revert Requests tab, and only your organization can withdraw it.
Deposits without Travel Rule data
Sometimes the funds land before any Travel Rule data, and your developers record the deposit as a transfer through the API. Notabene then asks the sending institution for its data, once your policies approve. The transfer sits in the Missing Information tab until the data arrives or your organization authorizes it.
If the sending institution doesn't answer, Receive Travel Rule data is skipped after its time-out. With If skipped, submit the data myself turned on under Authorization Rules › Requirements, you then add the sender's data yourself with Add data. Deposits, funds first in the developer docs has the calls.
When a counterparty asks you for data
A counterparty institution can also record a deposit that came from one of your customers and ask you for the sender's data. It appears under Outgoing, in the Information Requests tab, with Add data on the row. Add the requested data to answer, and it is sent once your policies approve the transfer.
If none of your customers sent those funds, reject the request, so the counterparty institution knows to look elsewhere.