This is a great request! We've been considering building out a managed auth flow and bank syncing, would love to chat for 15 minutes and learn from your use case. Does any of these times work for you this week https://calendly.com/letsfuse/fuse-demo-15, appreciate it!
In regards to coverage in the UK, we currently support Truelayer and we are building out a Tink and SaltEdge integration. They'll be available early next month.
Hey, we don't store personal info for our core product which is Fuse Connect we only act as a pass through. The Consumer/Business Credit Risk product does require us to store historic transaction data in order to calculate insights.
Over the past few years a lot of consumer apps have started using bank data to determine credit risk for customers. From our experience this is generally accepted by consumers, as credit data does not provide the full picture. For example, I am originally from the UK and after moving to the US, I had no credit history so it was generally hard for me to use any service that could not determine risk based on cash flow.
Forgive me if this is dumb, but is Fuse connect a direct route to connect to banks orthogonal to third party aggregators? Is there a way to say no third parties?
My priorities are privacy first then wider coverage for bank accounts. I'd rather some consumers are blocked form accessing the service than having their transaction data getting leaked to intermediaries.
Hey, right now Fuse is dependent on third party aggregators and is most useful for companies that want to increase coverage and reliability. One idea if you're concerned with aggregators storing your customer data, is to only whitelist institutions where connections are established through OAuth. This way the aggregator won't be storing any account credentials. Most top aggregators have a few of the top institutions using OAuth now, so if coverage is not an issue for you this would be a good path.
So if our customers want to use another service or build it out themselves in house at a later date, they can always get all the original tokens.
We've also seen some of our customers use this endpoint to get access to original tokens and use it to make a request that we don't support yet via the original aggregator.
Thanks! If you already have an aggregator contracts, you can pass in the API keys into our backend and we'll use that for new connections. We have many users who come in with existing aggregators and want to combine it with another one to improve coverage. Here's an example of the SDK initialization - https://docs.letsfuse.com/docs/fuse-sdk
We also partner with some of the aggregators, so if you wanted to combine your existing one with a new one, we can help you setup the contract with no effort on your end.
Our unified endpoints are also backward compatible, so if you pass in an aggregator access token instead of a Fuse access token it'll work as expected.
Here's an example webhook:
{
type: 'transactions.updates',
financial_connection_id: "financial_connection_id",
environment: "sandbox",
source: "teller",
//Boolean indicating whether historical transaction information (up to 24 months) is ready to be queried.
historical_transactions_available: true,
//An array of string transaction ids indicated the transactions that have been removed and will not be available if the transactions are queried again. Currently only supported by plaid
removed_transaction_ids: [
"tx_1234",
"tx_5677"
]
remote_data: {}
}
