March 4, 2026

# Coldcard troubleshooting

## Coldcard Mk 3+ hardware devices are compatible with Casa multisig vaults.

Whether you are **[adding the Coldcard](https://support.casa.io/knowledge/adding-coldcard-to-your-casa-vault-1?hsLang=en)**, doing a [**health check**](https://support.casa.io/knowledge/performing-a-health-check-with-coldcard?hsLang=en), or **[sending funds](https://support.casa.io/knowledge/signing-a-transaction-with-coldcard-1?hsLang=en)** from your Casa vault, it has the unique benefit of offering offline-signing via PSBTs to add a signature to your vault.

**One thing to keep in mind when using your Coldcard is to remember to check for the most recent firmware updates [here.](https://support.casa.io/knowledge/supported-platforms-and-hardware-device-firmware?hsLang=en)**

With Coldcard, the instructions for performing a health check and signing a transaction do differ slightly. See the below articles for the instructions for each function:

**[Performing a Health Check with Coldcard](https://support.casa.io/knowledge/performing-a-health-check-with-coldcard?hsLang=en)**

**[Signing a Transaction With Coldcard](https://support.casa.io/knowledge/signing-a-transaction-with-coldcard-1?hsLang=en)**

**Some common Coldcard errors are:**

**[Failure. My XFP not involved](https://support.casa.io/knowledge/coldcard-troubleshooting#XFP)**

[**C** **hange fraud**](https://support.casa.io/knowledge/coldcard-troubleshooting#changefraud)

[**Couldn't find signature**](https://support.casa.io/knowledge/coldcard-troubleshooting#cant_find_sign)

**[Failure Invaid PSBT multisig.py 715](https://support.casa.io/knowledge/coldcard-troubleshooting#C715)**

[**Failure Invalid PSBT multisig.py 716**](https://support.casa.io/knowledge/coldcard-troubleshooting#C716)

[**Failure XPUBs in PSBT do not match any known wallet**](https://support.casa.io/knowledge/coldcard-troubleshooting#donot_match)

**[Error: file must be .psbt](https://support.casa.io/knowledge/coldcard-troubleshooting#must_be_psbt)**

**["Sorry, there was a problem completing your Health Check. Problem Detail: Error. No authorization token was found"](https://support.casa.io/knowledge/coldcard-troubleshooting#sorry)**

**Failure. My XFP not involved**

Solution: Double-check that the Coldcard is the device used for that vault. **If you are performing a key rotation make sure that you are not using the device you marked for replacement to try to sign.**

**Change fraud**

There is an issue with the Coldcard firmware where it looks for the OP_CHECKMULTISIG opcode in the redeem script, but can't find it because it isn't taking into account that we use nested segwit (P2SH-P2WSH). It's assuming all addresses are P2SH or P2WSH.

You can get around this by going to **Settings > Multisig Wallets > Skip Checks**, and turning that setting on.

**Couldn't find signature**

Solution: Make sure to upload the correct file to confirm this request. It will prompt you with the file name to look for in the error message.

**Failure Invaid PSBT multisig.py 715**

This is shown when you are trying to sign a BTC transaction while in testnet mode or trying to sign a testnet transaction while in BTC mode. Ensure your mode matches your transaction type.

Advanced > Danger Zone > Testnet or BTC

**Failure Invalid PSBT multisig.py 716**

This is shown when trying to sign a testnet transaction, but the right setting has not been configured. In order to sign for testnet you must do the following:

In Coldcard settings, select: Advanced > Danger Zone > Have ‘Testnet: BTC’ checked, not ‘Bitcoin’

**Failure XPUBs in PSBT do not match any known wallet**

This is shown if "Trust PSBT" is not enabled.

In Coldcard settings, select Multisig Wallets > Trust PSBT and select "Trust PSBT."

If you've tried the above steps and are still having issues, please **[reach out to our support team](mailto:help@team.casa)**, and we're happy to assist.

**Error: file must be .psbt**

You are likely on Windows and have Sparrow installed. You must either uninstall Sparrow temporarily or use a Mac.

**Sorry, there was a problem completing your Health Check. Problem Detail: Error. No authorization token was found**

Expired link. Try the health check or the transaction again.