An open banking service that allows an approved third party to request payments from a user’s bank account. It is more sensitive than read-only data access because it directly affects funds movement and requires stronger accountability, validation, and revocation controls.
What a Payment Initiation Service Does
A payment initiation service sits between a customer, their bank, and a regulated third party that is allowed to request a payment. Its core role is not data display, but transaction trigger and payment creation, which makes the service operationally closer to funds movement than to ordinary account access.
That distinction matters because the service can directly influence whether a payment is created, rejected, or modified. Even when the user remains in control of authorisation, the service must preserve the integrity of the request, the payment context, and the approval path.
Why Payment Initiation Is More Sensitive Than Read-Only Access
Read-only access exposes information; payment initiation can move money. That changes the threat model because abuse can produce immediate financial loss, fraudulent transfers, dispute complexity, and pressure on customer support and recovery processes. In practice, the trust boundary is tighter than for account information services, and the acceptable tolerance for ambiguity is much lower.
The service therefore depends on strong validation of the payment intent, clear consent boundaries, and reliable confirmation of the user’s decision. Where payment data can be altered in transit or the requested payee is not tightly verified, the service can become a fraud enabler rather than a controlled banking integration.
For broader regulatory and control context, the EBA rules that shape access, accountability, and security expectations for payment service providers are summarised in EBA ICT and Security Risk Guidelines Guide.
Control Boundaries, Consent, and Transaction Integrity
Payment initiation services are only safe when the request, the authorisation, and the execution step are bound together. That usually means explicit consent, strong request integrity, and a design that prevents silent substitution of amount, beneficiary, or purpose. Open banking implementations often use fine-grained authorisation patterns so the third party can request only the transaction the user approved, not a broader banking capability.
This is why transaction-specific authorisation is such an important design principle. A general access token or broad consent scope is too blunt for a function that can initiate payments, especially when the user experience is asynchronous or the approval journey crosses multiple systems. The service should also support revocation and expiry in a way that lets the customer or bank stop future requests cleanly.
The best-known protocol pattern for this kind of fine-grained transaction consent is OAuth Rich Authorization Requests (RAR) Guide.
Operational Failure Modes and Accountability
The main failure modes are not just technical outages. They include misdirected payments, overbroad permissions, weak third-party onboarding, poor dispute evidence, and unclear responsibility when something goes wrong. In regulated payment flows, accountability is part of the control design: the bank, the third party, and the customer all have distinct roles that must be traceable.
That means logging, reconciliation, and exception handling are not optional extras. If the service cannot prove what was requested, who approved it, and what payment was executed, it becomes difficult to distinguish legitimate use from manipulation or error. This is especially important when a payment initiation interface is embedded inside a larger open banking or fintech journey.
For the payment-sector control environment around open banking and fraud liability, the broader policy landscape is mapped in Online Fraud Regulation Map.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP API Security Top 10 addresses the attack and risk surface, while NIST SP 800-53 Rev 5 sets the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-6 — Least Privilege | Payment initiation needs tightly scoped access to avoid overbroad transaction authority. |
| IA-2 — Identification and Authentication (Organizational Users) | Approved payment actors must be strongly authenticated before initiating funds movement. | |
| AU-2 — Audit Events | Payment initiation depends on traceable records of requests, approvals and execution. | |
| Recommendation — Limit each third party to the minimum transaction and account access required. Require strong authentication for users and operators who can initiate payments. Log initiation, approval, execution and revocation events for payment transactions. | ||
| OWASP API Security Top 10 | API5 — Broken Function Level Authorization | An initiation API must prevent callers from invoking payment functions they are not authorised for. |
| API2 — Broken Authentication | Payment initiation relies on reliable authentication of the third party and user session. | |
| Recommendation — Enforce function-level checks before any payment request is accepted. Verify caller and session authenticity before authorising payment initiation. | ||
Practitioner Guidance
Why practitioners should care: Payment initiation is a funds-moving capability, so it needs stronger governance than account data access. Treat onboarding, consent scope, revocation, and post-transaction traceability as first-order controls, not integration details.
What to watch for: Pay close attention to broad consent designs, ambiguous beneficiary confirmation, weak third-party assurance, and poor evidence of who approved the payment and when. These are the conditions that most often turn a valid initiation channel into a fraud or dispute problem.
Practitioner takeaway: If the service cannot tightly bind user intent to the executed payment, the control model is too weak for the risk profile.
Related resources from NHI Mgmt Group
- How should payment service providers build a transaction risk analysis programme that helps merchants keep checkout friction low under SCA?
- Why do payment service providers face higher fraud risk than many other fintech firms?
- How should payment service providers approach PCI DSS v4.0 scope revalidation before the deadline?
- How should payment service providers use fraud controls to improve merchant acceptance rates without adding checkout friction?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org