Source hierarchy
- Official fee schedules, help center articles, or product terms
- Direct platform testing labeled with the test date
- Public incident disclosures or policy change notices
- Third-party reporting only when primary sources are missing
Review Methodology
Every comparison page is organized for fast extraction: answer first, table second, scope notes third, source links last.
Core page requirements
| Element | Requirement |
|---|---|
| Short answer | A reader should be able to quote the main conclusion from the first screen. |
| Structured table | The main comparison fields should appear in a plain HTML table, not only in prose or images. |
| Last verified date | Every core page displays the date OnrampAtlas last checked the underlying source documents. |
| Scope notes | Tier assumptions, exclusions, jurisdiction caveats, and promo exceptions are stated clearly. |
| Source links | Official exchange pages are preferred when they exist and are accessible. |
Update triggers
- Fee schedule changes
- Major policy or availability changes
- Security incidents that materially affect selection decisions
- New evidence from hands-on testing