Trust

How this data is gathered and checked

Last checked

Every eligibility verdict on this site carries a source and a date, and the source is printed next to the verdict so you can check it yourself. This is how that works.

One dataset

The eligibility data lives in a single file, versioned in source control. Its history is the provenance trail: every change to a verdict is a recorded edit, with when it changed and why. Every page reads from that one file, so an account page and an institution page cannot disagree about the same provider.

How a verdict is made

Each claim names one provider and one account type, and lands on one of three verdicts: opens, opens with strings, or skip. The verdict is backed by a source, a public policy, an application flow, or a direct statement from the provider, and stamped with the date it was last checked. A confidence level records how firm the evidence is.

Published first, dated on every row

A verdict drawn from a credible source, such as the provider's own terms or a published policy, is published and then confirmed against the provider's own page. A verdict that rests only on a lead is still shown, so the table is complete. Every row carries the date it was last updated, whether a person read the provider's page that day or the weekly check read it again, and every row is shown the same way: the page does not mark which verdicts are still awaiting confirmation, and the date tells you how recent each one is.

Confirmation decides where a verdict can go. One still awaiting it is kept out of the page's structured data and out of the machine-readable digest, and a page is listed in search and the sitemap only once it carries at least one confirmed verdict. A verdict handed to a search engine or an AI tool as settled when it is only a guess costs more trust than it earns.

Five verdicts a week, read by a person

Each week a person reads the five verdicts most in need of it against the provider's own page. The order is fixed: leads still awaiting confirmation first, then verdicts whose source has aged, those held with low confidence, those with no link to their evidence and those resting on a single secondary source, then whichever has gone longest unchecked. A verdict that still holds is confirmed and its date moves. One that has changed, or whose evidence link no longer supports it, is rewritten from the source before it is dated again. Where rates are shown, the table is checked separately, and it counts as confirmed only if it lists every account on the provider's page.

Dates are real

The last-checked date on a verdict is the same date the structured data reports as the modified date, and a rebuild of the site never moves it. A date moves only when the provider's own page has been fetched and read that day. It never moves on a search result, a comparison site, a forum post or a remembered figure, and a page that could not be reached keeps the date it already had. If a date looks old, treat the verdict as due a recheck and confirm it.

Money stays out of it

No provider pays to be listed, placed or linked. The commitments that keep it that way are in the editorial code, and how Momo intends to earn a living is on How Momo makes money.

What this is not

This is an information service, not advice and not a regulated recommendation. Acceptance policies change without notice and your own facts may differ from the general case. The data is a map of where to start, not a ruling on your situation.

Confirm your own position with a cross-border specialist. Acceptance policies and tax rules change, and your facts may differ from the general case. Rates and terms here are the provider's published figures rather than an offer, and the provider decides each application on its own criteria. Use this as a map, not a ruling. Last checked .