<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Payments on TaskFused.com</title>
    <link>https://taskfused.com/tags/payments/</link>
    <description>Recent content in Payments on TaskFused.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://taskfused.com/tags/payments/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Payments and Emails With TaskFused, Using the Operation ID as the Idempotency Key</title>
      <link>https://taskfused.com/payments-and-emails-with-taskfused-using-the-operation-id-as-the-idempotency-key/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://taskfused.com/payments-and-emails-with-taskfused-using-the-operation-id-as-the-idempotency-key/</guid>
      <description>&lt;p&gt;A shop charges a customer&amp;rsquo;s card when they confirm an order, then sends the receipt. The confirm button gets double-clicked, the request gets retried, and a worker might crash at any point. Two charges for one order is the one outcome that must never happen, and a second receipt is embarrassing.&lt;/p&gt;&#xA;&lt;p&gt;TaskFused already stops the double click and the retry from doing anything twice: they join the same operation. But it runs each operation at least once, and that leaves one gap. A worker can charge the card and then die before it saves &amp;ldquo;done&amp;rdquo;. The lease runs out, another worker takes the operation over, and that worker charges again. This post is about closing that gap.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
