shipapis
StarSubmit an APISubmit API

GOV.UK Pay API vs IBANforge

Same instrument, two spec sheets — measured, not claimed.

APIGOV.UK Pay APINEW—IBANforgeNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key required200 requests/month with a free API key; /v1/demo and /health are keyless
Rate limitUnpublishedUnpublished (200/month free quota)
In directory since2026-07-052026-07-05
operationalpartialdownno data

GOV.UK Pay API vs IBANforge: common questions

Which is more reliable, GOV.UK Pay API or IBANforge?

On our scheduled checks, IBANforge leads on measured uptime — GOV.UK Pay API at —% versus IBANforge 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 GOV.UK Pay API and IBANforge need an API key?

IBANforge needs no key, while GOV.UK Pay API requires a free API key. If you want to start calling without signup, reach for IBANforge first.

Can I call GOV.UK Pay API and IBANforge from the browser?

Only IBANforge is browser-friendly — it returns CORS headers over HTTPS. GOV.UK Pay API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are GOV.UK Pay API and IBANforge free for commercial use?

GOV.UK Pay API has unclear commercial terms, and IBANforge 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.