ADYEN N.V. LONDON BRANCH

ADYEN N.V. LONDON BRANCH

 

OB Standards

This Section applies to ASPSPs that have implemented OB Standards


-Have you Implemented OB Standards?

  • Yes
  • No


Open Data - Which version have you Implemented?

  • None
  • V2.2
  • V2.3
  • V2.4


Read/Write API Specification Implemented or planning to implement

(Lowest version = Current, Highest version = Planned)

  • V3.0
  • V3.1
  • V3.1.1
  • V3.1.2
  • V3.1.3
  • V3.1.4
  • V3.1.5
  • V3.1.6
  • V3.1.7
  • V3.1.8
  • V3.1.9
  • V3.1.10
  • V3.1.11
  • V4.0


Read/Write API - Which date are you planning to implement your latest version?

Since 1 Feb 2025 v.4.0 is live

Have you implemented v4.0 information flows, if not date planned to Implement?

  • Already Implemented
  • Planning to implement
  • Not planning to implement 


Dynamic Client Registration - Which version have you Implemented or planning to implement?

(Lowest version = Current, Highest version = Planned)

  • None
  • V3.1
  • V3.2
  • V3.3


DCR - Which date are you planning to implement your latest version?


Have you implemented Trusted beneficiaries, if not date planned to Implement?

  • Already Implemented
  • Planning to implement
  • Not planning to implement 


Have you implemented Reverse Payments, if not date planned to Implement?

  • Already Implemented
  • Planning to implement
  • Not planning to implement 


Have you implemented ECA Standard?

  • Already Implemented
  • Planning to implement
  • Not planning to implement 


ECA Implementation details


Contact: [enter contact details for the relevant person(s) at your organisation]

[You can use this space to provide your status with respect to the Standard]

Have you implemented Bulk/File Payments?

  • Already Implemented
  • Planning to implement
  • Not planning to implement 


Have you implemented VRP – Sweeping, if not date planned to Implement?

  • Already Implemented
  • Planning to implement
  • Not planning to implement 


Have you implemented VRP non-Sweeping, if not date planned to Implement?

  • Already Implemented
  • Planning to implement
  • Not planning to implement 

Contact: [enter contact details for the relevant person(s) at your organisation]

[You can use this space to provide implementation details relevant to VRP]

PISP - Single Payment Limit

£


PISP - Daily Payment Limit

£


How many months of transaction do you provide?



Have you implemented TRIs (Transactional Risk Indicators), if not, date planned to Implement?

No


What is your approach to Implementing TRIs?

  • Accept payload with TRI fields – Process all fields
  • Accept payload with TRI fields – Ignore all fields
  • Reject payload with TRI fields – Error back to TPP
  • Accept payload with TRI fields – Process few fields (Provide list of accepted fields)  



 

SCA-RTS 90-day reauth Implementation


Which date are you planning on implementing the SCA reauthentication exemption?

31 July 2024


What is your approach to token management to enable application of the reauthentication exemption? (see link to FCA guidance)

Our access token lasts 24h and the refresh one up to 90 days.

Initial one goes through SCA.

Reauth approach: We will issue new access and refresh tokens based on the expiration or previous authorization from PSU

Example approach:
Issue a long-lived refresh token during one final SCA, with refresh token rotation implemented.

[Please use this space to provide more details on your approach]

Article 10A - Endpoints exempt of SCA-RTS

  • Accounts
  • Transactions (90days)
  • Balances
  • Standing orders
  • Direct debits
  • Beneficiaries
  • Products
  • Offers
  • Parties
  • Scheduled Payments
  • Statements


Article 10A - Endpoints not exempt of SCA-RTS

  • Transactions (more than 90days)
  • Standing orders
  • Direct debits
  • Beneficiaries
  • Products
  • Offers
  • Parties
  • Scheduled Payments
  • Statements


Article 10A - Maximum time period after authentication

Time to complete SCA: 10’
Access Token valid for 24h

