/
UBIDAC

UBIDAC

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
  • V4.0.1


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



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
  • V3.4


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 Bulk/File Payments?

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

[Please use this space to provide more details on bulk/file payments implementation]

(e.g. maximum value/volume of payments per file, maximum file size, requirement for payees to be existing trusted beneficiaries, etc)

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?



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?


Ulster Bank Ireland DAC serves only Ireland domiciled accounts, hence it will implement the EBA rules in re. SCA instead of FCA rules. This means that it will extend the current 90-day re-authentication period to 180-days. We are planning to deliver this change by  

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


Not Applicable for UBIDAC.


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


Please specify the time period in minutes

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


EBA SCA RTS implementation: In-progress

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



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



Security Profile Certification date?

 


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



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


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
  • V4.0.1


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

TBC


Redirection Model

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

Journeys are specific to RBSG / UBIDAC but align with CEG

PSD2

-Which Directory are you using as your Trust Framework?

Open Banking


Are you caching the Directory?

No

Directory Caching will be delivered by 24 February 2020 as part of PSD2 onboarding

Transaction IDs Supported

Yes - August 2019

Transaction id's are provided against each booked transaction that are returned on the transactions endpoint

Are you Seeking Fallback Exemption?

  • Yes
  • No


Article 10 - Maximum time period after authentication

N/A

RBSG / UBIDAC are adopting Article 10 Exemption for 90 day reauthentication, no further restrictions are being applied under Article 10

Article 10 - Endpoints exempt of SCA

N/A

RBSG / UBIDAC are adopting Article 10 Exemption for 90 day reauthentication, no further restrictions are being applied under Article 10

Major Milestones

V1.1 deprecation  
V3.1 roadmap

International Payments for Commercial Banking Customers - Q1 2020

SEPA MTS Bulk / Batch Payments - Q1 2020

P2 Two Way Notice of Revocation - Q1 2020

P8 SCA Exemptions - Q1 2020

API specification v3.1.4 & CEG v3.1.4 - Q1 2020

Uplift to PS256 encryption standard - Q2 2020

P15 Access Dashboards - Q2 2020


Brand(s)



ASPSP Dev Portal and Contact Details

Location of Well Known Endpoints

OB Technical Directory


Modified Customer Interface URL (if applicable)



Dev Portal URL

https://www.bankofapis.com/


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) 

~APIServiceDesk@rbs.com


Key Implementations

High Cost Credit

UBIDAC - HCC.xlsx


Deliveries of these SCA solutions will continue across the rest of 2019 will some delivered in Q1 2020

Customer Journey stage

Mobile (Direct Channel)

E-banking (Direct Channel)

Bankline (Direct Channel & Open Banking)

Open Banking Browser

Open Banking App to App

Customer Journey stage

Mobile (Direct Channel)

E-banking (Direct Channel)

Bankline (Direct Channel & Open Banking)

Open Banking Browser

Open Banking App to App

Logging in to identify themselves as a customer and gain access to in scope accounts

SCA @ Login

Steps:

Customers can use biometrics (as per the setup
of their device/customer preference) or passcode

Device binding will run in the background during
authentication

 

SCA @ Login

Steps:

Customer ID Plus Partial PIN Password Plus Device Profiling

SCA @ Login

Steps:
Customer and User IDs Plus Partial Password And using Card And PIN for Challenge and Response

SCA @ Login

Steps:

Customer IDs Plus Partial PIN Password AND Device Profiling

SCA @ Login

 Steps:

Customers can use biometrics (as per the setup of their device/customer preference) or passcode

Device binding will run in the background
during authentication

Making a payment from in scope accounts

No further SCA required for payments to trusted beneficiaries.

SCA via card and reader required for payments
above low value payment limit to non trusted
beneficiaries.

SCA for payments to non-trusted beneficiaries

Further SCA required for Payments using Card and PIN for Challenge and Response

Step up to One Time Passcode or Card & Reader for payments

No further SCA required for payment

 

LIVE

LIVE

Q1 2020

November 2020

LIVE