<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Finance on XKV.org</title>
    <link>https://xkv.org/tags/finance/</link>
    <description>Recent content in Finance on XKV.org</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 19 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://xkv.org/tags/finance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A Credit Limit Dropped From 100 to 50 and XKV Shows the Three Steps Behind It</title>
      <link>https://xkv.org/a-credit-limit-dropped-from-100-to-50-and-xkv-shows-the-three-steps-behind-it/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://xkv.org/a-credit-limit-dropped-from-100-to-50-and-xkv-shows-the-three-steps-behind-it/</guid>
      <description>&lt;p&gt;A customer calls support. Their credit limit was 100 yesterday and it&amp;rsquo;s 50 today, and nobody told them why. The support agent can see the 50. Everything else is spread across three services.&lt;/p&gt;&#xA;&lt;p&gt;The limits service set the 50, under its risk policy. The risk model raised the account&amp;rsquo;s score the day before. Billing had recorded a chargeback from the bank that morning. Each service did one reasonable thing, and each logged it in its own way. Putting the story together means knowing which logs to open and in what order.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
