Send financial transaction with captured device

In scenarios where you need to link a financial transaction to a captured device, you can submit a financial transaction as the third step of the Device Intelligence usage flow.

To do this, use the method for submitting a transaction for non-existing applicant with the following parameters included:

QUERY parameters

ParameterTypeRequiredDescription
levelNameStringNoName of the verification level . Case-sensitive and has to be created in the same environment. If contains reserved characters (e.g., @, +", white spaces as %20), it should be URL-encoded, otherwise you may get signature mismatch.
accessTokenStringYesAccess token that you have received at the first step of the flow.

BODY parameters

ParameterTypeRequiredDescription
applicantObjectYesApplicant full name and identifier on your side.
typeStringYesTransaction type: finance.
infoObjectYesGeneral information about the transaction.

applicant attributes

AttributeTypeRequiredDescription
fullNameStringYesFull name of the applicant.
externalUserIdStringYesUnique applicant identifier within your system.
emailStringYesApplicant email address.
phoneStringNoApplicant phone number.

info attributes

AttributeTypeRequiredDescription
currencyTypeStringYesTransaction currency type: crypto or fiat.
currencyCodeStringYesCurrency code (USD, GBP, BTC, etc).
amountDoubleYesAmount of funds used in the transaction.
directionStringYesTransaction direction.
  • out — applicant sends to counterparty.
  • in — counterparty sends to applicant.

Request example

curl -X POST \
     'https://api.sumsub.com/resources/applicants/-/kyt/txns/-/data?accessToken=_act-jwt-eyx8A8qkAWM9Tb2LSS6yuP8EoLqJtWKVsmhE6AgaCav5E28JAJiJidzG2qZIjMECQ6UWsuboKvMeM1HEhPTWF1ZPqJxcdtP0N8opXwJdCZLfetv5Ui516CloG6nKT9YUaZ' \
     -H 'content-type: application/json' \
     -d '{
            "type": "finance",
            "info": {
              "currencyType": "fiat",
              "amount": 100,
              "direction": "out",
              "currencyCode": "USD"
            },
            "applicant": {
              "fullName": "John Smith",
              "email": "[email protected]",
              "externalUserId": "john.smith.1234"
            }
        }'

Response explained

The response is a JSON file that represents the full and structured transaction data. See the response structure, possible content with descriptions on the following page.

The existence of some fields in the response depends on the transaction type and matched rules.

📘

Note

You can review the transaction check status on the Transactions page in the Dashboard.