/ics/v3/payments/{paymentProduct}/{paymentId}

Gets the status for a specific payment Id. The session Id and payment Id in the request must be associated with the same bank Id. This API will return a 1426 error if consent is required. If the payment is initiated without debtor details, the response will not contain debtor details until the payment is completed.

Note: This endpoint returns the status of a specific individual payment. If the payment was part of a batch payment, you should use the individual paymentId (not the batchId) to get the status of that specific payment within the batch.

Payment Product Options for Batch Payments:

  • Option 1: Use batch-transfer as the paymentProduct
  • Option 2: Use the specific payment product (domestic-transfer or domestic-scheduled-transfer) if you know the actual payment type

Both approaches work and return the same individual payment details. The response type field will always show the actual payment product type regardless of which paymentProduct you use in the URL.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

The payment Id returned in the response body when the payment was initiated.

string
required

Specific method used for a payment, which is one of the following values: 'sepa-credit', 'domestic-transfer', 'domestic-scheduled-transfer', 'sepa-scheduled-credit', 'batch-transfer'.

Headers
string
required

The session Id returned in the response body when this session was created.

string
required

String that uniquely identifies a single end-user or device.

string
required

The IP Address of the end-user (PSU), which must be provided if the PSU actively requests information. If this value is not provided, then the call will count towards the number of TPP calls without PSU interaction. Leave it empty if the end user is not actively requesting account information, such as during automatic background updates. Provided in either IPv4 or IPv6 format.

string

The host where the request is originating from. If you are using end to end encryption from our developer portal then this header is mandatory.

string

The request originating date. If you are using end to end encryption from our developer portal then this header is mandatory.

string

The signature header consisting of the signature string If you are using end to end encryption from our developer portal then this header is mandatory.

Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json