Payment

Upload bankgiro file

LB files

Supplier payments ("leverantörsbetalningar") are supported.

Supported features

The following features of the LB file format are supported: (TKXX refers to record types in file)

  • Payment to BankGiro with OCR number (TK14)
  • Payment to BankGiro with message (TK14 + TK25)
  • Payment to PlusGiro with OCR number (TK54)
  • Payment to PlusGiro with message (TK54 + TK65)
  • Payment to Bank account (TK40 + TK14 [+TK65])
  • Verify number and sum of payments (TK29)

Ignored features

The following features of the LB file format are silently ignored (ie will neither cause an error or trigger any functionality) : (TKXX refers to record types in file)

  • Common payment date (TK11)
  • Information record (TK12)
  • Header record (TK13)

Not supported features

The following features of the LB file format are not supported and will result in an error : (TKXX refers to record types in file)

  • Multiple sections (TK11)
  • Credit, rebate etc (TK15, TK16, TK17)
  • Notification by mail (TK26, TK27)
  • Foreign payments (TK0 - TK9)

Bg Lön files

Salary payments ("löneutbetalningar") are supported. All three record types (TK01, TK35 and TK09) are supported.

post/psu/{psuId}/bank-account/{bankAccountId}/payment-order/upload-bg-file

Request

  • Base URL: https://bankapidemo.svea.com
  • URL: https://bankapidemo.svea.com/psu/{psuId}/bank-account/{bankAccountId}/payment-order/upload-bg-file
  • Auth: Bearer (a scheme the document does not define)

Path parameters

bankAccountIdstring uuid required
Example:ccf7c77a-8e32-4d9b-8f40-ea446f37d492
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

Response

OK

paymentOrderIdstring uuid required

Example response

[
  {
    "paymentOrderId": "d0125fa2-daf7-4e8b-a198-46e2c708918e"
  }
]

Changes

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