During travel, my clients are making purchases abroad in a foreign country, they’re normally provided with two specific currencies on the point-of-sale terminal when they make the purchase. So a lot of clients are very confused about, um, “Which one should I select? Which one should I actually put onto my credit card when I make that purchase?” Say hey listen let’s, let’s develop a feature that allows them to make a more informed decision when they’re making their purchase. What we brought to the table was an ignition point, and that ignition point was the Visa Developer Program, and they ended up using the FX API that we have offered. It fit really nicely in with the solution that we were thinking about in terms of addressing the specific client irritant of clients not knowing which currency to select. Thanks to the APIs that Visa’d already developed, you know, we didn’t need to worry about where we’re going to get this data and this information from, where we’re going to store it, how we’re going to house it, um, it was just a matter of information’s already readily accessible, let’s integrate it into our, into our application, into our mobile banking application, and let’s display that rate in a convenient manner to the client that’s frictionless. So I think a lot of banks focus on APIs because it allows them to put the consumer at the center of the conversation, um, and really really expose, if you will, and utilize different APIs for different consumer experiences, and that’s the beauty of APIs, there is really no defining recipe, you make it up as you go. You know, I think one of the more interesting aspects of this deployment was the speed which it commercialized. This was a pretty easy one for us to be able to say “Yes, there’s a solution that exists, Visa’s already providing the APIs, let’s get this to market,” but fundamentally our goal is to be able to bring to market these solutions and these features and address these client irritants in the quickest time frame possible.