The idea of banks using APIs to 'open' their systems to third party developers is really popular now. That's fine when it comes to informational apps like Google maps. But with transaction data like card and other payments the security issue mean open APIs are not practical. PSPs have used hosted payments pages to circumvent this problem - OK but very limited control for the page developer often means poor UX. Tokenisation also helps but is quite limited and not suitable for interactions between user and app. This presentation explains a new approach by Ixaris which could revolutionize third-party development of transactional payments applications without compromising security.

1. Open Payments Without
Compromising Security

2. • Reduced
Interchange
• More Regulation
• Need for New
Revenues
• Increased
Compliance Burden
The future brings challenges

3. “Platforms that provide private and public Web APIs enable
banks to respond quickly to new opportunities, and third-party
developers to build the banking solutions they need”
Key Recommendations
• Use apps to deliver new services
• Provide private and public Web APIs to quickly pursue new
revenue opportunities and facilitate market expansion
Respond by opening up payments

4. Open APIs are starting to happen

5. open
but with permission
permissionlessclosed
But what does “open” really mean?

6. Legacy systems
Payments Application Platform
Corporate Purchasing
Steps to opening up
Web /
Mobile UI
Enterprise
systems
Client’s
own
services
Expense Management
APIAPI API
Incentive Payments

7. Legacy systems
Payments Application Platform
DIY products
Steps to opening up
Web /
Mobile UI
Enterprise
systems
Client’s
own
services
Off-the-shelf
APIAPI API
Apps built by trusted
developers

8. Legacy systems
Payments Application Platform
API
Product X
Crowd
?
API
But do you really want open APIs?

9. Secure vs Flexible?

10. Legacy systems
Payments Application Platform
PayML
Product X
Open secure access without APIs!
Mash-ups Mobile
Apps
Web-based
tools
Payment ‘tags’
added to standard
HTML, to specify
payment directives
Pages automatically
scrubbed to allow
only safe content
HTML/PayML pages
submitted by external
developers but run
within secure bank
environment

11. • more compelling
products
• enhanced by
Clients and
Developers
Competitive advantage
through:• Add a (cloud-based) payments application
platform over legacy systems to facilitate
service innovation
• API-enable payment products, but only give
APIs to trusted customers and partners
• Open up access through safe methods like
PayML to tap the broad developer community
for your own app store of myriad payment
apps and services…
The future is here…get busy!

12. Thank you
Alex Mifsud
Founder & CEO
alex.mifsud@ixaris.com
Ixaris Systems Ltd
22 Long Acre
London
WC2E 9LY
www.ixaris.com