Page Comparison

_{S. No.}

_{Requirements and Considerations}

_Participant

_{Implementation Requirements}

 ₁

_{ASPSP selection}

_{AISPs must ask the PSU to identify their ASPSP before requesting consent so that the consent request can be constructed in line with the ASPSP’s data capabilities (which the ASPSP must make available to all TPPs). ASPSP Implementation guides, which are located on the Open  Banking Developer Zone will have information about the ASPSP’s data capabilities.}

 _AISP

 _Required

₂

_{AISPs must provide PSUs with sufficient information to enable PSUs to make an informed decision, for example, detail the purpose for which the data will be used (including whether any other parties will have access to the information) the period over which it has been requested and when the consent for the account information will expire (consent could be on-going or one-off)}

 _{AISPs must display the company’s trading name/brand name (i.e. the Client Name) to the PSU during the setup and revocation of consent. If the AISP is only trading with its registered company name then it must display that name to the PSU} 

 _{If the AISP is not the user/customer-facing entity and there is an Agent who is acting on behalf of the AISP, then the Agent must make the PSU aware that they are acting as an agent on behalf of the AISP and must also, display the AISP’s full trading name/brand name or registered company name whichever is the user/customer-facing brand of the AISP}

 _{AISPs must also, populate the Agent company name in the ‘On behalf of’ field of the software statement, in order to inform the ASPSP about the agency relationship and allow the ASPSP to be able to display this information to the PSU (please refer to item #5). Only in instances where there is an Agent acting on behalf of the AISP, the ‘On Behalf of’ name must be displayed to the PSU. AISPs must not populate the ‘On behalf of’ field with the details of their TSP}

 _{For examples of what names should be displayed, please refer the section “Sample displays by TPP” below}

 _AISP

 _Required

₃

_{The AISP must provide the PSU with a description of the data being requested using the structure and language recommended by BOBF (see Data Cluster Structure & Language below) and ensure that this request is specific to only the information required for the provision of their account information service to the PSU}

_{The AISP must present the data at a Data Cluster level and allow the PSU to expand the level of detail to show each Data Permission. The AISP should only present those data clusters relevant for the product type in question. Where the request is for multiple product types then the detail shown in the data cluster should explain to the user/customer the product types to which it applies or state that it is shared across multiple product types.}

_{AISPs must allow the PSUs to choose the type of data to be collected and used by the AISP. Once PSU has consented, the PSU will be directed to their ASPSP. Please refer section Effective use of redirection screens for relevant messaging}

_{CX Considerations:}

_{Take points from ACCC document}

_AISP

_Required

₄

_{CX consideration:}

_{AISP should make the PSU aware on the inbound redirection screen that they will be taken to their ASPSP for authentication for account access}

_{ASPSP allows PSUs to perform a SCA Authentication (including dynamic linking). The ASPSP authentication must have no more than the number of steps that the PSU would experience when directly accessing the ASPSP channel}

_{CX consideration:}

_{ASPs should provide messaging to inform PSUs that they will be taken to their ASPSPs to complete the process}

_{Example wording: "You will be securely transferred to YOUR ASPSP to authenticate and choose the account for accessing information"}

_AISP

_Required

₅

_{Information summary}

• _{ASPSPs must display the TPPs’ trading name/brand name (i.e. the Client Name in the software statement) to the PSU during authentication screens and on any Access Dashboards. They do not need to display the registered company name of the TPP even if it is different
  If there is an Agent acting on behalf of the TPP, ASPSPs must also display the Agent company name (as captured in the ‘On behalf of’ field of the software statement) to the PSU. (Please note that ASPSPs can only show the Agency/On Behalf field only in cases where this information has been provided by AISPs).}

• _{ASPSPs must allow PSUs to select the account for data sharing with AISP}

• _{ASPSPs must not seek confirmation of the consent that has already been provided by the PSU to the AISP}

• _{Once the PSU has selected the account(s), refer to section Effective use of redirection screens for redirection messaging}

_{For examples of what names should be displayed, please refer the section “Sample displays by TPP” below}

_{CX consideration:}

_{If the ASPSP provides an option for the PSU to view the data they have consented to share with the AISP as supplementary information, this must be done using the structure and language recommended by BOBF (see Data Cluster Structure & Language below). Display of such information must not be provided to the PSU as a default}

_ASPSP

_Required

 ₆

 _{The AISP should  confirm the successful completion of the account information request to the PSU}

_AISP

 _Required

_{S. No.}

_{Data Cluster Language}

_{API End Points}

_Permissions

_{Description of the field}

_{Information Available}

 ₁

_{Your Account Details}

_Accounts

_{Accounts Basic}

_{Any other name by which you refer to this account and/or the currency of the account}

_{Currency of the account, Nickname of account (E.g. ‘Jakes Household account’)}

_{Accounts Detail}

_{Your account name, number and sort-code}

_{Account Name, Sort Code, Account Number, IBAN, Roll Number (used for Building Society) (plus all data provided in Accounts Basic)}

_Balances

_Balances

_{Your account balance}

_{Amount, Currency, Credit/Debit, Type of Balance, Date/Time}

_{All where IBAN is available}

_IBAN

_{Your card number}

_{IBAN masked or unmasked depending on how ASPSP displays online currently}

₂

_{Your Regular Payments}

_{Beneficiaries}

_{Beneficiaries Basic}

_{Payee agreements you have set up}

_{List of Beneficiaries}

_{Beneficiaries Detail}

_{Details of Payee agreements you have set up}

_{Details of Beneficiaries account information (Name, Sort Code, Account) (plus all data provided in Beneficiaries Basic)}

_{Standing Orders}

_{Standing Order Basic}

_{Your Standing Orders}

_{SO Info, Frequency, Creditor Reference Info, First/Next/Final Payment info}

_{Standing Order Detail}

_{Details of your Standing Orders}

_{Details of Creditor Account Information (Name, Sort Code, Account) (plus all data provided in Standing Order Basic)}

_{Direct Debits}

_{Direct Debits}

_{Your Direct Debits}

_{Mandate info, Status, Name, Previous payment information}

_{Scheduled Payments}

_{Scheduled Payments Basic}

_{Recurring and future dated payments}

_{Scheduled dates, amount, reference. Does not include information about the beneficiary}

_{Scheduled Payments Detail}

_{Details of recurring and future dated payments}

_{Scheduled dates, amount, reference. Includes information about the beneficiary}

₃

_{Your Account Transactions}

_Transactions

_{Transactions Basic Credits}

_{Your incoming transactions}

_{Transaction Information on payments made into the user/customer’s account (Reference, Amount, Status, Booking Data Info, Value Date info, Transaction Code(-M7] ). Does not include information about the entity that made the payment}

_{Transactions Basic Debits}

_{Your outgoing transactions}

_{Same as above, but for debits}

_{Transactions Detail Credits}

_{Details of your incoming transactions}

_{Transaction Information on payments made into the user/customer’s account (Reference, Amount, Status, Booking Data Info, Value Date info, Transaction Code). Includes information about the entity that made the payment}

_{Transactions Detailed Debits}

_{Details of your outgoing transactions}

_{Same as above but for debits}

_{Transactions Basic}

_{Your transactions}

_{Transaction Information on payments for both credits in and debits out of the user/customer’s account (Reference, Amount, Status, Booking Data Info, Value Date info, Transaction Code). Does not include information about the payer/payee}

_{Transactions Detail}

_{Details of your transactions}

_{Transaction Information on payments made both credits in and debits out of the user/customer’s account (Reference, Amount, Status, Booking Data Info, Value Date info, Transaction Code). Includes information about the payer/payee}

₄

_{Your Statements}

_Statements

_{Statements Basic}

_{Information contained in your statement}

_{All statement information excluding specific amounts related to various balance types, payments due etc.}

_{Statements Detail}

_{Details of information contained in your statement}

_{All statement information including specific amounts related to various balance types, payments due etc.}

₅

_{Your Account Features and Benefits}

_Products

_Product

_{Product details – fees, charges, interest, benefits/rewards}

_{Refers to Section Product details below (the fees, charges, interest, benefits/rewards). Applicable to PCA and BCA}

_Offers

_{Offers available on your account}

_{Balance transfer, promotional rates, limit increases, start & end dates}

₆

_{Contact and party details}

_{Account specific:}

• _Parties

• _Party

_Party

_{The full legal name(s) of account holder(s)}

_{Address(es), telephone number(s) and email address(es)}

_{The name of the account. Full Legal Name(s), Account Role(s), Beneficial Ownership, Legal Structure, Address or addresses, telephone numbers and email address as held by the bank/card issuer and party type (sole/joint etc.)}