Creditor

OCR validation

The result has the following meanings:

  • noValidationSupported - corresponds to noValidation level
  • valid - corresponds to any level except noValidation, if valid
  • invalidMayBeAccepted - corresponds to soft, invalid OCR but should in most cases just warn the user
  • invalidWillNotBeAccepted - corresponds to all three hard levels, payment order will not succeed
post/psu/{psuId}/creditor/validate-ocr

Request

  • Base URL: https://bankapidemo.svea.com
  • URL: https://bankapidemo.svea.com/psu/{psuId}/creditor/validate-ocr
  • 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

accountNumberstring required
accountNumberType'bankGiro' | 'plusGiro' required
ocrNumberstring required

Example request

{
  "accountNumber": "5707-9055",
  "accountNumberType": "bankGiro",
  "ocrNumber": "123456789"
}

Response

OK

result'noValidationSupported' | 'valid' | 'invalidMayBeAccepted' | 'invalidWillNotBeAccepted' required

Example response

{
  "result": "valid"
}

Changes

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