%20%20--%3E%0A%3Csvg%20version%3D%221.1%22%20id%3D%22Layer_1%22%20xmlns%3D%22http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%22%20xmlns%3Axlink%3D%22http%3A%2F%2Fwww.w3.org%2F1999%2Fxlink%22%20x%3D%220px%22%20y%3D%220px%22%0A%09%20viewBox%3D%220%200%20684.6%2068.1%22%20style%3D%22enable-background%3Anew%200%200%20684.6%2068.1%3B%22%20xml%3Aspace%3D%22preserve%22%3E%0A%3Cg%3E%0A%09%3Cpath%20d%3D%22M444.1%2C29.3h-17.4v14.5h17.4V29.3z%20M36.4%2C68.1l29.3-50.8V0H50.4L32.9%2C36.8L15.5%2C0H0v68.1h16.7V45.8l12.4%2C22.3H36.4z%0A%09%09%20M49.1%2C68.1h16.6V23.4L49.1%2C52.1V68.1z%20M76.6%2C68.1h45V53.8H93.3V41.6h21V27.1h-21V14.8h28.3V0.1h-45V68.1z%20M175.6%2C68.1h17.3v-68%0A%09%09h-16.5v40.3L150%2C0.1h-17.6v68h16.7V27.7L175.6%2C68.1z%20M235.8%2C14.8h15.4V0.1h-47.4v14.7H219v53.2h16.8V14.8z%20M290.3%2C45.9h-17.1%0A%09%09l7.5-15.6h2L290.3%2C45.9z%20M298.7%2C68.1h18l-32.2-68h-5.7l-32%2C68h18l3.3-7.1h27.1L298.7%2C68.1z%20M325.2%2C68.1h46.2V53.8h-29.6V0.1h-16.7%0A%09%09V68.1z%20M423.7%2C14.8h27.2V0.1H407v68h16.7V14.8z%20M462%2C68.1h46.2V53.8h-29.6V0.1H462V68.1z%20M564.8%2C34.1c0%2C10.7-7.2%2C19.2-18.5%2C19.2%0A%09%09c-11.4%2C0-18.5-8.5-18.5-19.2s7.1-19.2%2C18.5-19.2C557.6%2C14.9%2C564.8%2C23.4%2C564.8%2C34.1%20M580.6%2C34.1c0-19-14.2-34-34.3-34%0A%09%09c-20.2%2C0-34.3%2C15-34.3%2C34c0%2C19%2C14.1%2C34%2C34.3%2C34C566.4%2C68.1%2C580.6%2C53.1%2C580.6%2C34.1%20M604.8%2C20.5c0-4.1%2C3.3-6.2%2C6.7-6.2%0A%09%09c4.4%2C0%2C6.6%2C3%2C6.6%2C6.6h14.7C631.8%2C9.1%2C625.1%2C0.1%2C611%2C0.1c-12%2C0-21.7%2C9.3-21.7%2C20.6c0%2C10.9%2C5.9%2C15.9%2C16.7%2C19.8%0A%09%09c5.2%2C1.8%2C11.5%2C3.2%2C11.5%2C8c0%2C3.3-2.4%2C5.5-6.4%2C5.5c-3.6%2C0-6.6-3-6.6-6.7h-15.2c0%2C11.5%2C7.9%2C20.8%2C21.8%2C20.8c12%2C0%2C21.6-9.3%2C21.6-20.6%0A%09%09c0-10-5.3-16.4-16.7-19.8C610.6%2C26.1%2C604.8%2C25.3%2C604.8%2C20.5%20M670%2C20.9h14.7C683.8%2C9.1%2C677.1%2C0.1%2C663%2C0.1c-12%2C0-21.7%2C9.3-21.7%2C20.6%0A%09%09c0%2C10.9%2C5.9%2C15.9%2C16.7%2C19.8c5.2%2C1.8%2C11.5%2C3.2%2C11.5%2C8c0%2C3.3-2.4%2C5.5-6.4%2C5.5c-3.6%2C0-6.6-3-6.6-6.7h-15.2c0%2C11.5%2C7.9%2C20.8%2C21.8%2C20.8%0A%09%09c12%2C0%2C21.6-9.3%2C21.6-20.6c0-10-5.3-16.4-16.7-19.8c-5.4-1.6-11.3-2.4-11.3-7.2c0-4.1%2C3.3-6.2%2C6.7-6.2C667.7%2C14.4%2C670%2C17.3%2C670%2C20.9%0A%09%09%22%2F%3E%0A%3C%2Fg%3E%0A%3C%2Fsvg%3E%0A)
Can banking make a developer’s life easier? Today, open banking is the up-and-coming tech movement positioned to spark innovation within the field of financial services, putting a whole new world of financial services at users’ fingertips.
The possibilities of exciting new user experiences, frictionless payments, and smart handling of financial data offer promising opportunities to create new products. Whether you’re a product manager or a developer, here are a few handy things that can help inspire your next project.
1. DATA SHARING CAN BENEFIT YOUR USERS.
“Open banking” sounds exciting, but what exactly is it? Put simply, it’s the push for banks to allow secure data sharing with third-party developers via interfaces known as APIs, or application programming interfaces. APIs have long been used as ways for different software and servers to communicate and exchange functions. Open banking is the push for banks to open their APIs, thus making financial information available to developers.
What does this openness mean for your business? Imagine you’re building an incredible e-commerce site. Wouldn’t it be fantastic if you could let shoppers pay for their purchases using credit card rewards points? With an API from Citi Open Banking, you can easily add that functionality to your store. Customers will benefit from the ability to seamlessly spend their points, and they might even be more likely to make a purchase since you’ve given them that power.
2. APIS CAN GET THE JOB DONE.
On top of user-facing benefits like enabling customers to pay with points, APIs are a huge boon for fintech developers, because they offer businesses a “way to integrate a technological brick or a set of data in their application without the need to build it themselves,” explains lead API economist Mehdi Medjaoui of the API Academy. “Banks can open APIs that enable fintech companies to access customers’ payment history, initiate payment, or open a credit line, for example.”
In other words, the next time you need to add financial functionality to a project, you may be able to skip the long hours of painstaking coding by utilizing a tested, supported API that can get the job done.
3. THE DEVELOPER COMES FIRST.
Developers and product managers have to constantly think about the needs of their customers, but when it comes to open banking APIs, the situation is reversed—the developer becomes the customer. As banks make their APIs available, developers will jump at the opportunity to access new data and functionality, especially if these APIs fulfill specific needs. Since APIs are supposed to be reliable, time-saving tools, usability is as important as usefulness.
That’s good news for developers, because it means banks are motivated to make effective APIs that can be easily implemented. “If developers have a choice between two APIs that do similar things, they will pick the one that they can understand and use quickly,” says API Academy vice president Matthew McLarty.
In other words, the makers of APIs are actively looking to make your life as a developer easier in order to drive adoption of their APIs. This means that developers will ultimately receive a flexible API that has their needs in mind, preferably accompanied by documentation that explains how API calls can help a consumer complete a task.
4. NOT ALL SUPPORT IS CREATED EQUAL.
Support is crucial, especially for self-service APIs where users are left to their own devices when integrating and tinkering with APIs. Some good support functions to look out for include a forum where new versions and updates are clearly communicated, a blog where users can share knowledge, or a 24/7 helpdesk. Some support naturally comes from the communities of developers that coalesce around APIs: An “active community of users that are able to collaborate and solve their own issues through a web forum or other means” is a good sign, says McLarty.
5. “FIT” ISN’T JUST A BUZZWORD.
“When you integrate an API, you integrate the world behind it,” notes Medjaoui. APIs can be incredibly useful for developers, but it’s also important that developers think about how APIs serve their purposes and fit into the larger product they’re building. Like any tool, it’s important to pick the right API for the job.
“Developers should analyze their business goals and business models and determine what product features are their differentiators, and what features are just enablers,” cautions McLarty. “I would recommend using APIs for the enabling features, but keeping the differentiators in house.”
Here’s a useful line of thinking, suggests Medjaoui: “A great search experience for my e-commerce website would be a plus, but since it’s not critical in my value proposition, let's use an API for that.” By using an API for that sort of functionality, you can speed up your project’s timeline and open up resources for the unique aspects of your product.
One more thing developers should know about open banking: Citi Open Banking offers a whole suite of global APIs that can help bring your next project to life. Learn more at https://sandbox.developerhub.citi.com/.