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/v*/payments/domestic/{payment-id}
GET: /personal/v*/payments/sepa/{payment-id}

What has changed?

Initiating the signing process of one or multiple payments

PUT: /personal/v*/payments/domestic/confirm
PUT: /personal/v*/payments/sepa/confirm

Detailed explanation

Endpoint	Description	More info of changes
POST: /personal/v/payments/domestic or POST: /personal/v/payments/sepa	response 201 CREATED
DEPRECATED PUT: /personal/v*/payments/domestic/{paymentid}/confirm	response 202 ACCEPTED _links: "response": { ... "_links": [ { "rel": "signing", "href": "$nasa_url$?order_id=1234567&redirect_uri=$obi_url$&state=$url_encoded_parameters$" } ] ...	The link relation "signing" will be the header "location" redirection to be sent to the PSU in some form of browser. The result will in the end be a 200 OK, this should trigger a close of the browser session
PUT: /personal/v/payments/domestic/confirm or PUT: /personal/v/payments/sepa/confirm	request { "payments_ids": ["string","string"], "redirect_url": "string", "state": "string" } response 202 ACCEPTED { ... "_links": [ { "rel": "signing", "href": "$nasa_url$?order_id=1234567&redirect_uri=$obi_url$&state=$url_encoded_parameters$" } ] ...	payments_ids = A string list of paymentIds to be confirmed] redirect_url = The TPP redirection URL, One of the urls from the initial sign up state = Optional info to be returned with the redirection
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): $tpp_redirect_url$?success=true&state=tppstate	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). If the page is not available for some reason, the PSU will be redirected to the Nordea bank page. The "success" query parameter in the response indicates if the signing was completed. Note: it doesn't have to mean the payment was successfully executed. For example: for domestic DK payments a second channel confirmation (like SMS) would be required when the amount is bigger than 100 000 DKK. To make sure the transfer was paid and done - see next step.
GET: /personal/v/payments/domestic/{payment-id} or GET: /personal/v/payments/sepa/{payment-id}	response 200 OK	Check the "payment_status" field value to find out if the payment was successfully executed (should be "paid").

Related Questions

Introduction

What has changed?

Detailed explanation