Create transfer

Creates a new transfer. The fields required in a transfer differ depending on the jurisdiction of the originating VASP.
Additional data may be provided to the beneficiary VASP depending on their jurisdiction.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Transfers Information

string

Idempotency key: to prevent duplicate transactions and proactively manage disruptions arising from the idempotency key becoming mandatory in the future, it is highly recommended to populate this field with a unique identifier for the transfer

required

Asset symbol (BTC,ETH)

string
required
^0*[1-9][0-9]*$

Amount in base unit of the asset (satoshi, wei, etc)

number

Asset decimals

customAssetPrice

Object containing custom asset price if not available in Notabene

string
^did:[a-zA-Z0-9]*:.*$

Decentralized Identifier

string
^did:[a-zA-Z0-9]*:.*$

Decentralized Identifier

string
string
string
required
^did:[a-zA-Z0-9]*:.*$

Decentralized Identifier

string
^did:[a-zA-Z0-9]*:.*$

Beneficiary VASP did - If you do not have this data, we will try to resolve it.

string

Beneficiary VASP Name - If you do not have this data, we will try to resolve it.

string

Beneficiary VASP Website - If the VASP does not already have one, it is required to provide it.

transactionBlockchainInfo
object
required

Information about the transaction on the blockchain

originator
object

The originator is defined in Section 1.1 as the account holder who allows the VA transfer from that account or, where there is no account, the natural or legal person that places the order with the originating VASP to perform the VA transfer.

beneficiary
object

The beneficiary is defined in Section 1.1 as the natural or legal person or legal arrangement who is identified by the originator as the receiver of the requested VA transfer.

string

Encrypted Personal Identificable Information (obscure schema-less value)

string
enum
Allowed:
string

Beneficiary VASP Notification Email

boolean

Disable beneficiary data validation (opportunistic compliance)

boolean

Should consider beneficiary's jurisdiction in determining if a transfer is of type TRAVEL_RULE

originatorProof
object

Ownership Proof, which can be an CryptographicalProof, ScreenshotProof, SelfDeclarationProof or MicroTransferProof

beneficiaryProof
object

Ownership Proof, which can be an CryptographicalProof, ScreenshotProof, SelfDeclarationProof or MicroTransferProof

pii
object
string

Chainalysis network

boolean

Autopopulate originator and beneficiary fields with institution's information

date-time
Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json