Skip to main content

​
Scopes

  • Open Data 🌐
  • Account Information 🔒
  • Payment Initiation 🔒

​
Live Environment

Precondition: To connect to live Open Banking entities, whether you are accessing account information or initiating payments, your business must have the right regulatory permissions as per the Open Banking Guide.
  1. Upload your transport and signing certificates (PEMs) created in the Open Banking directory, along with the keys into Yapily’s certificate vault.
  2. Add First Trust Bank from the Live tab to your Dashboard application and add your Signing key Id, which can be obtained from the Open Banking Directory.
  3. Select your Open Banking transport and signing certificates from the relevant drop-downs lists then click Next.
  4. Click the ‘download the SSA’ button to download your Software Statement Assertion from the Open Banking Directory. This is the token that the Open Banking UK institutions will use during registration to verify your enrolment and possibly create your application.
  5. Log in to First Trust Bank: https://developer.firsttrustbank.co.uk
  6. Select ‘Add new Production app’. Complete the form by pasting the downloaded SSA into the SSA form field and selecting the relevant TPP roles. Click ‘Create App’. Once done, you will need to wait for the app to be approved.
  7. Copy the credentials for this app from the First Trust Bank developer portal into the credentials view for First Trust in the Yapily dashboard. Add the obtained consumer key as Key and the consumer secret as Secret. Click ‘Next’ to save.

​
Support

If you require technical support with certificate management, please contact Support.

​
Sandbox Environment

To connect to the First Trust Bank sandbox, follow the above steps while selecting First Trust Bank from the sandbox tab in step 2. The institution Id for this is firsttrustbank-sandbox. Notes: This Sandbox environment has the following issues:
  • The authorisation page uses a self signed certificate thus most browsers will prevent you from visiting.
  • The PSU access-token has a short expiration time (some minutes) and they do not support refreshing.
  • The transactions filtering is not working
  • On the second account the next link is broken and throws an error.