Corporate Payments: FAQ

Q:

We wish to implement a PIS flow for Nordea Corporate Denmark. Could you provide the maximum supported character lengths for the following fields:

• creditor.message
• creditor.message_to_bank_statement
• debtor.own_reference
• payment_instruction.information

within these templates:

• DOMESTIC_CREDIT_TRANSFER_DK
• SALARY_PENSION_DK
• DOMESTIC_TRANSFER_FORM_DK
• DOMESTIC_TRANSFER_FORM_WITH_OCR_DK
• INSTANT_CREDIT_TRANSFER_DK

A:

Please see:

* Only transfer form 73 in DOMESTIC_TRANSFER_FORM_DK and 75 in DOMESTIC_TRANSFER_FORM_WITH_OCR_DK have creditor.message field. Other transfer forms do not allow creditor.message.

Q:

With Corporate Payments API v3 now in Sandbox, can a single user sign multiple payments at once (a basket feature)? If yes, how many payments can be included in one signing request? Is this the correct high-level flow?

1. Authorize user with PAYMENTS_PSD2 scope
2. Initiate payment instructions without SCA via POST /corporate/v3/payments
3. Sign all payments in one SCA using POST /corporate/v3/payments/confirm

A:

Yes, it's possible and the flow is correct. We aim for 600 payments. Please see:

Corporate Payments API v3

Corporate Payments - API Reference

Q:

We are integrating with Corporate Payments API v3 for basket payments and observe the following:

• Individual payments are initiated and confirmed via PUT /corporate/v3/payments/confirm (bulk confirm).
• PSU authorizes the basket through an OAuth redirect.
• After basket authorization, trying to cancel individual payments with PUT /corporate/v3/payments/{payment-id}/cancel returns a 400 error: "Payment can't be cancelled at this stage".

After basket authorization, what status do individual payments have? Can individual payments be canceled after basket confirmation, and if so, when?

A:

The status following payment confirmation depends on various factors, primarily the individual user's permissions for the specific action. The status may vary and can be one of the following:

• AUTHORIZATION_FAILED - when an error has occurred
• AUTHORIZATION_PARTIAL - when additional confirmation is required (four-eyes principle)
• PAYMENT_EXECUTED - when the payment requires no further confirmation

For details on the payment flow, see:

Payment Flow - Corporate Payments API

Not all payments can be canceled at every stage. Primarily, cancellations are possible for payments in an AUTHORIZATION_PARTIAL state and, in some cases, for those in PAYMENT_ACCEPTED status, depending on the payment type and the progress of the payment process.

Cancellations cannot be performed when the payment is in AUTHORIZATION_PENDING or any final states such as PAYMENT_EXECUTED or PAYMENT_REJECTED.