This site is designed to be reliable and easy to verify. We use a clear source hierarchy, explicit evidence labels, and a last-verified date on major pages and claims.
We separate what is confirmed from what is interpreted.
Directly supported by an official source (for example, a bank press release, annual report, product page, or regulator publication).
A source-backed summary of one or more sources. The wording is ours; the facts trace back to the cited source(s).
Our interpretation of public signals (for example, documentation clarity, portal usability, or how to plan an implementation). Always labelled as interpretation.
We flag content when public information is incomplete or ambiguous. These items should be confirmed with the bank or primary source before production use.
High: primary official evidence; Medium: official evidence but partial/undated; Low: limited or indirect evidence.
When we last checked that the source and the claim still match. Developer portals and product pages can change without notice.
We prioritize sources that are most defensible and least likely to misstate product scope.
| 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 compare what is publicly visible first, and separate it from what typically moves into onboarding.
Scores are editorial summaries intended to help users navigate. They are not performance claims, SLAs, or commercial guarantees.
Counts represent publicly visible endpoints and/or documented capabilities that can be enumerated without privileged access. They may not represent full product scope.
We assess discoverability, onboarding clarity, sandbox visibility, auth/security overview visibility, event/callback documentation, and whether region differences are clearly described.
How we decide what to include and how we avoid hype.
| 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 format used across pages: 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 | Mar 23, 2026 | |
| Citi Implementations | Official bank product/implementation page | Undated page | Mar 23, 2026 | |
| J.P. Morgan Payments developer portal: llms.txt | Official developer portal index | Undated page | Mar 23, 2026 | |
| OSFI Guideline B-13 | Official regulator guidance | Guideline (see page) | Mar 23, 2026 | |
| SWIFT ISO 20022 | Official infrastructure source | Ongoing | Mar 23, 2026 |
If a source becomes unavailable or changes materially, related claims should be marked requires validation until re-verified.