Lookup creditors

OCR validation levels

For reference, see https://www.bankgirot.se/tjanster/inbetalningar/bankgiro-inbetalningar/ocr-referenskontroll/

Valid OCRs use the well known Luhn algorithm to produce a checksum. In some cases, the next to last digit will also bear meaning.

Validation levels:

noValidation - No validation, will accept any text
soft - Prefers a valid Luhn number, but the payment will accept any text
hard - Requires a valid Luhn number, will not accept anything else
hardWithVariableLength - Same as hard, except the next to last digit must be the number of digits mod 10
hardWithFixedLength - Same as hardWithVariableLength, except the length can only be one of 1-2 values specified in advance

post/psu/{psuId}/creditor/lookup

Request

Base URL: https://bankapidemo.svea.com
URL: https://bankapidemo.svea.com/psu/{psuId}/creditor/lookup
Auth: Bearer (a scheme the document does not define)

Path parameters

psuIdstring uuid required

Example:febbe8f2-bd6b-4e53-89c6-e89ca92ff5ee

Headers

Authorizationstring required

Example:Bearer {BearerToken}

X-Svea-ClientAppstring required

Tenant client app name, version, and optional comment <client-app-name>/<version>(/<comment>)

Example:TENANT-IOS/0.99.0

X-Svea-CorrelationIdstring uuid

The correlationId is a unique identifier value that is attached to requests and messages that allow reference to a particular transaction or event chain. Used to follow transaction information, especially for logging purposes.

Example:21436a05-d62d-4f29-a253-31b3815d148b

X-Svea-SessionIdstring uuid

The sessionId is a unique identifier value for a users session. This identifier should be the same for the entire duration of that users session. Mainly used for logging and troubleshooting purposes.

Example:afe56332-dee2-48b4-ae0b-d694a6174a7e

Request body

numberGuessstring required

numberType'bankGiro' | 'plusGiro' | 'bankGiroOrPlusGiro' | 'swedishBankAccount' | 'guess' required

Note! New numberTypes might be added at any time

Example request

{
  "numberGuess": "96692474932",
  "numberType": "guess"
}

Response

Example response

[
  {
    "bankAccountNumber": "2474932",
    "bankDisplayName": "Svea Bank AB",
    "clearingNumber": "9669",
    "creditor": {
      "bankAccountNumber": "2474932",
      "bankDisplayName": "Svea Bank AB",
      "clearingNumber": "9669",
      "iban": "SE4796600000096692474932"
    },
    "creditorType": "swedishBankAccount",
    "iban": "SE4796600000096692474932"
  }
]

Changes

No recorded changes to this operation across all 1 revision of this API.