Law / United Kingdom

Access to payment accounts for payment initiation, account information and card-based confirmation of funds

Payment Services Regulations 2017, reg. 69

In force since .

A data subject rights rule binding public and private bodies.

Criminal exposure
No
Enforcement body
Financial Conduct Authority
Obligation class
Data subject rights, Consent, Security

What it requires

  • It reaches you if you are a payment service provider, as regulation 2(1) defines the term: an authorised or small payment institution, a registered account information service provider, an electronic money institution, a credit institution or one of the other bodies it names, and the payment account is accessible online (regs. 69(1), 70(1)).
  • If you are the payer's account servicing payment service provider, communicate securely with the payment initiation service provider or account information service provider in accordance with the technical standards made under regulation 106A (regs. 69(2)(a), 70(2)(a)).
  • If you are the account servicing payment service provider, provide or make available to the payment initiation service provider, immediately after receipt of the payment order, all information on the initiation of the payment transaction and all information accessible to you about its execution (reg. 69(2)(b)).
  • If you are the account servicing payment service provider, treat a payment order or a data request from a payment initiation service provider or account information service provider in the same way as one received directly from the payer, unless you have objective reasons for treating it differently, and do not require the provider to enter into a contract first (regs. 69(2)(c), (d), 70(2)(b), (c)).
  • If you are an account information service provider, do not provide account information services without the payment service user's explicit consent, and access only information from designated payment accounts and associated payment transactions (reg. 70(3)(a), (d)).
  • If you are an account information service provider, do not request sensitive payment data linked to the accounts accessed, and do not use, access or store any information for any purpose except the account information service the user explicitly requested (reg. 70(3)(e), (f)).
  • If you are a payment initiation service provider, never hold the payer's funds in connection with the service, do not store sensitive payment data, request only the information the service needs, and use, access or store information only for the service the payer explicitly requested (reg. 69(3)(a), (e), (f), (g)).
  • If you are a payment initiation service provider, provide information about the payer to no one but the payee, and to the payee only with the payer's explicit consent (reg. 69(3)(c)).
  • If you are an account information service provider or a payment initiation service provider, ensure the payer's personalised security credentials are available to no other party apart from the issuer and are transmitted through safe and efficient channels, and identify yourself to the account servicing payment service provider for each session or payment order (regs. 69(3)(b), (d), 70(3)(b), (c)).
  • If you issue card-based payment instruments, request confirmation of the availability of funds only where the payer has given explicit consent and has initiated a payment using your card-based instrument, and do not store the confirmation or use it for any purpose other than executing that transaction (reg. 68(3), (8)).
  • If you are the account servicing payment service provider, give the requesting issuer a yes or no answer immediately where the account is accessible online and the payer has given you explicit consent for that issuer's requests, and do not include a statement of the balance or block funds (reg. 68(4), (5), (7)).

These lines are LexLint's reading of the law's text.

What this law does

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

Research summary

Legal information, not legal advice. This is LexLint's own research summary of a public legal source, and it creates no attorney-client relationship. For decisions that matter, consult qualified counsel in the relevant jurisdiction. About LexLint

Regulations 68 to 70 of the Payment Services Regulations 2017 give a payment service user the means to have payment account data shared with a payment initiation service provider, an account information service provider or a card-based payment instrument issuer, and set the duties on the account servicing payment service provider and on each recipient.

Regulation 69(2) requires the payer's account servicing payment service provider to give the payment initiation service provider all information on the initiation of the payment transaction. Regulation 69(3) requires a payment initiation service provider not to store sensitive payment data of the payment service user.

Regulation 70(2) requires the account servicing payment service provider to treat a data request from an account information service provider in the same way as a data request received directly from the payer. Regulation 70(3) requires an account information service provider not to provide account information services without the payment service user's explicit consent.

Regulation 70(3) also requires it not to use, access or store any information for any purpose except the account information service the user explicitly requested. Regulation 68(8) prevents a card-based payment service provider from storing the confirmation of funds. The FCA may impose a penalty of such amount as it considers appropriate on a payment service provider that has contravened a requirement of the Regulations.

Section 1 of the Data (Use and Access) Act 2025 states that Part 1 confers powers on the Secretary of State and the Treasury to make provision in connection with access to customer data and business data.

When LexLint raises it

When your app profile says your app is a bank or is a payment provider.

Back to the example  ·  Lint your app

Page updated .