Introduction
Nordea has introduced support to initiate signing of one or multiple payments as one single group in order for Nordea to process them in a batch. The payments, to be signed as single group, must be created by the same user.
When initiating signing of multiple payments Third Party Provider (TPP) optionally can supply their own redirect url and/or state parameter, which Nordea will use to redirect the PSU back to after successfully initiating execution of the payment(s). If signed, all the payments get processed and TPP can check their status by requesting one of the endpoints
- GET: /personal/v4/payments/domestic/{payment-id}
- GET: /personal/v4/payments/sepa/{payment-id}
- GET: /personal/v5/payments/{payment-id}
What has changed?
Initiating the signing process of one or multiple payments
- PUT: /personal/v4/payments/domestic/confirm
- PUT: /personal/v4/payments/sepa/confirm
- PUT: /personal/v5/payments
Detailed explanation
Endpoint |
Description
|
More info of changes
|
|
---|---|---|---|
POST: /personal/v4/payments/domestic or POST: /personal/v5/payments/{paymentType}/ |
response 201 CREATED |
|
|
PUT: /personal/v4/payments/domestic/confirm or PUT: /personal/v5/payments |
request { response 202 ACCEPTED {
|
payments_ids = A string list of paymentIds to be confirmed]. |
|
GET: "$nasa_url$?order_id=1234567&redirect_uri=$obi_url$ &state=$url_encoded_parameters$" |
response 200 OK Format of the success response (redirection url to the TPP):
|
After the payment is signed by the PSU, the user is redirected to the Third Party Provider (TPP) page (the one provided during the onboarding process for the sake of the OAuth2.0 authorization flow). The "status" query parameter in the response indicates if the signing was successfully signed or not. |
|
GET: /personal/v4/payments/domestic/{payment-id} or GET: /personal/v5/payments/{payment-id} |
response 200 OK |
Check the "payment_status" field value to find out if the payment was successfully executed (should be "paid"). |