bank2
One of the most common discussions I have with any business is about API use cases related to industry specific scenarios – their scenarios. We are making the information shared in these discussions more accessible to everyone by publishing a series of industry specific white papers covering these and related topics.  Each white paper has a consistent format that includes:

  • Identifying the common business drivers for API initiatives
  • Describing an API identification methodology
  • Supplying industry-specific examples using the methodology
  • Discussing the current state of regulatory requirements and industry standards for APIs
  • Providing recommendations for starting an API initiative


mobilebanking
I am excited to have worked with industry subject matter experts to author each paper in this series.  In each case my co-authors bring years of real world industry experience working with companies in the industry.  The first paper in the series is now available and focuses on the Banking industry.  My co-author for this paper is Esther Kim who is the Global Mobile API Economy Solutions Executive for Financial Services.  In the Banking paper we cover use cases related to Retail Banking, Commercial Banking, and Wealth Management across a wide variety of scenarios – internal, partnering, social, analytics, and more.

You can click here to download the paper.

To understand more about IBM’s thoughts on the API Economy visit the IBM API Economy website.  IBM API Connect is IBM’s complete foundation to Create, Run, Manage, and Secure APIs.  You can find more information about IBM API Connect at the API Connect website.  And you can also download a trial version of API Connect.

If you have questions, please let me know.  Connect with me through comments here or via twitter @Arglick to continue the discussion.

2 comments on"Identifying API Use Cases in Banking – White Paper available"

  1. Vikas Mulik July 13, 2017

    Need to understand API Open Banking

Join The Discussion

Your email address will not be published. Required fields are marked *