Authorization

Use the access_token from step 2 and the id from step 1 (or flow_id from the callback) to fetch the report.

Fetch the report

GET https://api.finx-s.qwist.cloud/rest/account-verifications/{id}

Authorization: Bearer {access_token}

Response:

{
  "id": "a9c2e4f8-1b3d-4e7a-9f2c-8d1e3b5a7c9e",
  "provided": {
    "name": "Maria Müller",
    "iban": "DE89370400440532013000"
  },
  "matched": {
    "name": "Maria Müller",
    "affinity": "VERY_HIGH"
  },
  "account": {
    "name": "Girokonto",
    "type": "Giro account",
    "owners": ["Maria Müller"],
    "iban": "DE89370400440532013000",
    "currency": "EUR"
  }
}

Understanding the affinity score

The affinity field indicates how closely the provided.name matches the best account holder name found at the bank.

✅

Recommended decision logic

• VERY_HIGH or HIGH → Accept as verified.
• MEDIUM → Flag for manual review.
• LOW → Reject or require alternative identification.

Using readout data

If you passed "ACCOUNTS" or "TRANSACTIONS" in the readout parameter during step 1, you can also fetch account and transaction data using the same access token via the standard /rest/accounts/ and /rest/transactions endpoints.

{
  "error": {
    "code": 1000,
    "group": "client",
    "description": "Request body doesn't match input schema.",
    "data": {
      "redirect_uri": ["Not a valid URL."]
    }
  }
}