PISP license in Spain
"We handle the entire PISP authorization process with the Bank of Spain: regulatory application, technical documentation, business plan and security policy."
Get your license and operate as a PISP (payment initiation service provider) with full legal certainty: PSD2 regulatory advice, registration with the Bank of Spain, legal structuring, AML/CFT compliance and technical documentation for payment institutions and fintechs.
"We handle the entire PISP authorization process with the Bank of Spain: regulatory application, technical documentation, business plan and security policy."
"We design the PSD2 compliance framework for your PISP: strong customer authentication (SCA), account access interfaces (APIs), consent management and user protection."
"We implement an anti-money laundering system tailored to the PISP business model: user KYC, transaction monitoring and reporting to SEPBLAC."
"We advise on the EU passport notification so you can operate as a PISP in other EU Member States from your Spanish license, with minimal additional regulatory burden."
End-to-end management of the authorization application as a PISP payment institution: descriptive report, business plan, security policies and complete regulatory documentation.
Design and implementation of the PSD2 regulatory framework for PISPs: strong customer authentication (SCA), API-based account access, consent management and incident reporting.
Implementation of an anti-money laundering system tailored to the PISP model: risk assessment, user KYC, transaction monitoring and reporting obligations to SEPBLAC.
Drafting of general terms and conditions, framework contracts for payment services, agreements with banks and TPPs, and the pre-contractual information documents required by PSD2.
Preparation of the information security policy, business continuity plan, major incident management and reporting to the Bank of Spain under PSD2.
EU passport notification to operate as a PISP in other Member States: notification procedure, local requirements and coordination with the competent authorities.
Authorization refused or withdrawn: operating as a PISP without the required Bank of Spain authorization is a very serious infringement that can lead to fines and the immediate cessation of the activity.
PSD2 non-compliance: a lack of strong customer authentication (SCA), inadequate access interfaces or incorrect consent management expose the PISP to regulatory penalties and user complaints.
Security risks and liability: PISPs are liable for losses arising from unauthorized payment transactions if they cannot prove that the user authenticated the transaction correctly.
Breach of AML/CFT obligations: PISPs are subject to anti-money laundering legislation. A lack of KYC controls and transaction monitoring can lead to SEPBLAC penalties.
Blocked European expansion: without a properly notified passport, the PISP cannot legally offer its payment initiation services in other EU Member States.
A PISP (payment initiation service provider) is a category of payment service provider regulated by the PSD2 Directive (Directive (EU) 2015/2366) that allows third parties to initiate payments from the user’s bank account, with the user’s express consent, without the user having to go to their bank directly.
The PISP acts as an intermediary between the paying user and the bank where the account is held: it initiates the payment order through the open access interfaces (APIs) that banks must make available to third parties under the PSD2 open banking framework.
PISPs are a key player in the European fintech ecosystem, enabling instant payments, card-free checkout, B2B payment solutions and new business models based on access to payment data.
A PISP (payment initiation service provider) initiates payment orders from the user’s account, while an AISP (account information service provider) only accesses the user’s account information for aggregation, analysis or data presentation, without executing payments.
Both are regulated by PSD2 and require authorization or registration with the competent supervisor, but their obligations differ: PISPs bear greater responsibility for security and authentication because they execute transactions that move funds, while AISPs operate in a read-only environment.
The same entity can obtain dual PISP + AISP authorization if its business model combines payment initiation with account aggregation, which is common in full open banking solutions.
In Spain, authorization as a PISP is obtained from the Bank of Spain, the competent authority for supervising payment institutions under Law 21/2011 on Electronic Money and Royal Decree-law 19/2018 on payment services.
The authorization process usually takes three to six months from submission of the complete application, depending on the complexity of the business model and the quality of the documentation provided.
Strong customer authentication (SCA) is one of the most demanding requirements for PISPs under PSD2. Before initiating a payment, the PISP must make sure that the user has been authenticated by their bank using at least two of the three possible factors: something the user knows (PIN, password), something they have (mobile device, card) and something they are (biometrics).
PISPs do not store the user’s online banking credentials: they access the bank’s interface (production API) using the authentication token generated in the SCA process, which secures the transaction without compromising the user’s credentials.
Correct SCA compliance is essential for the PISP to be released from liability in claims for unauthorized payment transactions.
PISPs are among the obliged entities under Law 10/2010 on the prevention of money laundering and terrorist financing, which entails a series of specific obligations tailored to the payment initiation business model.
The most relevant obligations include identifying and verifying the identity of customers (KYC), identifying the beneficial owner when the payer is a legal entity, ongoing monitoring of initiated transactions to detect anomalous patterns, and reporting suspicious transactions to SEPBLAC.
The PISP’s AML/CFT system must be adapted to its position in the payment chain: although the PISP does not hold customer funds, it has access to valuable transaction information that must be handled rigorously and confidentially.
In June 2023 the European Commission published its proposals for PSD3 and the new Payment Services Regulation (PSR), which will bring significant changes for PISPs: stronger rights of access to bank interfaces, an improved liability framework for fraud, new obligations to inform users and higher interoperability requirements.
PSD3 also broadens the scope of open banking and strengthens the competitive position of PISPs vis-à-vis banks, which will have to provide higher-quality interfaces with stronger availability guarantees.
Entities already operating as PISPs under PSD2 will need to review their regulatory documentation and technical systems to adapt to the new PSD3 requirements once it is transposed into Spanish law.
Obtaining PISP authorization in Spain takes between three and six months from submission of the complete application to the Bank of Spain, although it can take longer if the authority requests additional documents or clarifications about the business model.
The cost of legal advice for obtaining a PISP license depends on the complexity of the business model, the number of payment services applied for and how well prepared the entity already is. On top of this come the Bank of Spain’s regulatory fees and the cost of technically implementing the required security systems.
Specialist advice from the start of the process significantly reduces the risk of additional requests for information from the Bank of Spain and shortens the time needed to obtain the PISP license.
PISP regulation intersects with other key areas of regulatory compliance, fintech and financial regulation. Discover the services that complement your project.
Full range of anti-money laundering services for payment institutions: risk assessment, manual, training and audits tailored to the fintech sector.
Advice for PISPs that integrate crypto-asset payments or blockchain technology: MiCA regulation, VASP registration and regulatory compliance.
Independent regulatory compliance report for PISP applications: validation of the AML/CFT framework, security policies and documentation for the Bank of Spain.
Corporate compliance programs for PISP payment institutions: whistleblowing channel, code of ethics and internal controls adapted to the financial regulatory environment.
Design and implementation of AML/CFT systems for PISPs: user KYC, transaction monitoring and preparation for SEPBLAC inspections.
Mandatory document tailored to the PISP business model: procedures, roles, approval workflows and due diligence measures under Law 10/2010.
Legal structuring of secondary sales of shares in fintechs and PISP institutions: SPA, transfer restrictions and regulatory compliance.
Criminal compliance program for payment institutions: whistleblowing channel, code of ethics and evidence of compliance for Bank of Spain inspections.
Tick the situations that apply to your business model. The more that match, the greater the need to obtain PISP authorization and specialist regulatory advice.
0 of 10 situations
Tick the situations that apply to your business model.
Everything you need to know about PISPs: the concept, the regulatory framework in Spain and the EU, the authorization process, technical requirements, AML/CFT obligations and adaptation to PSD3.
A PISP (payment initiation service provider) is a regulated payment service provider that, with the user’s express consent, accesses the account access interface (API) of the payer’s bank to send a credit transfer order on that user’s behalf, usually to complete a purchase or a B2B payment.
A PISP transaction works as follows: the user chooses to pay through the PISP’s service; the PISP redirects the user to their bank to authenticate with SCA; once the user is authenticated, the PISP sends the payment order through the bank’s API; and the bank executes the transfer, confirming to the merchant or payee that the payment has been initiated. The whole process can be completed in seconds, with no credit card and without the user having to log in to their online banking manually.
In Spain, the regulatory framework for PISPs is set out mainly in Royal Decree-law 19/2018 on payment services and other urgent financial measures, which transposed the PSD2 Directive into Spanish law. It sets the authorization requirements, transparency obligations, liability rules and penalty regime applicable to payment institutions, including PISPs.
The Bank of Spain is the competent supervisory authority for authorizing and supervising PISPs in Spain. The EBA’s Regulatory Technical Standards (RTS) complement the regulatory framework by setting the technical security requirements, the SCA specifications and the conditions for access to bank interfaces.
The authorization process for a PISP payment institution in Spain has several stages. The preliminary phase is preparing the application: drafting the program of operations, business plan, security policies, AML/CFT procedures, organizational structure and documentation on significant shareholders and senior managers.
The second stage is submission to the Bank of Spain: the application is filed electronically through the Bank of Spain’s registry. The authority has three months to decide from the date the application is complete, although in practice the process includes rounds of questions and requests for clarification that can extend the timeline.
Once authorized, the PISP is entered in the Bank of Spain Register of Institutions and in the EBA’s European register (EBA Register), which enables passporting to operate throughout the EU.
Open banking is the ecosystem that makes the PISP model possible. Under PSD2, banks and other entities that hold payment accounts (known as ASPSPs, account servicing payment service providers) must provide PISPs with dedicated access interfaces—typically REST APIs that follow standards such as Berlin Group or STET—through which PISPs can initiate payments with the user’s consent.
PISPs must be certified with each bank to access its production API, using qualified eIDAS certificates (QWAC and QSealC) issued by a qualified trust service provider. This technical certification is an essential prerequisite for the PISP’s actual operations, regardless of the regulatory authorization already obtained.
The PISP liability regime is one of the most important aspects of its regulation. When a payment transaction initiated by a PISP turns out to be unauthorized or is executed incorrectly, primary liability lies with the payer’s bank (ASPSP), which must refund the user immediately. However, if the PISP is liable for the unauthorized or incorrect transaction, it must compensate the bank.
To be released from liability, the PISP must prove that it acted correctly within its sphere of competence and that the user was authenticated in accordance with SCA requirements. That is why technical documentation and the record of each transaction are critical to the PISP’s defense against claims.
The most common mistake is starting operations without a license in the belief that the business model is covered by a PSD2 exemption. Many fintechs discover too late that their activity requires express authorization as a PISP, building up a period of irregular operation that can lead to penalties from the Bank of Spain.
Another frequent mistake is underestimating the technical requirements: obtaining eIDAS certificates, integrating with bank APIs and implementing SCA take considerable time and technical resources, which must be planned in parallel with the regulatory process, not afterwards.
Finally, neglecting the AML/CFT system from the outset is a serious risk: the Bank of Spain and SEPBLAC require PISPs to have their compliance controls up and running from the first day of activity, and the absence of these systems can prevent the license from being granted or lead to later penalties.
Key legislation, linked to the official text:
Legislation and links reviewed in .