> ## Documentation Index
> Fetch the complete documentation index at: https://docs.yapily.com/llms.txt
> Use this file to discover all available pages before exploring further.

# N26

## Links

* [N26 Open Banking Support](https://support.n26.com/en-eu/security/open-banking-psd2/psd2-open-banking-for-third-party-providers)

## Scopes

* Account Information 🔒
* Payment Initiation 🔒

## Preconditions

* Access requires active eIDAS Certificates to be uploaded to dashboard

1. Upload your eiDAS certificates (QWAC and QSEAL) into Yapily's [certificate vault](https://console.yapily.com/certificates).
2. Add **N26** from the **Live** tab to your [Yapily Console](https://console.yapily.com/applications) application.
3. Add this institution into your app from the `Live` tab and configure the institution by selecting the `certificates` from the dropdown.
4. Select your `QSEAL` and `QWAC` certificates from the relevant drop-downs lists then click *Save registration* to save the certificates.

See [accessing the APIs](https://developers.sozialbank.de/#/apis/22/136#accessing-the-ap-is) for sandbox login details.

## Notes

* N26 only support European-destined SEPA payments. International, Periodic or Scheduled payments are not available at this time.

### AIS

For the accounts flow we are using [Pre-Auth Decoupled](/open-banking-flow/user-authorisation/pre-authorisation). After a call to [POST Create Account Pre-authorisation Request](/api-reference/authorisations/create-pre-authorisation), the Consent needs to be updated with the [PUT Create Account Authorisation Request](/api-reference/authorisations/update-account-pre-authorisation). For N26, a call to this PUT endpoint will give an authorisation status of `AWAITING_DECOUPLED_AUTHORIZATION`. This is to inform the TPP that the user must authenticate on their device rather than following a second redirect URL. To check on the status of this SCA, the [GET Get Consent](/api-reference/consents/get-consent) endpoint can be queried; the status will update to `AUTHORIZED` once the consent is approved.

### PIS

For the payments flow we are also using [Pre-Auth Decoupled](/open-banking-flow/user-authorisation/pre-authorisation). After a call to [POST Create Payment Pre-authorisation Request](/api-reference/authorisations/create-payment-pre-authorisation), the Consent needs to be updated with the [PUT Create Payment Authorisation Request](/api-reference/authorisations/update-payment-pre-authorisation). For N26, a call to this PUT endpoint will give an authorisation status of `AWAITING_DECOUPLED_AUTHORIZATION`. This is to inform the TPP that the user must authenticate on their device rather than following a second redirect URL. To check on the status of this SCA, the [GET Get Consent](/api-reference/consents/get-consent) endpoint can be queried; the status will update to `AUTHORIZED` once the consent is approved. There are no refresh tokens allocated for PIS and each access token is tied to a single payment. This means that after access token expiry (currently 15 minutes), the payment details will not be able to be retrieved (this is a restriction from N26).

## Payments

* SEPA Instant payment rail is supported
* For Hosted SEPA Instant payments PSU is required to accept the T\&C on the app which appear when during the first submission of a manual SEPA instant Payment
* IBAN is required for domestic single payment

  **Note**: International, Periodic and Scheduled payments are not supported by N26 at this time

## Support

If you require technical support with certificate management, please contact [Support](/resources/support).