PSD2 in 2015: Designing payment APIs as a business process
A retrospective on the 2015 payment services directive, with practical implications for consent, customer journeys and reconciliation.
Archive retrospective · Topic year 2015
The 2015 framework clarified service roles
EU Directive 2015/2366 addressed payment initiation and account information as distinct services. Its adoption date should not be confused with the timing of later technical rules. Teams need to explain which organization services an account and which can initiate a request on the customer’s behalf. Entering a service does not transfer unrestricted access. Describe the permission, its purpose and affected data in the customer journey.
Make the recorded permission match the screen
A person may grant access to transaction history for a summary. That is separate from permission to make payments or retain data indefinitely. Match the consent interface with the backend scope and duration. Withdrawal should prevent further collection and trigger the appropriate retention handling. Customer support needs to see whether the withdrawal has taken effect. A consent checkbox is only part of the operating process.
A payment status is more than an HTTP code
A request acceptance does not prove that money moved. Record initiation, pending status, final result and reconciliation separately. After a network interruption, check the existing transaction identifier before opening another request. Give support staff a way to trace the initiator, the assigned payment ID and the source of the final status without putting sensitive payment material into ordinary logs.
Test a complete business process
Walk through a completed payment, an abandoned payment and one with an ambiguous response. Reconcile what the customer sees with back-office records. Describe which steps are safe to repeat before enabling them in support tools. For current compliance decisions, use the applicable rules for the organization and jurisdiction. This article uses the 2015 framework to explain design and operational decisions.
Take a working example into real usage
A solution is not production-ready merely because a demo works. Test malformed input, access denial, network failure, timeouts, concurrency and retries. Keep API contracts explicit and display actionable errors in the interface. Verify both desktop and mobile layouts. Safe defaults, observability and reproducible tests reduce long-term maintenance cost.
Publish and maintain with measurements
Document the original problem, impacted screens and changed behavior before release. Test database compatibility, permissions and performance. A healthy HTTP response is not enough: validate rendered content and key user journeys. Retain application and data backups so a failed deployment can be rolled back responsibly.
Comments
No comments yet. Be the first to contribute.
Reading “PSD2 in 2015: Designing payment APIs as a business process” raised this question for me: results should be tested under different filters.
Editor note: Results can vary by scale. Cost, latency and user experience should be compared together.
The learning curve and accessibility also matter for actual users.
A practical case study with load testing or a pilot would help establish the trade-offs.
✎ Write a comment