How to block and replace lost or stolen cards with an AI agent

Let the agent freeze the card the moment a customer reports it missing, since a freeze can be lifted. Permanent cancellation follows once the customer confirms it is lost or stolen. The replacement goes only to an address that has stayed the same for a set period; anything else, and any transaction the customer disputes, goes to a person.

What does the process involve, and who owns it?

A lost or stolen card report has three parts that are often run as one: stopping the card being used, cancelling it for good, and sending a new one. They carry different risks. Stopping use is urgent and almost harmless. Cancellation cannot usually be reversed, since a card reported stolen is rarely reactivated. Replacement sends a working payment instrument through the post, which is exactly what someone who has taken over the account wants.

The head of card operations owns the process. The fraud team owns the rules for when a replacement is held. A named card services team leader decides held replacements. The general principles for agents in this area are in our guide to AI agents in banking.

What does the agent prepare, and what does a person approve?

1. Agent, depth 3: freezes the card on report. If the customer is authenticated, freeze at once. If they cannot authenticate, a freeze is still reasonable because it only stops spending; record that authentication was incomplete. Evidence: freeze event with authentication status.
2. Agent, depth 1: reviews recent activity with the customer. It lists transactions since the customer last had the card and asks which they recognise. Evidence: list shown and responses.
3. Agent, depth 3: cancels the card permanently once the authenticated customer confirms it is lost or stolen. Evidence: cancellation with reason code.
4. Agent, depth 2: prepares the replacement order. Address on file, delivery method, any linked recurring payments or stored card details that will need updating. Evidence: draft order.
5. Platform: checks the replacement against hold rules. Address or phone changed within the set period, several replacements in a short period, recent failed login attempts, a new device on the account. Evidence: verdict naming the rule.
6. Agent, depth 3: issues the replacement when no hold rule fires. Evidence: order reference and dispatch.
7. Person, card services team leader: decides held replacements. Usually by contacting the customer through a channel already on file. Evidence: decision and contact record.
8. Agent, depth 2: opens a claim for any unrecognised transaction and hands it to the unauthorised transaction process. Evidence: claim reference linked to the card case.

How an agent should handle freezes and lifts more generally, including customer-initiated ones, is set out in how to let an AI agent block and unblock cards.

Which controls matter, and what evidence do they leave?

Freeze first, ask later. The agent never delays a freeze to finish authentication. Evidence: freeze time against report time.

Cancellation needs an authenticated confirmation. A stranger who knows a card number should be able to stop it, not cancel it. Evidence: authentication record on the cancellation.

Address stability rule. Replacements go to an address unchanged for a set period. Evidence: address history checked on each order.

Velocity rule. Several replacements in a short window are held. Evidence: count on each verdict.

Card data kept out of the conversation. The agent refers to cards by the last four digits and never asks the customer for the full number or security code. Evidence: masked values in the log.

Disputes routed, not decided. The agent does not decide refunds for unrecognised transactions. Evidence: claim reference and hand-off.

What should you measure?

• Time from report to freeze. The most important number in the process.
• Replacements held, by rule. One rule firing on almost every order needs tuning.
• Held replacements confirmed as fraud. This shows whether the hold rules catch real attacks.
• Customers chasing a replacement after a hold, which shows whether holds are cleared promptly.
• Unrecognised transactions reported per case.

Where does it usually go wrong?

The address-change pattern. A fraudster who controls the account changes the address, then reports the card lost. If the agent ships to the new address, it posts them a card. The address stability rule exists for this.

Freeze and cancel are merged. An unauthenticated caller permanently cancels a customer's card, and the real customer finds it declined at a till.

Unrecognised transactions are blocked, not claimed. The agent tries to stop a pending transaction instead of opening a claim. Some can be stopped and many cannot; whether an agent should try is covered in whether an AI agent can block a suspicious transaction.

Recurring payments are forgotten. The customer's bills fail on the old card. The agent should tell the customer which merchants may need new details.

Fees are waived inconsistently. If replacement fees apply, the waiver rule belongs in the bounds, not in the agent's judgement on each call.

Where Pryme fits

In Pryme, freezing, cancelling and issuing are separate capabilities, each certified on your own cases and each checked against your hold rules at the moment of action. A replacement that trips a rule becomes a held verdict for a named team leader, and every step is filed in one case record.