Skip to main content

bLink API - payments-submission-service module (5.0.0.1-SNAPSHOT-fi)

Download OpenAPI specification:Download

This is the specification of the bLink 'payments-submission-service' module API. (as implemented by providers (e.g. financial institutions) and used by SIX)

payments

Submit payment instructions

Create new payments submission.

header Parameters
Authorization
required
string

Bearer followed by a base64 encoded OAuth access token

X-CorAPI-Client-ID
required
string

ID of the client forwarded to the provider.

X-Correlation-ID
required
string <= 64 characters

Unique ID (defined by the caller) which will be reflected back in the response.

User-Agent
required
string

Name and version of the of the Client software

X-CorAPI-Target-ID
string

ID of the target, e.g., a financial institution.

X-PSU-IP-Address
string

IP address of the user initiating the operation

X-PSU-User-Agent
string

User of the client software

X-PSU-Accept-Lang
string

Language of client software

Request Body schema: application/json
required

Payment instruction details as defined by data model.

bookingInstruction
required
string (Payment Booking Instruction)
Enum: "SINGLEBOOKING_SIA" "SINGLEBOOKING_NOA" "BATCHBOOKING_SALA_NOA" "BATCHBOOKING_SALA_CND" "BATCHBOOKING_NOA" "BATCHBOOKING_CND" "BATCHBOOKING_CWD"

The payment booking instruction, i.e. the method for processing and grouping a payment. Corresponds to the attribute DbtrAcct ⇾ Tp ⇾ Prtry in SPS/ISO-20022. Possible methods are:

  • SINGLEBOOKING_SIA
  • SINGLEBOOKING_NOA
  • BATCHBOOKING_SALA_NOA
  • BATCHBOOKING_SALA_CND
  • BATCHBOOKING_NOA
  • BATCHBOOKING_CND
  • BATCHBOOKING_CWD
required
object (Payment IBAN Account)

The IBAN account object.

initiatingPartyId
required
string (InitiatingPartyId) <= 32 characters

The identifier of the third party provider (TPP) who created the payment instruction message derived from the OAuth 2.0 flow.

messageId
required
string (MessageId) <= 35 characters

The unique identifier (UUID) of the the instruction message. Corresponds to the attribute MsgId in SPS/ISO-20022.

requestedExecutionDate
required
string <date> (Date)

A date.

required
Array of objects (Payment Instruction Item)

The transaction items.

Responses

Request samples

Content type
application/json
{
  • "bookingInstruction": "BATCHBOOKING_SALA_CND",
  • "debtorAccount": {
    },
  • "initiatingPartyId": "TPP01746",
  • "messageId": "eb6305c91f7f49deaed016487c27b42d",
  • "requestedExecutionDate": "2018-04-13",
  • "transactions": [
    ]
}

Response samples

Content type
application/json
{
  • "submissionId": "618d4ac6e8a64e3d9f26aa3d8c4f323e"
}

Retrieve payment submission status information

Retrieve a specific payment submission's status.

path Parameters
submissionId
required
string <= 35 characters
Example: submissionId

ID of payment submission to be retrieved.

header Parameters
Authorization
required
string

Bearer followed by a base64 encoded OAuth access token

X-CorAPI-Client-ID
required
string

ID of the client forwarded to the provider.

X-Correlation-ID
required
string <= 64 characters

Unique ID (defined by the caller) which will be reflected back in the response.

User-Agent
required
string

Name and version of the of the Client software

X-CorAPI-Target-ID
string

ID of the target, e.g., a financial institution.

X-PSU-IP-Address
string

IP address of the user initiating the operation

X-PSU-User-Agent
string

User of the client software

X-PSU-Accept-Lang
string

Language of client software

Responses

Response samples

Content type
application/json
{
  • "statusCode": "PART",
  • "messageId": "eb6305c91f7f49deaed016487c27b42d",
  • "transactions": [
    ]
}

iso20022

Submit ISO20022 XML payment instruction (PAIN.001)

Submit an XML pain.001 payment instruction according to the ISO20022 specification.

  • bLink supports payment instructions only in XML-Schema «pain.001.001.09».
header Parameters
Authorization
required
string

Bearer followed by a base64 encoded OAuth access token

X-CorAPI-Client-ID
required
string

ID of the client forwarded to the provider.

X-Correlation-ID
required
string <= 64 characters

Unique ID (defined by the caller) which will be reflected back in the response.

User-Agent
required
string

Name and version of the of the Client software

X-CorAPI-Target-ID
string

