Test freezing a card and proving payments decline

Failure modes in this flow

The only meaningful test of a card control is a transaction attempted in each state, which is what separates this from a toggle test.

• Frozen state is reported - a notice that new payments will be declined.
• A payment is actually declined - with the merchant, the amount and a reason naming the freeze.
• Unfrozen state is reported - a notice that payments work again.
• A payment is actually approved - and no new declined entry is added.

That final clause matters. A card that approves the payment while still logging a decline has a reporting bug that would show a customer a transaction they did not have, which erodes exactly the trust the freeze feature exists to build.

Writing the objective

The declined entry is asserted with its merchant, amount and reason, so a decline logged without a cause is distinguishable from one correctly attributed to the freeze.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/revolut-clone-app/card?reset=true
max_steps: 45
tags: [revolut, fintech, cards]
---

# Revolat 19.1: Card freeze

Catalog objective: freeze the virtual card, confirm declines, then unfreeze.
Key assertion: the state toggles and the card is usable again.

## Freeze the card
Verify the card badge reads that the card is active, then click the freeze button and verify a notice says the card is frozen and new payments will be declined.

## Verify a payment is really declined
Click "Simulate purchase" and verify a notice reads "Payment declined - the card is frozen." and the declined list shows a "Metro Grocer" entry at "$24.60" with a reason of "Card is frozen".

## Unfreeze the card
Click the unfreeze button and verify a notice says the card is unfrozen and payments work again.

## Verify the card works again
Click "Simulate purchase" and verify a notice reads "Payment approved - $24.60 at Metro Grocer." with no new declined entry added.

The fourth step asserts both the approval and the absence of a new decline, which is a positive and a negative assertion about the same action.

The assertions in detail

Two states, each with a claim and a proof.

Testing the return path is as important as the freeze. A card that cannot be unfrozen strands a customer who found their wallet, and support cannot fix it from their side.

Running it locally

kane-cli testmd run tests/revolut/card-freeze_test.md

Add a variant covering a recurring payment against a frozen card, since subscriptions are often exempted deliberately and that exemption needs to be intentional.

Security controls are worth verifying behaviourally rather than by state. Evidence based QA covers retaining the proof, and running Kane CLI in CI covers checking it on every build.