Urgent.News

650+ sources. One page. See who else covered it.

Editions

Tech

Free Signup vs Production Access: What Self-Serve PSD2 Providers Actually Gate

"Self-serve" is doing a lot of work Every PSD2 account-information provider markets some version of "get started in minutes." What varies — enormously — is what you can actually do before a human from sales gets involved. There are really three gates: Signup — can you create an account at all, alone, with an email address? Sandbox — can you call working APIs before signing anything? Production —…

Self-serve PSD2 account information providers offer varying levels of accessibility before sales involvement. There are three main gates: signup, sandbox access, and production access. A provider can be accessible at the first two gates but still restricted at the third. This discrepancy can lead to confusion when comparing providers.

As of August 2026, Enable Banking offers a self-serve experience with a magic-link signup, auto-created account, sandbox access without a contract, and restricted production access without a contract. Credit is given for their sandbox's extensive bank coverage and honest documentation. However, production access requires a signed contract, KYB verification, and sales team pricing.

Other providers, such as GoCardless, TrueLayer, Tink, Yapily, and open-banking.io, also have restrictions on production access, requiring contracts, KYB verification, and additional costs for certificates. The decision to use a specific provider depends on the project's needs. For personal tools or evaluation purposes, providers like Enable Banking and open-banking.io offer genuinely free tiers with no contracts and public production access.

For public production access, other providers require contracts, KYB verification, and additional costs.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Qdrant Recall Inconsistency: It Took 300 Test Runs to Discover the Index Wasn't Refreshed

At 2 AM, a user reported that the AI Agent suddenly forgot details of a project we discussed yesterday. I groggily opened Grafana and saw the memory recall rate had dropped from 98% to 60%.

  • AI Agent forgot project details, memory recall rate dropped from 98% to 60%
  • Qdrant writes and queries have time gap, causing intermittent failures
  • Qdrant's write and index building are asynchronous, leading to empty or partial results

The most boring service in the stack

The most reliable part of a stack is rarely the part anyone shows off. It has no clever layer to point at. That is the whole reason it never breaks.

  • Payment service remained unchanged for four years
  • Black Friday caused system failures
  • Simplicity avoided unnecessary complexity

More from Sunday 16 August →