Skip to main content

Check Address Validity

POST 
/frontoffice/api/v1/travel/address

Verifies whether the provided wallet address is associated with PingExchange or not.

  • Before using this API, providers must submit their profile to PingExchange, including the Virtual Asset Service Provider's name (VASP) and a secret key. The VASP's name will be referred to as the vaspId. Based on RFC #2104 section.3 and also RFC #4848 page.5, key needs to be chosen at random (or using a cryptographically strong pseudo-random generator seeded with a random seed). This key is required by HMAC cryptography mechanism.
  • To comply with the FATF Travel Rule verify if a wallet address is linked to PingExchange, a call to the following API is necessary.

Request​

Header Parameters

    X-Signature stringrequired

    The applicant should encrypt the wallet address using the HMAC256 encryption algorithm with the designated key, and place the resulting encrypted address in the request header.

    • Please be aware that currently, we exclusively offer support for HMAC256.
    • Generated hash value should be in Hex format.

Body

required

Contains VASPId, WalletAddress and AssetId parameters.

  • All properties are required and must be sent.

    vaspId stringrequired

    Possible values: >= 3 characters and <= 256 characters, Value must match regular expression ^[a-zA-Z0-9]*$

    The Virtual Asset Provider identifier (required)

    walletAddress stringrequired

    Possible values: >= 3 characters and <= 256 characters, Value must match regular expression ^[a-zA-Z0-9]*$

    The address of the wallet that requires verification to determine if it is associated with PingExchange (required)

    assetId stringrequired

    Possible values: >= 3 characters and <= 4 characters, Value must match regular expression ^[a-zA-Z0-9]*$

    The ID of the asset associated with the wallet such as ctn, xcb, btn etc. (required)

Responses​

Success

Loading...