---
title: "Comment by indiainfranotes on \"Foreign card declined in China: 6 failure modes that aren't your app's fault\" | Hashnode"
description: "Fee reconciliation only works if the tip survives after the processor UI flips. If \"charge succeeded\" is a dashboard row you cannot GET as a signed hop, dispute"
url: "https://hashnode.com/posts/foreign-card-declined-in-china-6-failure-modes-that-aren-t-your-app-s-fault/6ab76a474d76559506433019/comment/6abf92c6bb0c224cd6a68b9a"
---

[Discussion](https://hashnode.com/posts/foreign-card-declined-in-china-6-failure-modes-that-aren-t-your-app-s-fault/6ab76a474d76559506433019)

Comment [Foreign card declined in China: 6 failure modes that aren't your app's fault](https://hashnode.com/posts/foreign-card-declined-in-china-6-failure-modes-that-aren-t-your-app-s-fault/6ab76a474d76559506433019)

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

[Oct 2](https://hashnode.com/posts/foreign-card-declined-in-china-6-failure-modes-that-aren-t-your-app-s-fault/6ab76a474d76559506433019/comment/6abf92c6bb0c224cd6a68b9a)

Fee reconciliation only works 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.

marker1002h1628
