Banking API vs GOV.UK Pay API
Same instrument, two spec sheets — measured, not claimed.
Banking API vs GOV.UK Pay API: common questions
Which is more reliable, Banking API or GOV.UK Pay API?
On our scheduled checks, GOV.UK Pay API leads on measured uptime — Banking API at —% versus GOV.UK Pay API at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.
Do Banking API and GOV.UK Pay API need an API key?
Both ask you to authenticate — Banking API uses an API key and GOV.UK Pay API uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.
Can I call Banking API and GOV.UK Pay API from the browser?
Neither sends browser-friendly CORS headers reliably, so call Banking API and GOV.UK Pay API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.
Are Banking API and GOV.UK Pay API free for commercial use?
Banking API has unclear commercial terms, and GOV.UK Pay API has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.