ID of the target, e.g., a financial institution.

X-PSU-IP-Address
string

IP address of the user initiating the operation

X-PSU-User-Agent
string

User of the client software

X-PSU-Accept-Lang
string

Language of client software

Request Body schema: application/xml
required

Payment instruction details as defined by data model.

string <binary>

Responses

Response samples

Content type
application/json
{
  • "submissionId": "618d4ac6e8a64e3d9f26aa3d8c4f323e"
}

Retrieve ISO20022 XML status report of a payment instruction (PAIN.002)

Retrieve the status report for the requested XML ISO20022 payment instruction (PAIN.002).

  • bLink supports status reports only in XML-Schema «pain.002.001.10».
path Parameters
submissionId
required
string <= 35 characters
Example: submissionId

ID of payment submission to be retrieved.

header Parameters
Authorization
required
string

Bearer followed by a base64 encoded OAuth access token

X-CorAPI-Client-ID
required
string

ID of the client forwarded to the provider.

X-Correlation-ID
required
string <= 64 characters

Unique ID (defined by the caller) which will be reflected back in the response.

User-Agent
required
string

Name and version of the of the Client software

X-CorAPI-Target-ID
string

ID of the target, e.g., a financial institution.

X-PSU-IP-Address
string

IP address of the user initiating the operation

X-PSU-User-Agent
string

User of the client software

X-PSU-Accept-Lang
string

Language of client software

Responses

Response samples

Content type
application/problem+json
{
  • "detail": "Detailed problem description with respect to the current request",
  • "title": "This is the general problem description",
  • "type": "/problems/TECHNICAL_ERROR",
  • "instance": "path/to/corresponding/resource"
}

consents

Retrieve a list of consents

The consents endpoint allows the client (e.g., a third party provider) to query the consents for a given user. The provider (e.g., a financial institution) must return the consents linked with the access token supplied with the request.

query Parameters
cursor
string
Example: cursor=cursorIDxyz

Optional parameter for pagination. Use the ID of the last item from the previous response to retrieve the next set of results.

limit
integer <int32> >= 1
Default: 25
Example: limit=25

Optional parameter for pagination, specifying the number of items to return. The actual maximum limit can be defined by the provider.

header Parameters
Authorization
required
string

Bearer followed by a base64 encoded OAuth access token

X-CorAPI-Client-ID
required
string

ID of the client forwarded to the provider.

X-Correlation-ID
required
string <= 64 characters

Unique ID (defined by the caller) which will be reflected back in the response.

User-Agent
required
string

Name and version of the of the Client software

X-CorAPI-Target-ID
string

ID of the target, e.g., a financial institution.

X-PSU-IP-Address
string

IP address of the user initiating the operation

X-PSU-User-Agent
string

User of the client software

X-PSU-Accept-Lang
string

Language of client software

Responses

Response samples

Content type
application/json
[
  • {
    }
]

diagnostics

Returns all specified request headers and additional diagnostic information

header Parameters
X-Correlation-ID
string <= 64 characters

Unique ID (defined by the caller) which will be reflected back in the response.

User-Agent
string

Name and version of the of the client software

X-CorAPI-Target-ID
string

ID of the target, e.g., a financial institution.

X-CorAPI-Client-ID
required
string

ID of the client forwarded to the provider.

X-PSU-IP-Address
string

IP address of the user initiating the operation

X-PSU-User-Agent
string

User of the client software

X-PSU-Accept-Lang
string

Language of client software

Responses

Response samples

Content type
application/json
{
  • "requestDateTime": "2018-04-13T11:11:11Z",
  • "receivedHeaders": [
    ],
  • "receivedPayload": "... as received ..."
}

Returns all specified request headers, the request body and additional diagnostic information

header Parameters
X-Correlation-ID
string <= 64 characters

Unique ID (defined by the caller) which will be reflected back in the response.

User-Agent
string

Name and version of the of the client software

X-CorAPI-Target-ID
string

ID of the target, e.g., a financial institution.

X-CorAPI-Client-ID
required
string

ID of the client forwarded to the provider.

X-PSU-IP-Address
string

IP address of the user initiating the operation

X-PSU-User-Agent
string

User of the client software

X-PSU-Accept-Lang
string

Language of client software

Request Body schema: application/json
required
string

Responses

Request samples

Content type
application/json
"string"

Response samples

Content type
application/json
{
  • "requestDateTime": "2018-04-13T11:11:11Z",
  • "receivedHeaders": [
    ],
  • "receivedPayload": "... as received ..."
}