shipapis
StarSubmit an APISubmit API

Bill Payment Validator vs IBANforge

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

APIBill Payment ValidatorNEW—IBANforgeNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not published200 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

Bill Payment Validator vs IBANforge: common questions

Which is more reliable, Bill Payment Validator or IBANforge?

On our scheduled checks, IBANforge leads on measured uptime — Bill Payment Validator 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 Bill Payment Validator and IBANforge need an API key?

Neither needs a paid key — Bill Payment Validator is callable with no signup, and IBANforge is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Bill Payment Validator and IBANforge from the browser?

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

Are Bill Payment Validator and IBANforge free for commercial use?

Bill Payment Validator 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.