apidays LIVE LONDON - The Road to Embedded Finance, Banking and Insurance with APIs API Design in Fintech: Challenges and Opportunities for next gen APIs Jeremy Glassenberg, Director of Product, APIs at Deserve

1. API Design in Fintech
Challenges and Opportunities for Next-Gen APIs

2. About Me
2
Founder of the Box developer platform
Early writer for ProgrammableWeb
Managed these platforms
Mentor, advisor, consultant for other developer platforms & accelerators

3. A Brief History of Fintech APIs

4. A brief history of Fintech “APIs”

5. A Bank’s Philosophy
The dream of accessible dataBanks

6. Then… Open Banking, PSD 2
Open Banking
Data,
APIs

7. Now, we can work with APIs...

8. Quite a groovy time!

9. And there are a lot of good people here who know APIs...

10. After all

11. And there are Industry Standards
https://www.xmldation.com/en/2017/iso-20022/
ISO 20022

12. API Consistency

13. API Consistency: Currency
MarqetaPlaid
Stripe

14. API Consistency: Endpoints and Objects
Stay RESTful, try to keep some consistency
Stripe Marqeta

15. We like Idempotency
All Core API POST calls are
idempotent capable when the
primary token is set in the request
object.
Marqeta SquareStripe
Square APIs require idempotency
keys to protect against accidental
duplicate calls when duplicate calls
can have negative consequences
(for example, charging a credit card
twice).

16. API Consistency: Authentication: Client-Server

17. API Consistency: Authentication
The Core API enforces HTTP Basic Authentication on incoming requests. This
mechanism utilizes the standard Authorization field in the header for holding the
credentials.
Basic Auth server-to-server
User
Partner-Client
(ex: Mobile app)
Partner-Server Marqeta-API
View
Transactions
View
Transactions
Request
GET /users (master token)
User token
GET /transactions (user token)
Transactions list

18. API Consistency: Authorization

19. Consistency: Sandboxes

20. The Dream: Consistency

21. Thank You!