Payment

Overview

The Payment product allows you to create payments (e.g. single payments and periodic payments). The product is PSD2-compliant.  

Step-by-step on how to use the Payment product

Initial activities

Enrollment and TPP security need to be in place.

For every payment

This flow shows how to initiate and authorize a payment (including Strong Customer Authentication):

Signing basket (for WebBank Corporate agreements only)

A corporate PaymentServiceUser (PSU) can initiate several payments and sign all payments using a signing basket.

The feature is not available for private PaymentServiceUsers.

Simple step-by-step:

1. POST a payment and get a paymentID in return.
2. POST several payments.  Check limitations in the payment yaml-file.
3. Create a signing basket using all the paymentIDs and use the flow shown above.
4. Let a corporate PSU sign the content of the signing basket.

If the payments require signing by more than 1 PSU, you can create a new signing basket with paymentIDs needing further signing.

Additional authentications of payments can also be handled by PSUs in the WebBank Corporate using the payment overview.

Detailed documentation

The Payment API is described by the Payment API OpenAPI specification. 

Specification	Standard	Base path	Products / services covered
Payment API v1 — download OpenAPI	Berlin Group 1.3	/openbanking-payment/v1/...	domestic-credit-transfers, instant-domestic-credit-transfers, intraday-domestic-credit-transfers, periodic-payments/domestic-credit-transfers, and signing-baskets, sepa-credit-transfers and cross-border-credit-transfers.

 

The API covers initiation, payment details and status, authorisations (SCA), cancellation and signing-basket handling for all payment products listed above.

Try it out

You can try the Payment API against the sandbox using Postman.

• Collection: Payment Sandbox — ready-to-run requests.
• Environment: Payment Sandbox Environement — points at the sandbox resource servers.

The sandbox uses static mockdata for all endpoints.

The various IDs (e.g. paymentID) that are available in the Postman collections. We recommend reading through the collection and it's documentation.

Prerequisites

You will have received the following when you signed up for sandbox access:

• a client id,
• an API key
• a test client certificate

The sandbox follows the PSD2 security flow described at: Security

Using the collections

1. Import the collection and the sandbox environment into Postman, and select the environment.
2. In the environment, fill in clientId and x-api-key with the values from your sign-up.
3. In Postman, go to Settings → Certificates and add your test client certificate (with its password) for both mTLS hosts: sandbox-cert-api.sydbank.dk (resource server) and sandbox-cert-auth.sydbank.dk (token server). This is required for the mutually-authenticated (mTLS) connections.