Skip to main content

Payment Submission Services (PSS)

Payment Submission Services (PSS) refers to the submission of payment initiations by a Service User (SU) to a Service Provider (SP). Payment initiations must then be approved by the customer in e-banking.

PSS on bLink provides customers with multiple options, such as:

Payment submission

  • IBAN payments
  • Swiss QR-bill payments
  • other payment types
  • Batch bookings
  • Single bookings
  • Bookings without debit/credit advice
  • Individual advice (debit or credit)
  • Collective advice (debit or credit) without details
  • Collective advice (debit or credit) with details

Payment status

  • Payment status code
  • Payment status reason

In order to offer PSS on bLink, SUs can use multiple requests, which are described below.

Third-party payment instruction submission​

Submit payment instructions (POST/payments)​

This request can be used to start a collective payment as a credit transfer from a payer's authorized account to a recipient's account. If payment instructions are submitted successfully, a payment instruction object is created. On the other hand, if the resource cannot be created due to an invalid request format, for example, the SP responds with an error code.

The following must be considered regarding collective payments:

  • A collective payment contains transactions for one account, one currency and one value date.
  • Collective payments can contain transactions of different payment types.
  • A single payment is a collective payment with only one transaction.

The diagram below shows the steps for submitting a successful payment instruction.

Payment instruction submission sequence

  1. The SU submits the payment instruction.
  2. The payment instruction is transmitted to the SP of the payer.
  3. The SP creates the resource for the payment instruction and returns the response, including a unique identifier for the submission (submissionId).
  4. The SU receives the response with the unique identifier (submissionId) for the payment instruction. The submissionId can be used by the Service User to retrieve the details of the submitted payment instruction and its status.

Retrieve a payment submission (GET/payments/{submissionId})​

TPPs can retrieve a payment instruction. As a result, the SU will receive the submitted payment instruction for the resource indicated in the request. Additionally, a link to the status of the payment submission is returned.

Retrieve payment submission status information (GET/payments/{submissionId}/status)​

This request allow TPPs to retrieve the final status of a submitted payment instruction by using the resource created after submission. A payment instruction can have following status:

  • Accepted (ACCP)
  • Partially accepted (PART)
  • Rejected (RJCT)

If a payment instruction is partially accepted or rejected, the SP must return the rejected transaction(s) for the payment instruction with additional status information.

The following diagram shows the steps for successfully retrieving a the payment instruction status:

Payment instruction status sequence

  1. The SU submits the request to retrieve the status of the payment instruction.
  2. The request is transmitted to the SP of the recipient.
  3. The SP returns the response.
  4. The SU receives the response with the final status of the submitted payment instruction.

In case the status of the payment instruction is not yet available, the SP responds with an error code.

IMPORTANT

The status message of the corresponding payment instruction must be available for seven calendar days after submission.

Retrieve a list of consents (GET/consents)​

The consent endpoint allows SUs to query the consent for a given corporate user. The SP must return the consent linked with the access token supplied with the request. The consent will contain a list of authorized accounts with their corresponding ID, IBAN and further information.

Health check (/healthcheck)​

SUs can use this request to check if a specific module of the selected SP is available. An empty request will be sent over bLink to the corresponding SP and return a timestamp and confirmation about receipt.

"SPSPMTS": Transport XML payment initiations​

Submit an ISO-20022 XML payment instruction pain.001 (POST/iso20022/payments)​

In order to support the Swiss Payment Standard ISO-20022 files implemented by SPs, a separate channel will be offered for receiving pain.001, which is a payments initiation message by ISO-20022 that depicts a Credit Transfer message in XML format.

Retrieve ISO-20022 XML status report pain.002 of a payment instruction (GET/iso20022/payments/{submissionId})​

A submissionId has to be assigned by the SP for every pain.001 submission. This unique identifier can then be used to retrieve the corresponding pain.002 message, which is used by the SP to inform customers about the status of pain. 001 credit transfer orders.

Last updated on