Research, verification and independence
NeobankDB is an independent database and field guide. We classify what a product legally is, scope every material fact to a market, show the source trail and keep commercial relationships out of factual records, rankings and scores.
A licensed bank, banking-fintech programme, EMI, money transmitter, wallet, business finance platform and crypto exchange can all look like “money apps”. They do not carry the same legal structure or user protections.
A US programme-bank fact does not become a UK fact. Every material claim needs a subject, market, value, source, observed date, verification state and confidence.
Firecrawl and AI tools may collect candidate evidence, but scraped or model-extracted data never publishes directly.
Scope
The site covers the wider modern-money market, but classification is deliberately narrow.
NeobankDB covers licensed digital banks, bank-partner fintechs, electronic-money institutions, payment institutions, multicurrency accounts, remittance services, payment wallets, business finance platforms, corporate cards, credit products, brokers, crypto exchanges, crypto wallets, crypto cards, stablecoin accounts and fiat-to-crypto gateways.
The shared data model isBrand → Legal Entity → Product → Plan → Country → Fact → Evidence → Verification Event. That chain stops a brand-level description from overruling a country-specific product record.
NeobankDB is not a bank, lender, broker, exchange, wallet or adviser. It does not hold funds, connect to bank accounts, ask for credentials, collect card numbers or promise a financial outcome.
Automation and approval
Automation is useful for discovery and extraction, but the publication boundary stays human-reviewed.
Firecrawl or manual research may gather official pages, help articles, terms and regulator references.
AI can suggest facts such as legal entity, market, fee state or route status. These remain candidate records.
An editor verifies the source URL, observed date, authority tier, market scope, verification state and confidence.
Approved data is exposed through repository interfaces. UI pages do not publish raw crawler output or ORM records directly.
Project instructions for coding agents are maintained in repository files such asCLAUDE.md, AGENTS.md, memory.md and modular rules. Public methodology pages describe that governance at a high level only; they do not expose internal secrets, credentials or operational prompts.
Verification states
The site preserves gaps instead of turning missing data into a confident claim.
Current official source directly supports the claim.
Regulatory or licence source supports the claim.
Multiple acceptable sources agree, but the page still names the evidence.
Previously supported but outside the freshness window or awaiting re-check.
Sources disagree; the page must explain the conflict before recommending.
No approved fact exists yet. The UI may show the candidate lane but not a claim.
Evidence says a route, action or product use is not supported.
The value may exist publicly, but NeobankDB has not approved it for publication.
Reviews and comparisons
Reviews, comparisons and route verdicts use different views of the same evidence graph.
NeobankDB does not claim hands-on app testing unless a page records the date, market, account type, test conditions and limits of that test.
A comparison can recommend a starting point for a stated country and use case, but it does not force a global winner where evidence differs by market. Verdicts cite the factors used: legal type, protection model, fee verification, route support, product fit and evidence completeness.
Route records are exact and directional. Wise to Coinbase is not the same as Coinbase to Wise, and a generic ACH or card rail does not prove compatibility between named products. A route may be direct, conditional, intermediary, unsupported, historical or research required.
Illustrative only
This calculator is not attached to Revolut, Wise, Airwallex or any provider. It shows the scoring shape NeobankDB uses when a page has enough evidence to publish a scored module.
Commercial policy
Commercial relationships are kept separate from the evidence graph.
A provider cannot buy a factual classification, protection statement, route verdict, eligibility claim, score component or comparison winner. Paid links may affect how the site earns money; they cannot rewrite the evidence record.
Read the full editorial policy andinspect verified attribution.
If fee, limit, licence, route or protection evidence is missing, the page shows that gap. It does not award a hidden bonus for popularity, advertising spend or affiliate payout.
Corrections and provider responses
Validated intake stores an unapproved candidate when the durable API is configured; static builds fail closed and retain an explicit email fallback.
Submit the exact route, claim, source URLs, market, observed date and proposed correction. Provider responses follow the same evidence, conflict and approval rules as reader submissions. Receipt never means acceptance or publication.
There is no silent demo success. If durable API storage is unavailable, the intake says that no correction was recorded and directs the sender to email instead.
Privacy and security
The current site stores anonymous browser preferences only.
The site does not ask for bank logins, card numbers, crypto seed phrases, identity documents, balances, account numbers or transaction histories. Route checking is informational and uses public product names, country context and source-backed records.
NeobankDB currently uses organisation-level authorship. Future author and fact-checker pages should identify the reviewer, role, expertise area, review date and conflicts policy without weakening the same evidence requirements.
Glossary
These definitions appear consistently across reviews, country hubs, transaction routes and comparisons.
Current official source directly supports the claim.
Regulatory or licence source supports the claim.
Multiple acceptable sources agree, but the page still names the evidence.
Previously supported but outside the freshness window or awaiting re-check.
Sources disagree; the page must explain the conflict before recommending.
No approved fact exists yet. The UI may show the candidate lane but not a claim.
Evidence says a route, action or product use is not supported.
The value may exist publicly, but NeobankDB has not approved it for publication.
Source ledger
A source can support only the market, subject and claim it actually covers.