Fable API Hub

03.10.23 10:27 AM - By Naushad Contractor

API and Open Banking

Open banking is revolutionizing how banking services are availed by businesses. Banks all over the world publish their APIs for their corporate customers and fintech partners. This allows your corporate customers to access all their financial information on their own ERP systems.


With a properly executed open banking strategy, your corporate customers:

  1. Never have to log in to bank systems for every small task.
  2. Can digitise and automate their processes and systems to achieve high efficiency at reduced costs.

    Result - A great customer experience which eventually leads to better retention.
    This seems like a win-win strategy for everyone. However, there are roadblocks on both sides when it comes to proper execution.


     Table of contents

    ​​Roadblocks at your customer’s end

    • High dependency on their ERP solution provider and other aggregators
    • High involvement of IT team
    • Custom integration can be costly and time-consuming

    ​​Roadblocks at the bank’s end

    • Banks might not have APIs built for key financial services

    • Need to build custom APIs for each customer and aggregator as their tech stack can vary;

     

     1) Multiple ERP solutions

      2) Different database types
    • Every integration requires very high involvement of the bank’s IT resources
    • This makes the whole process less financially viable and not scalable

    Therefore, even though there is intent from both sides, the adoption of these services is extremely low.

    ​​A better approach

    Fable’s API Hub makes open banking adoption easier, faster, and more interoperable.


    Thus future-proofing your open banking strategy while making it scalable.

    Banks don't have to connect directly with customers, aggregators, and pay-out partners (domestic and cross-border). They can now have a single reusable API set for everyone to use. Imagine a Zapier for open banking.
    Let’s explore this approach in detail.

    One-time integration with Fable’s API Hub allows you to

    • Improve onboarding and integration experience for corporate customers, aggregators, and pay-out partners

    • Have a fully standardised open banking API stack;

     

     1) Single reusable API set for everyone to use

      2) Very low involvement bank’s IT resources for every integration
      3) No need to maintain multiple interfaces, thus reducing complexity
      4) Lower cost of deployment and maintenance for every customer

    • Offer highly customisable open banking service to customers;

     

     1) No dependency on ERP provider and other aggregators

      2) Minimal IT work required
      3) Customers can access all financial services on their own ERP solution;
     

     - Make transaction requests

      - Check transaction status
      - Check account balance
     - Get reconciliation related information
      - Upload and review documents
      - Perform KYC checks
      - Authenticate users
      - Get taxation related information
      - And many more..

    • Reduce exposure of your core banking application to multiple entities


    Let’s see how this process works for your customers

    ​​Making a payment

    Here is how your corporate customers (like Unilever) can make payments to their vendors after availing their services.

    Steps for making payments

    • The finance manager (user) wishes to make payments to their vendors (Either single or in bulk)
    • The user logs into their ERP system (Like SAP, MS Dynamics, Oracle, etc) and makes a payment request
    • The Fable API Hub authenticates the user
    • Accepts the transaction details
    • Debits the relevant account
    • Sends the payment for delivery via domestic or cross-border pay-out partners
    • Sends the success or failure (with reasons) update to the ERP system
    • Passes accounting entries to the core banking system

    ​​Receiving payment

    Here is how Unilever can make payments to their channel partners before dispatching inventory.

    Steps for receiving payments

    • ​The core banking system receives an inward transaction (domestic or cross-border) favouring Unilever
    • Once accepted, the core banking system alerts Fable API Hub through standardised APIs
    • The API hub then updates Unilever’s ERP system with the details of received payments
    • The finance manager gets an alert
    • If required, the user can upload documents using the same interface
    • Unilever dispatches inventory to the respective channel partner

    ​​Fable’s API Hub platform is everything your open banking strategy needs, and more. It is:

    • Compliant
     

     1) 100% compliant with global regulations and internal bank standards

      2) Fable is an ISO 27001 certified company and is GDPR compliant
    • Inclusive
     

     1) Agnostic to bank’s technology maturity levels - works with file upload, REST, SOAP, SFTP, etc.

      2) Agnostic to your customer’s technology stack - works with any ERP solution or Database type
    • Frictionless
     

     1) Requires minimal involvement of Bank’s IT team

      2) Eliminates the need to change your existing Card Management, Core trade, FX, Doc management, or compliance systems
    • Flexible
     

     1) Allows you to set the rules, define corridors and make purpose-specific configurations

      2) Offers multiple commercial and deployment options available

    To acquire the platform, book a demo with the Fable Fintech cross-border platform experts;

    Book a FREE Demo!
    Tags :
    Categories :