Late consent after a payment recall

Payment Series | Episode 13

camt.029 already sent: “No response from beneficiary.”

Later, the beneficiary says:

“I agree. Please return the money.” 🤔

Now what?

Corporate A accidentally sends €25,000 twice to Beneficiary B.

→ camt.056 received to cancel the duplicate

→ Beneficiary contacted

→ No response within the applicable window

→ camt.029 sent with a negative outcome

→ Case closed

Then the beneficiary comes back later and agrees to return the funds.

Can we now generate `pacs.004`?

If this is SEPA SCT

Recall is scheme-driven.

Once the applicable Recall lifecycle has closed, late consent should not simply reopen the same Recall.

Any subsequent repayment must follow the applicable process outside that closed case.

If this is CBPR+

There is no equivalent universal business deadline that defines the late-consent window for every bank.

So where the scheme does not define the boundary, the bank must define its operational eligibility window, subject to applicable service rules, agreements and internal policy.

That means deciding:

How long does the original payment remain actionable?

Day 25 may still be workable.

Day 365 is a different story.

And that is where payment-data lifecycle matters:

Hot → Warm → Cold

The Insight 💡

Message deadline ≠ Case-closure deadline ≠ Data-retention period.

Three different clocks.

SEPA: the scheme defines the Recall boundary.

CBPR+: where no universal scheme deadline defines the line, the bank must define its operational boundary.

A closed case isn’t just a status.

It defines how long the payment remains actionable.

One episode. One practical example. One insight.

#Payments #ISO20022 #camt056 #camt029 #pacs004