Freeze a card from one sentence, after the customer confirms
Last updated 13 October 2026
The customer says they do not recognise a charge and asks to freeze their card. Rendel finds the charge and the card it was made on from your API, explains what freezing does, and freezes it through your endpoint once the customer confirms.
Why it matters
Freezing a card is a task customers usually do under stress. Done from one sentence, the app answers with the charge itself and the card it hit, rather than a menu path to find.
In Corvo, a demo app
Asked: “I don't recognise this €89.99 charge. Freeze my card.”
Answered: That charge was made on your debit card ending 4821 on Oct 7. Freezing the card stops new payments at once, and you can unfreeze it any time.
Waited for the tap on: Freeze your debit card ending 4821?
After the tap: Your debit card ending 4821 is frozen. No new card payments or cash withdrawals will go through. The €89.99 from DGTL*SVC 8841 was already taken, so to ask for it back, open a dispute.
Questions
Can it dispute the charge too?
If you give it a dispute action, yes: it opens the dispute through a form and a confirmation, and never decides it.