Next chapterRead the article

Open Banking1 min read

Open banking is a consent problem

The technology is the easy part. The hard part is a customer who understands what they agreed to, can see who is using it, and can take it back.

Most conversations about open banking begin with APIs. They matter, and they are also the part we already know how to do. Connecting two systems safely is a solved kind of problem.

What is harder is the person in the middle. Every connection rests on a customer saying yes, and that yes has to mean something.

What a real yes looks like

Consent that holds up has three parts.

  1. The customer can read what they are agreeing to, in plain words and in their own language.
  2. They can see, later, who is using that permission and for what.
  3. They can withdraw it as easily as they gave it.

Why this falls to the bank

When something goes wrong, customers will look to their bank, whichever party caused it. So the bank carries the reputation even for connections it did not build, and the consent screen is one of the few places it can still speak to the customer directly.

The institutions that get this right will not be the ones with the most connections. They will be the ones whose customers still feel in charge of them.

Keep reading

More from the blog

A round steel vault door, closed, set into a stone wall

Security2 min read

What a security questionnaire is really asking

Most vendor assessments run to hundreds of questions, but only a handful decide the answer. Here is what regulated institutions are actually checking for, and how to answer it straight.

Read the article