The original hackathon submission was to use an Aggregator (screen scraper) to validate a business owner’s access to a bank account so that a renewal order for cheques could be completed digitally. Today, the renewal order is done either via fax or an inbound call; the solution created a frictionless digital approach to reorder.

For the Super Hack, we have taken the frictionless and aggregation concepts and have applied it to Fusion Fabric.Cloud in an “Aggregator of an Aggregator” model. At issue is inconsistency between Aggregators. They work with different banks in different countries, have different data exchange formats, collect different data points, are priced differently, and the businesses are of different sizes and maturity. Fusion Aggregate provides developers, banks and consumers the ability to build once and reliably deploy applications globally.

The application of machine learning in the environment would be leveraged to optimally route requests based on data requirements, price, availability and geography.

The business model exists today whereby aggregators charge a fee for each screen scraped data pull. Research suggests that 1 out of every 10 transaction in online banking platforms are made by an aggregator. Our model includes a surcharge or a “toll” on each transaction made through the service and charged to the application owner. Plaid, a privately held aggregator, is currently valued at $2.7B.

As Fusion Fabric.Cloud grows and adds banks to the environment, this solution ultimately displaces aggregators as the routing logic shifts to internally routed requests.

What it does

  • an API, Login control
  • Using login control, which is called with a country code (62 countries supported), customer selects their bank, and logs in with their credentials
  • API routes the request based on geography and bank to the "best fit" aggregator. Calls routed to either Saltedge (an International aggregator), Flinks (a Canadian aggregator), or FFDC (Astra Bank on FFDC US Retail API)
  • The API returns customer profile information to the application
  • We demonstrate through streaming logs that how the calls are routed
  • We have built 3 mock-up samples that consume the API. A Canadian e-commerce registration, an investment bot in Singapore, and a US mortgage origination example

How we built it

  • C# for API
  • Azure App services for hosting
  • Node.js for mock-up consumer apps
  • Integration with FFDC Retail banking, Saltedge (international aggregator), Flinks (Canadian aggregator)

Challenges we ran into

  • OpenID implementation
  • Working with 3rd party API - learned some functionality was disabled by default
  • Working in a different time zone / time change adjustment
  • Laptop died day before travel to London - had to re-setup dev tooling!
  • Abandoned implementations.
    --We tried to inject our API into a production app using a Chrome control, had to abandon after many wasted hours. ---Wasted time trying to re-use markup from production app we were trying to integrate with

Accomplishments that we're proud of

  • Understand from FFDC platform team we are the first to connect with OpenID with C# on FFDC. We uncovered an interesting bug, that the FFDC platform team promptly patched for us!
  • Connecting to FFDC
  • Implementing OpenID
  • Taking the concept from whiteboard to PoC

What we learned

  • OpenID
  • OPEN BANKING: We have learned a lot about aggregation and open banking internationally - something we weren't familiar with at the start of this project - PSD2, consent requirements, UK open banking
  • Understand FFDC's role in Finastra's strategy

What's next for Fusion Aggregate

We have a use case in Canada for the Aggregator model that the business intends on implementation in to production.

As the Fusion Fabric.Cloud environment matures, developers will require access to data from external sources. Fusion Aggregate demonstrates this ability to efficiently access data. The model can be applied to screen scraping, credit bureaus, dark web monitoring and any other data environment that have geographic differences. Think every credit bureau call for a mortgage application routing through the Fusion Aggregate application. Think every credit card application leveraging Fusion Aggregate. Think every deposit account application leveraging Fusion Aggregate. Think every wealth account application leveraging Fusion Aggregate.

Built With

Share this project: