Q:
What's the maximum timeframe between the scheduling and execution of a scheduled payment using:
POST /v5/payments/{paymentType}
If there are any limitations or restrictions on how far in advance a payment can be scheduled when utilizing this API? Is there a maximum number of days or weeks between the scheduled date and the execution date?
A:
The following are the time limitations when it comes to future dated payments rules:
- SEPA: 1 year
- Domestic: 1 year
- Cross Border: 1 year
Q:
(Sandbox) We attempt to setup SEPA payments for Sweden using:
API reference - Payments Common API
While initiating a payment we encounter the following error (code: 'error.validation', description: 'Debtor SEPA account should be from Finland', path: 'debtor.account.value', type: 'ValidSepaDebtorAccount'):
Request- endpoint: POST /v5/payments/sepa-credit-transfers- body: {instructed_amount: { amount: 100000, currency: 'EUR' },creditor: {account: {_type: 'IBAN',currency: 'EUR',value: 'SE45[REDACTED]7466'},message: null,name: 'name'},debtor: {account: {_type: 'IBAN',currency: 'EUR',value: 'SE80[REDACTED]0039'},message: null},external_id: '550e8400-[REDACTED]-446655440028',urgency: 'standard'}ResponseStatus: 400 Bad requestdate: 'Mon, 09 Jun 2025 10:09:48 GMT'failures: [{code: 'error.validation',description: 'Debtor SEPA account should be from Finland',path: 'debtor.account.value',type: 'ValidSepaDebtorAccount'}]message_identification: '79fc7fc5-5cbc-430e-aabf-006d93774141',creation_date_time: '2025-06-09T10:15:26.910313864Z',http_code: 400
Is it not possible to test it with Sweden?
A:
The endpoint:
POST /personal/v5/payments/sepa-credit-transfers
is created exclusively for Finland. Sending SE payments using the above request will result in a 4xx error. In other countries (e.g. Sweden) for SEPA payments you should use cross-border endpoint:
POST /personal/v5/payments/cross-border-credit-transfers
If you make a cross-border payment in Euro and it fulfills SEPA Credit Transfer requirements, the payment will automatically be performed as SEPA Credit Transfer.
Q:
What charging method can you use for EU-area?
A:
The only allowed charging method for payments that have beneficiary bank in EU-area or EEA-area is SHA (shared charges).
Q:
If a SEPA payment in Finland is made after a cut-off time, is it going to be rejected or rescheduled?
A:
The payment will be rescheduled provided it is not an instant payment with the urgency parameter set to express.
Q:
Regarding the callback from the payment authorization endpoint POST /personal/v2/payments/authorization/sepa-credit-transfer. After the user completes SCA and is redirected to our redirect_uri, the response_code parameter contains a signed JWT. Decoding it reveals a status field. Example JWT header and body:
{
"kid": "openbanking_signed_token_4",
"alg": "RS256"
}{
"external_id": "***",
"jti": "***",
"status": "Confirmed"
}Does this status indicate the payment status (the payment instruction state at Nordea after SCA) or the authorization status (whether the user successfully authenticated)? Specifically, does "Confirmed" mean the payment is accepted and pending settlement, or just that the user completed the authorization step?
A:
The status in the JWT represents the payment status. In this example, the signing/SCA process has been completed, and the payment has been confirmed and registered in backend systems with the status "Confirmed."
Note: The status "Confirmed" does not indicate the final payment status. You need to retrieve the updated payment status by making calls to:
GET /personal/v5/payments/{paymentId}
until you get the final payment status. See: