That’s a very good question. At this stage we don’t really have a defined set of principles about what should or should not remain in the feed… same for notifications. That will probably change at some point, just not yet
So far we’ve been making the call with every new thing we produce, based on our experience and a fair amount of user testing.
Something else you’d like to know we do is to always release this kind of feature first to a small proportion of our user-base and wait for their reaction. So if we get it wrong (we sometimes do), only a few of our users are affected and we can fix it before rolling out to the remaining ~99%. I hope it makes sense
Thanks @hugo Hopefully this will be something to think about as the service and range of items develops so that the feed fulfils a consistent function as well as responding to potentially inconsistent feedback. It will be good to hear how the approach to the feed is developing as part of the transparency hub. What different users want from it and how these wishes are squared will be interesting!
Not sure what’s going to happen when you start introducing items from third party APIs to the feed
There’s a big piece of work to be done precisely about that.
We haven’t decided yet, one alternative is to try to curate and “approve” integrations and only let them send notifications or even feed items if they follow a set of rules.
Another alternative would be to make it a bit more open but give powerful tools to users to tune what kind of actions want to authorise and integration to do (from “this app can see my balance” to “this app can send me notifications”).
The right solution would probably be somewhere in between
Hi @Naji By mispost I was referring to say someone quoting a wrong nine digit code on a credit meaning the credit ended up with the wrong user. Or a fraudster misdirection credits to his account by changing remitted details through fraud. Cheques sent to Monzo for collection could be keyed by mistake to the wrong account.
Collected cheques could be unpaid. etc.
Even with the best systems things get onto the wrong account or have to be reversed.
While I’m guessing that you have a modulus check digit in account numbers to reduce the incidence of error some misposts could result.
The approach on whether to contra or remove the transaction entirely could depend on the nature of the mispost. E. G. If crime is involved not alerting the criminal to detection.
I think there should be a real emphasis that the bank acts first and foremost for the CUSTOMER. All to often, with traditional banks, it seems they are being run for the regulator and compliance teams. And while that is of course important, that should NOT drive the business. Which it now seems to be doing in big banks. As a customer of a big bank I feel they would sacrifice my interests (and confidentiality) in a heartbeat, when the bank should have its loyalty to the customer. I am hoping Monzo will be different in this regard.
I couldn’t agree more - our goal is to act for you and all our customers first, ensuring we give you the best banking experience possible…
Our regulator is mainly concerned with the stability of the Bank (i.e. do we have enough money) and whether we treat our customers fairly, so I actually don’t know if they are truly to blame. I think the real problem lies in the way regulations and laws are interpreted … this is what causes frustrating situations for customers as a result of poor or overzealous interpretation of rules or guidelines.
Here we’re trying very hard to avoid that situation at Monzo, so while we always want to be fully compliant with the rules and regulations, we equally will ensure that in doing so, we don’t impact the experience or interests of our customers, (that being said there are certain situations which require us to follow more strict rules that relate to Fraud, Financial Crime and Money Laundering rules – which I’m sure you’d want us to adhere to!)
Thanks for the reply, which makes sense. As you say, it may well be that the internal compliance people in banks, in a “backside covering approach”, go over the top and jeopardise customer relationships. By all means follow the rules, but never forget the customer is king and that is key
Building on this, and as raised in the thread about Monzo-to-Monzo payments, the transparency page should provide details on how Monzo uses data on your phone which it asks for access to (contacts, photos, etc), including what gets sent off the phone, in what form, and where to. The second post in that thread details this for contacts data with regards to P2P payments, but I think there needs to be a statement that covers the app as a whole, and all categories of data Monzo requests permissions for.
I would like to see statistics about flexible and part-time working at Monzo. In particular, it would be interesting to see to what extent you find it hard or impossible to facilitate the desire for flexible working and what the reasons for this are.
I agree with vapoto. Are savings invested responsibly, in line with targets set at the UN climate summit in Paris in 2015? How can we be sure that our savings support sustainable energy and responsible business practices (fair wages)? I know the savings are handled by separate firms but it would be helpful to clarify this to attract more members.
There is no mention of environmental impacts of the Monzo business in the annual reports (which is a little surprising for a new~ish business). I would be interested to see the carbon impact of Monzos digital services and whether or not carbon-intensity of platforms such as AWS are at all a consideration in the decision making. Some overview and numbers in the annual reports could help form a benchmark from which to improve upon.
Hi, I got here through the link on this website: monzo.com/transparency
I wonder: I would like have your app published on F-Droid.
They have an inclusion policy.
I wonder where and how you would like to discuss this.
You would be the first bank there, I think and having an open-source client could make a difference in transparency.