
A Payment Initiation Service Provider (PISP) is a regulated third-party provider that initiates a payment directly from a customer’s bank account to a merchant or payee, with the customer’s consent and authentication. Instead of paying through a card network, wallet balance or manual bank transfer, the user authorises the PISP to trigger the payment from their bank account.
The term is most commonly used in open banking frameworks such as PSD2 in Europe and the UK Payment Services Regulations. A PISP does not usually hold customer funds. Its role is to securely initiate the payment instruction between the customer’s bank and the recipient.
In simple terms: a PISP helps a user pay directly from their bank account through a regulated third-party interface.
PISPs became important because open banking created a regulated way for licensed third parties to access payment accounts, subject to user consent and strong authentication. This opened the door for account-to-account payments that can be faster, more transparent and potentially less dependent on card rails.
For merchants, payment initiation can reduce checkout friction in markets where open banking payment rails are mature. For fintechs, it creates opportunities around embedded payments, bill payments, subscription collections, B2B payments and instant account-to-account checkout.
India does not use PISP as a mainstream standalone licensing label in the same way as the UK or EU. However, the underlying idea of consent-based, account-linked digital payments has parallels in India’s digital payment ecosystem, especially through UPI, payment aggregators and broader open finance discussions. The regulatory terminology and operating permissions, however, are different and should not be mixed.
A typical PISP flow looks like this:
1. The customer chooses account-to-account payment at checkout.
2. The PISP redirects or connects the customer to their bank’s authentication flow.
3. The customer gives consent and authenticates the payment.
4. The PISP sends the payment initiation request to the bank.
5. The bank executes the payment and confirms status back to the PISP or merchant.
The core principle is that the user remains in control. The PISP cannot initiate payments without consent, and regulated frameworks require security, authentication, transparency and customer protection measures.
PISPs matter because they represent a shift from card-led payment experiences to bank-account-led payment experiences. For businesses, this can affect payment cost, settlement speed, customer authentication, checkout design and reconciliation.
Potential benefits include:
• Direct account-to-account payment initiation
• Reduced dependence on card credentials
• Better payment status visibility in some open banking flows
• Useful structure for bill payments, B2B collections and high-value transfers
The main caution is jurisdiction. A PISP is a regulatory concept tied to specific open banking laws. Businesses operating in India, the UK, EU or other markets should map the local licensing, consent, data-sharing and payment aggregation requirements before using the term in product, legal or compliance material.