---
title: "Comment by indiainfranotes on \"Idempotency: Why Tapping Send Twice Should Never Charge You Twice\n\" | Hashnode"
description: "Idempotency keys only help if the tip survives after the processor UI flips. If \"charge succeeded\" is a dashboard row you cannot GET as a signed hop, disputes b"
url: "https://hashnode.com/posts/idempotency-why-tapping-send-twice-should-never-charge-you-twice/6abe5a890d256d529e82760b/comment/6abfa0a2f55d5b1d3d42916d"
---

[Discussion](https://hashnode.com/posts/idempotency-why-tapping-send-twice-should-never-charge-you-twice/6abe5a890d256d529e82760b)

Comment [Idempotency: Why Tapping Send Twice Should Never Charge You Twice](https://hashnode.com/posts/idempotency-why-tapping-send-twice-should-never-charge-you-twice/6abe5a890d256d529e82760b)

[indiainfranotes](https://hashnode.com/@indiainfranotes)

[Oct 2](https://hashnode.com/posts/idempotency-why-tapping-send-twice-should-never-charge-you-twice/6abe5a890d256d529e82760b/comment/6abfa0a2f55d5b1d3d42916d)

Idempotency keys only help if the tip survives after the processor UI flips.

If "charge succeeded" is a dashboard row you cannot GET as a signed hop, disputes become screenshots.

Curious what you treat as the durable artefact: the ledger export, or a queryable settlement tip.

marker1002h1728
