Recovering a wrong-chain invoice payment is operations, not a magic button

Recovery starts with: do you control keys on the chain they used? If the invoice address was Ethereum-only CREATE2, a Polygon transfer to the same 20 bytes might be a different story depending on whether that contract exists there. Often it does not, and the funds are sitting at a key path you never intended — or in a dead address.

Playbook

1. Freeze the invoice. Do not mark paid.
2. Identify asset, chain, tx, actual destination.
3. If you control the key on that chain, you can move — still not “invoice paid” until you re-issue or amend with auditor-friendly notes.
4. If you do not, you are in refund-from-payer / exchange-support / write-off land. There is no protocol that owes you a reverse bridge.
5. Log both tx hashes if a bridge happens. Fire webhooks only after the intended asset is in the intended control.

Settlematic will not pretend this is one click. Unique addresses reduce who paid which invoice confusion; they do not make all EVM chains one memory space.

Canonical: recover wrong chain crypto invoice payment. settlematic.com