PaymentsJournal
No Result
View All Result
SIGN UP
  • Commercial
  • Credit
  • Debit
  • Digital Assets & Crypto
  • Digital Banking
  • Emerging Payments
  • Fraud & Security
  • Merchant
  • Prepaid
PaymentsJournal
  • Commercial
  • Credit
  • Debit
  • Digital Assets & Crypto
  • Digital Banking
  • Emerging Payments
  • Fraud & Security
  • Merchant
  • Prepaid
No Result
View All Result
PaymentsJournal
No Result
View All Result

5 API Standards PSD2 Still Hasn’t Refined:

By PaymentsJournal
January 28, 2020
in APIs, Compliance and Regulation, Debit, Digital Assets & Crypto, Emerging Payments, Open Banking, Truth In Data
0
0
SHARES
0
VIEWS
Share on LinkedIn

Open banking initiatives built around PSD2 were designed to create greater competition, innovation, and consumer choice across financial services, but inconsistent API standards continue to slow adoption and limit interoperability. Research from Mercator Advisory Group highlights how uneven security models, inconsistent functionality, fragmented data structures, and weak developer testing environments remain significant barriers to a seamless open banking ecosystem. As financial institutions and fintech providers increasingly rely on APIs to power digital payments and cloud-based services, the need for more standardized and scalable open banking frameworks has become increasingly apparent.

Don’t miss another episode of Truth In Data! Click on the red bell in the lower-left corner of your screen to receive notifications as soon as the episode publishes.

Data for today’s episode is provided by Mercator Advisory Group’s report – The Emergence of API Platforms: Open Banking and Payments Drive New Business Models.

5 API standards PSD2 still hasn’t refined:

  • Because PSD2’s requirements aren’t specific & interfaces not-standardized, open banking needs refining:
  1. Inconsistent security models across banks; some limit sessions to just their bank
  2. Inconsistent functionality; many are read-only
  3. Inconsistent interface and data models require bank-specific coding
  4. Ineffectual sandboxes for testing; currenct security model has no “guest” function
  5. Inconsistent documentation, few are multilingual and few work across banks

About Report

Mercator Advisory Group has released a report describing the technical and regulatory challenges delaying the implementation of the European Union’s PSD2 Open Banking mandate and contrasts that with the rapid growth in new application programming interface (API) driven platforms that operate in the cloud. There has been a surge in platform-as-a-service (PaaS) solutions utilizing APIs.

The report, The Emergence of API Platforms: Open Banking Drives New Business Models, identifies the technical and regulatory issues that continue to be challenges to lift-off for the European Union’s open banking vision and contrasts that situation with the structures that have driven a surge in the availability of cloud platforms that utilize APIs to enable similar services, such as payments.

“In a past report we identified the game-changing value proposition associated with internet-based application programming interfaces. This report identifies why the implementation of APIs has failed to help the EU Open Banking initiative gain liftoff even as these APIs have created a surge in the number of cloud-based platforms recently announced,” commented the author of the report, Tim Sloane, VP, Payments Innovation, and Director, Emerging Technologies Advisory Service at Mercator Advisory Group.

This research report has 20 pages and 10 exhibits.

Companies and other organizations mentioned in this report include: Bank of America, The Berlin Group, Citibank, Citizens Bank, European Banking Authority, Fidor, Financial Conduct Authority, Mastercard, Railsbank, solarisBank, Visa, Vyze, and Wells Fargo.

0
SHARES
0
VIEWS
Share on LinkedIn
Tags: APIOpen BankingPSD2Truth In Data

    Get the Latest News and Insights Delivered Daily

    Subscribe to the PaymentsJournal Newsletter for exclusive insight and data from Javelin Strategy & Research analysts and industry professionals.

    Must Reads

    payment credential management

    Why Payment Declines Are a Data Issue, not a Checkout Problem

    July 27, 2026
    identity theft protection services

    The Missing Piece in Banks’ Identity Protection Strategy

    July 24, 2026
    African cross-border payments

    Africa’s Payment Problem Isn’t What You Think It Is

    July 23, 2026
    remittance platform

    The Case for Not Building Your Own Remittance Stack

    July 22, 2026
    instant payments fraud, business payments

    When Faster Isn’t Better: The New Rules of Business Payments

    July 21, 2026
    Gen Z banking

    For Gen Z, Banking Loyalty Begins with Payments

    July 20, 2026
    syria visa mastercard

    Visa’s Stablecoin Platform Marks the Next Phase of Digital Payments

    July 17, 2026
    cross-border payments

    Beyond Pix: The Cross-Border Layer Latin America Is Building Next

    July 16, 2026

    Linkedin-in X-twitter
    • Commercial
    • Credit
    • Debit
    • Digital Assets & Crypto
    • Digital Banking
    • Commercial
    • Credit
    • Debit
    • Digital Assets & Crypto
    • Digital Banking
    • Emerging Payments
    • Fraud & Security
    • Merchant
    • Prepaid
    • Emerging Payments
    • Fraud & Security
    • Merchant
    • Prepaid
    • About Us
    • Advertise With Us
    • Sign Up for Our Newsletter
    • About Us
    • Advertise With Us
    • Sign Up for Our Newsletter

    ©2026 PaymentsJournal.com |  Terms of Use | Privacy Policy

    • Commercial Payments
    • Credit
    • Debit
    • Digital Assets & Crypto
    • Emerging Payments
    • Fraud & Security
    • Merchant
    • Prepaid
    No Result
    View All Result