Monzo Labs: Connected Credit Cards

It’s just pooped up, that’s a pretty cool feature! Honestly once this supports American Express and the app has dark mode I couldn’t think of any ways to improve it

3 Likes

Is there any way to see the planned CC integrations? Only ones I’m missing are Amex and Virgin Atlantic.

Anything missing needs to wait for open banking next month (:crossed_fingers:)

Both have been mentioned before

5 Likes

Thanks! So you’re saying all UK CCs will be added once that’s done?

Not sure if they’ve said all (I’m imagining how long the list you’d need to scroll through would be) but definitely the most popular ones

3 Likes

That’s kinda the issue :confused: I have no idea whether those two are deemed “popular” or not.

Yes, they are

i’s sure there was a post about this but can’t see it atm. Will post it when I find it

2 Likes

Amex is for sure, not sure about the Virgin one

1 Like

If I remember correctly Virgin was near the top of the poll on here about top credit cards.

2 Likes

Hey all,

I can give an update on where we’re at with this feature.

As many of you know the feature has been in a partially-rolled out state for a few months. Anyone can connect to their cards, but we only promote the feature to a small % of users actively.

This is for a couple of reasons:

  • We don’t think the current method of connection (Credential Sharing / Screen Scraping) has proven itself to be reliable enough.
  • We know we need to migrate all connections over to Open Banking connections around September, and want to minimize the number of people having to do that.
  • The team that built this feature had to help out with some other urgent projects (getting our own systems ready for Open Banking), so didn’t have as much capacity to support a new feature being promoted to 100% of users (especially one with some known issues).

We’ve been in a bit of a holding pattern while we waited for banks to provide Open Banking APIs that support credit cards - as we hope these will perform more reliably.

Some banks are starting to switch over (RBS and Natwest), so here’s a quick run down of our migration plan.

  • In a couple of weeks, we’ll change the connection flow to offer Open Banking connections if they’re available. Not all banks are ready yet, but most of the high-street banks are.
  • For people with existing connections, we’ll send you an in-app message when your bank switches off the old way to connect, explaining how to reconnect via Open Banking.
  • We may hit a point where some banks turn off credential sharing, but don’t have an Open Banking API ready yet. In this case, the cards will disconnect and it won’t be possible to reconnect them. However, so far we’ve only seen banks turn off credential sharing once they have an API live.

During this period, we’re going to keep the feature at a similar level of availability, so make sure the new connections are working better. Once we have that confidence we’ll likely roll it out further.

In terms of when different credit cards will be supported, it’s really not something we have heaps of visibility or control into. We were told in Spring that APIs were coming for some of the most requested cards, but many have failed to materialise yet. In the immediate term, we’ll be supporting the same banks, with no new additions.

Hope this helps clarify things.

41 Likes

Excellent update Jami, just one thing id like to get clarified if possible.

Once the banks share their new open apis will you be removing TrueLayer as a partner and use your own in house connections?

I’d much prefer this than to using another third party (truelayer)

1 Like

Our plan for now is to stick with TrueLayer.

They make the migration from one method of connection to the other much quicker and easier, and will also reduce the work needed to add new banks once they provide APIs.

Given there’s so much changing with Open Banking, and there will likely be teething issues, we think it makes more sense for us to let TrueLayer do what they do best, and for us to focus on Monzo-specific problems - instead of us dealing with integration issues multiple times for all the different banks.

19 Likes

They’ve just posted a new status summary - spoiler: they’re still not ready!

2 Likes

That makes sense, but who is responsible if there’s ever a data breach for our details that we’ve passed on to TrueLayer? Will Monzo let us know or are we wholly reliant on a third party here?

Also, do you vet TrueLayer’s security and accreditation?

I imagine Monzo would behave as they did when there was a data breach from another supplier – Typeform.

They apologised, informed everyone affected and the Information Commissioner’s Office, and would have taken the necessary precautions to protect the bank from fraud.

2 Likes

The use of this is entirely optional so we have the ability to run to our own level of risk aversion, fortunately.

1 Like

@Jami did you mean won’t?

Yes that’s what he meant

thanks - will edit :bowing_man:

1 Like

Hey Jami,

Thanks for the update on this. Obviously the next steps will be to get all these new APIs connected and sort out teething problems…but have you thought about what’s the next step after that?

Is transaction information still on the backlog? Or is that reliant on a more stable version of the new design?