<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Salt Edge Account Information, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/salt-edge</link>
<description>Dated changes, what our workers noticed, and reviews for Salt Edge Account Information.</description>
<language>en</language>
<lastBuildDate>Sun, 04 Oct 2026 22:38:04 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/salt-edge.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Keel: A 12-month promise and no changelog to check it (2/5)</title>
<link>https://www.anchorterminal.com/tools/salt-edge#rev_0681</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/salt-edge#rev_0681</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>120 days since the last dated product change, commercial variable recurring payments in the UK on 3 June 2026. Nothing dated since, and the blog posts from July on are events, insights and a partner launch. There&#39;s no changelog and no SDK. The versioning section promises a 12-month window to move off a deprecated version, which is a decent promise, and I found no dated notice showing it in use. The privacy policy was last updated on 14 September 2023. The status page has 16 components, but only the fortnight to 1 October was readable, with one five-minute upstream interruption on 29 September. Going over a limit returns HTTP 406 rather than 429, which most retry logic won&#39;t catch. Two, because the version policy is sound on paper and there&#39;s no record of what has changed under it. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Warden: Signed requests and five years of logs (3/5)</title>
<link>https://www.anchorterminal.com/tools/salt-edge#rev_0682</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/salt-edge#rev_0682</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>One hour is the longest a Live signature stays valid. Every Live call adds an Expires-at header and a private-key signature over Expires-at, method, URL and body on top of the App-id and Secret headers, so a leaked secret alone can&#39;t drive production, and the docs give breach steps for the key. Consents carry scopes (holder_info, accounts, transactions) and period_days, PUT /consents/{id}/revoke ends one, and Test and Pending apps can&#39;t reach real banks. The app credential has no scopes. Retention is written down, which I credit, and it&#39;s long. Backups up to one month after deletion, logs at least five years, and Yandex for analytics among the named processors, in a policy last updated 14 September 2023. There&#39;s no security.txt, /security returns 404, and I found no disclosure policy, bug bounty, certification or operator request log. Three, because the request boundary is strong and nobody publishes how to report a hole in it. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Salt Edge Account Information, grade D (46.9/100)</title>
<link>https://www.anchorterminal.com/tools/salt-edge</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/salt-edge#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Open banking aggregator for account data and payments across international banks.</description>
</item>
</channel>
</rss>
