Stop payment request

How do we take a stop payment from any channel and place it in the core with the item details, the fee consent and the expiry right?

Give the stop payment its own guided process. Callvu identifies the customer, prefills the recent items so they pick the check or the preauthorized debit rather than typing it, discloses the fee and takes consent, applies the rule for the item type (a check under the UCC, a preauthorized electronic transfer under Reg E), places the stop in the core with the right expiry, and confirms to the customer.

In scopeSimpleCallvu moves: prefill, write back

Talk to an expert Try it in the sandbox

Last updated November 6, 2026.

The problem today

The check number is taken over the phone, typed wrong, and the check pays anyway.

Today, without Callvu

A customer calls to stop a check. The agent asks for the number, the amount and the payee, types them into the core, and charges the fee. The customer read the number from a stub and got one digit wrong, so the stop does not match and the check clears. Or the customer wanted to stop a recurring debit, which is a different kind of stop with a different rule, and the agent placed a check stop instead.

The rules differ by item. A stop on a check under the UCC must describe the item with reasonable certainty, is effective for six months in writing and may be renewed, and the bank is liable if it pays over a valid stop. A stop on a preauthorized electronic transfer under Reg E must be received at least three business days before the scheduled transfer, and the bank may require written confirmation within fourteen days. A process that does not know which one it is placing cannot enforce either.

The fee needs consent and a disclosure, and the expiry needs a date the customer was told. Both are easy to lose on a call.

How it runs

From the requestto the system of record.

A customer asks to stop a payment in the app, on the web, on a call, in a branch, or through an AI agent. Callvu identifies the customer and opens the account's recent and scheduled items.

Customer: Picks the item, confirms its details, consents to the fee, and receives the confirmation with the expiry.
Callvu: Identifies, prefills the items, classifies the stop, applies the rule, takes the fee consent, places the stop in the core and confirms.

Identify and prefill
The customer is authenticated under the bank's policy for the channel. Callvu reads recent checks (paid and outstanding), pending items and scheduled preauthorized transfers from the core and shows them, so the customer picks the item rather than typing a number. An item not yet presented can be described by number, amount and payee.
Classify the stop
The item type sets the rule: a check (UCC Article 4, six-month written stop, renewable), a preauthorized electronic transfer (Reg E, three business days before the scheduled date, with the option to stop all future transfers from that payee), or a cashier's or certified check, which the policy handles differently.
Disclose and consent
The stop payment fee from the account's fee schedule is shown, the expiry date is stated, and the customer consents on a process-controlled screen. For a preauthorized transfer stop, the customer is told whether written confirmation is required and by when.
Write back
The stop is placed in the core with the item details as picked, the type, the expiry date and the fee, and the confirmation with the expiry goes to the customer. A stop that cannot be placed (the item already paid, the Reg E window missed) is explained and, where the policy allows, routed to a person.

Where it ends: The stop is in the core with the exact item details, the right type and expiry, and the fee consented, and the customer has the confirmation. The Decision Trace shows the rule applied; the Audit Trace shows the identification, the consent and the write.

Runtime enforcement

What is enforcedwhile the work runs.

The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.

Regulations

UCC Article 4, stop payment orders (UCC 4-403): A customer may stop payment of any item drawn on the customer's account by an order describing the item with reasonable certainty, received in time for the bank to act. A written stop is effective for six months (an oral stop lapses after fourteen days unless confirmed in writing) and may be renewed. A bank that pays over a valid stop is liable for the loss, and the burden of proving the loss is on the customer.
Reg E stop payment on preauthorized transfers (12 CFR 1005.10(c)): A consumer may stop payment of a preauthorized electronic fund transfer by notifying the bank orally or in writing at least three business days before the scheduled date. The bank may require written confirmation within fourteen days of an oral notice, if it tells the consumer so when the notice is given. The consumer may also revoke the authorization with the payee.
Reg DD fee disclosure (12 CFR 1030.4(b)(4)): The stop payment fee is a disclosed account fee; the process shows the fee from the schedule before the customer consents.

Company policies

The item types that can be stopped in self-service, and the ones that need a person (cashier's checks, items in process), are set by the bank's policy and applied by Callvu.
The customer picks the item from the account's activity where it exists, so the details match what will present.
The fee is disclosed and consented before the stop is placed; the expiry is stated in the confirmation.
A Reg E stop outside the three-business-day window is refused with the reason, not placed and forgotten.
The core is the system of record; the stop is placed once with its type and expiry.

Controls

Channel authentication before account activity is shown.
Item selection from recent and scheduled activity.
Classification by item type with the matching rule.
Fee disclosure and consent on a process-controlled screen.
Reg E window check before placing a preauthorized transfer stop.
Expiry set from the type and written to the core.
Confirmation with the expiry sent to the customer.

Clocks and deadlines

Reg E stop window: At least three business days before the scheduled transfer.
Written confirmation (Reg E and UCC): Fourteen days from an oral stop where the bank requires it; the request is in the confirmation.
Check stop expiry (UCC): Six months for a written stop, renewable; the expiry date is on the record and the customer is told before it lapses.

Documents and checks

The authentication result
The item as picked or described, with number, amount, payee and date
The fee disclosure and the customer's consent, timestamped
The stop record in the core with type and expiry
The confirmation sent to the customer

In the Decision Trace

The item type and the rule it triggered.
The window check for a preauthorized transfer.
The fee disclosed and the consent captured.
The expiry set and why.

In the Audit Trace

The channel and the time of the request.
The item selection and any details entered.
The write to the core with its time.
The confirmation sent and the renewal reminder where one applies.

The handoff

Between the front doorand the back office.

The front door

The app, the web, a call, a branch, or an AI agent over MCP. The customer picks the item and consents on a process-controlled screen; nothing is keyed by an agent.

The back office

There is no back-office step for a standard stop: it is placed in the core by the process. Deposit operations sees stops that could not be placed and why.

The Decision Desk

A stop the rule refused (an item already paid, a Reg E window missed, a cashier's check) can be routed to deposit operations in the Decision Desk where the bank's policy offers an alternative (a return request, an indemnity process), with only those outcomes.

Proof

In scope.Proof at scale, not one process at a time.

The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.

More than 1,000 processes are live across Callvu customers.

Across Callvu customers

Banca Transilvania automated more than 100 workflows with Callvu.

BNK-04

Bank Leumi digitized all loan application and servicing workflows within six months, and dozens more processes since.

BNK-01

Questions

What buyers ask next,answered plainly.

Why pick the item instead of typing the check number?

Because a stop must describe the item with reasonable certainty, and a typed number with one wrong digit does not match. Picking from the account's activity makes the stop match what presents.

Can a customer stop a recurring debit?

Yes, under Reg E, at least three business days before the scheduled date. The process checks the window, offers to stop all future transfers from that payee, and tells the customer about written confirmation where the bank requires it.

When does a check stop expire?

Six months for a written stop under the UCC. The expiry is on the record and in the confirmation, and the customer is reminded before it lapses so they can renew.

What if the check already paid?

The stop cannot be placed, and the customer is told why. Where the bank's policy offers an alternative, the request routes to deposit operations with that option.

Related processes

Service requests completed digitally Unauthorized ACH claim (WSUD)Check fraud and forgery claims Try it in the sandbox All banking and credit unions processes

Bring this process, or the one that costs you most.

We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.