This site is built to be easy to trust and easy to challenge. We show where a claim comes from, how strong the evidence is, and when a statement still needs bank validation.
Use these labels to separate facts, summaries, interpretation, and open questions.
Directly supported by an official source such as a bank press release, annual report, product page, or regulator publication.
A source-backed summary of one or more sources. The wording is ours, but the facts trace back to the cited source set.
Our reading of public signals, such as documentation clarity, portal usability, or implementation implications. Always labelled as interpretation.
Used when the public record is partial, ambiguous, or market-specific. These items should be confirmed with the bank or primary source before production use.
High: primary official evidence; Medium: official evidence but partial or undated; Low: limited or indirect evidence.
Shows when we last checked that the cited source still supports the claim. Developer portals and product pages can change without notice.
We rank sources by how defensible they are in client, legal, and executive settings.
| Priority | Source type | Examples | Notes |
|---|---|---|---|
| Official bank sources | Annual reports, investor presentations, earnings materials, product pages, developer portals, API docs, whitepapers, press releases | Preferred. Record source date and last verified. | |
| Official regulators and market infrastructure | Federal Reserve, CFPB, OSFI, Payments Canada, Bank of Canada, SWIFT, BIS | Preferred for timelines, rules, and infrastructure capabilities. | |
| Trusted primary media | Reuters, Bloomberg, FT, WSJ, American Banker, Euromoney (where accessible) | Use to contextualize, not to replace official product scope. | |
| Secondary summaries | Blogs, vendor roundups, unsourced rankings | Avoid for important claims. If referenced, label as requires validation. |
We start with what any user can verify publicly, then separate out what typically moves into onboarding.
Scorecards help users navigate. They are not performance claims, SLAs, or commercial guarantees.
These counts reflect publicly visible endpoints or documented capabilities that can be enumerated without privileged access. They do not imply full contracted scope.
We assess discoverability, onboarding clarity, sandbox visibility, auth and security visibility, event documentation, and whether regional differences are clearly described.
These rules keep the news feed useful and grounded.
| Rule | What we do | Why |
|---|---|---|
| Source hierarchy | Official bank/regulator/infrastructure sources first | Reduces misinformation and avoids paywalled paraphrase risk. |
| Recency | Prioritize the last 30 days; archive older items | Keeps the digest actionable for treasury teams. |
| Duplicate suppression | Prefer the primary source over reprints | Avoids double counting and contradictory summaries. |
| Client implication | One line on what it changes for clients | Connects news to treasury design and operating model decisions. |
| Citi-relative note | Only include when evidence supports it | Avoids unsupported superiority claims. |
This is the citation format used across the site: source, source date, last verified date, and confidence.
| Source | Type | Source date | Last verified | Confidence |
|---|---|---|---|---|
| CitiConnect® API Portal announcement | Official bank release | Apr 12, 2021 | Apr 16, 2026 | |
| Citi Implementations | Official bank product/implementation page | Undated page | Apr 16, 2026 | |
| J.P. Morgan Payments developer portal: llms.txt | Official developer portal index | Undated page | Apr 16, 2026 | |
| OSFI Guideline B-13 | Official regulator guidance | Guideline (see page) | Apr 16, 2026 | |
| SWIFT ISO 20022 | Official infrastructure source | Ongoing | Apr 16, 2026 |
If a source becomes unavailable or changes materially, related claims should be marked requires validation until re-verified. For the full live registry, open the verification center.