Please specify the time period in minutes

SCA-RTS implementation status (updated by OBL PS team only)


Planned / In-progress / Implemented / TBC


 

Security Profile


-Which Security profile have you Implemented or planning to implement?

(Lowest version = Current, Highest version = Planned)

  • OB Security Profile (Legacy)
  • FAPI (ID2)
  • FAPI 1 Advanced
  • Other (Please define) 


Security Profile - Next Planned Version Implementation Date

FAPI 1.0 Advanced since December 2024


CIBA Profile - Implemented or planning to implement

(Lowest version = Current, Highest version = Planned)

  • None
  • CIBA
  • CIBA FAPI Profile


CIBA Profile - Next Planned Version Implementation Date

 N/A


Security Profile Certification date?

 N/A


Token Endpoint Authentication Methods Supported

  • client_secret_post
  • client_secret_basic
  • client_secret_jwt
  • tls_client_auth
  • Private_key_jwt


Planned date to Cease support for client id and client secret token endpoint authentication

N/A


POST-BREXIT POST TRANSITION - Certificates Accepted (from 1st Jul 2021)

  • eIDAS QWAC
  • eIDAS QSealC
  • OB legacy (obtransport, obsigning)
  • OBWAC
  • OBSeal
  • Other (Please define) 



 

Customer Journey


-What is your approach to Implementing OBL Customer Experience Guidelines (CEG)?

(tick all that apply)

  • Already Implemented
  • Planning to implement or upgrade
  • Not planning to implement CEG

Since we are B2B2X provider our platforms are the ones implementing UX

Which version have you implemented or planning to implement?

(Lowest version = Current, Highest version = Planned)

  • V3.1.2
  • V3.1.3
  • V3.1.4
  • V3.1.5
  • V3.1.6
  • V3.1.7
  • V3.1.8
  • V3.1.9
  • V3.1.10
  • V3.1.11
  • V4.0


Which date are you planning to implement your latest CEG version?



Redirection Model

  • App to App redirection
  • Decoupled authentication
  • Embedded Flow
  • Bespoke User Journeys

When customer gives consent through the TPP site the Bank ABC login page (Auth0) is used to authenticate customer consent.  The customer provides username, password and OTP during login.  The system verifies credentials with the bank.


 

PSD2


-Which Directory are you using as your Trust Framework?

Open Banking


Are you caching the Directory?

No


Transaction IDs Supported

Yes

  1. ASPSPs provide a Unique, Immutable TransactionID from their core system

  2. ASPSPs generate a Unique TransactionID from a set of Immutable fields

  3. ASPSPs specify field(s) for TPP to generate a Unique Transaction Identifier

  4. ASPSPs provide neither a TransactionID nor the method by which TPPs can generate one

Are you Seeking Fallback Exemption?

  • Yes
  • No


Article 10 - Maximum time period after authentication


Time to complete SCA: 10’
Access Token valid for 24h

Article 10 - Endpoints exempt of SCA

None

Major Milestones



Brand(s)




 

ASPSP Dev Portal and Contact Details


Location of Well Known Endpoints

Well-known: https://openbanking-oidc-live.adyen.com/obuk/oidc/.well-known/openid-configuration

DCR API: https://openbanking-uk-psd2-live.adyen.com/obuk/open-banking/v4.0/dcr/register

Account Access API: https://openbanking-uk-psd2-live.adyen.com/obuk/open-banking/v4.0/aisp/

Funds confirmation API: https://openbanking-uk-psd2-live.adyen.com/obuk/open-banking/v4.0/cbpii/

Payments API:https://openbanking-uk-psd2-live.adyen.com/obuk/open-banking/v4.0/pisp/


Modified Customer Interface URL (if applicable)



Dev Portal URL



Test Facility URL



Brand Landing Pages URL


[You can use this space to explain your guidance on using Brand logos]

ASPSP Support Desk Email or Phone Number

(including queries about consent success rates) 


openbanking@adyen.com