Playbook, fintech app
Nothing switches off cleanly while money is still pointed at the account
Closing an account is an operation with an order to it, and almost nobody knows the order before they start. The balance has to reach somewhere in the same name, the card stops working at the moment of closure rather than at the end of a month, and anything anybody else has arranged to send to or take from that account carries on arriving until it is redirected. Get the sequence wrong and a salary lands in a closed account.
Why this is not the general answer
The handling pattern for cancellations holds across every trade. What follows is the part that does not.
- There is no period already paid for, so the usual reassurance about access continuing until a date does not apply: closure is an event and the card stops at it.
- A balance cannot simply be abandoned, and the destination is normally an account in the same name, which means somebody locked out elsewhere cannot complete a closure at all until that is sorted.
- Incoming payments and standing arrangements set up by other people keep pointing at the account after it closes, and a returned salary is a far worse outcome than a fee, so the sequence is the actual advice.
- An account under review or with an open dispute usually cannot be closed, which is a genuine constraint rather than a retention tactic and is best published plainly before somebody accuses you of the second.
How it arrives
- how do i close my account for good
- what happens to the money left in my balance
- will my card stop working straight away
- i have a direct debit set up on this account what do i do
- can i close the account while a payment is still pending
- if i close it can i open a new one later
What has to be indexed for this to work
| The closure sequence, written in the order it has to happen | Redirect what is arriving, empty the balance, then close. Written as a sequence rather than a list of facts, because the whole value is the order and the consequence of getting it wrong is somebody's wages bouncing. |
|---|---|
| Where a remaining balance can be sent | Whether the destination must be an account in the same name, what happens to a small residual amount, and what you do with a balance nobody claims. The same name condition is the one that stops closures, and it is rarely mentioned until it does. |
| What blocks a closure | An open review, a disputed transaction, a pending payment, an outstanding amount. Publishing the list stops a blocked closure being read as obstruction, which is the complaint this generates when it arrives as a surprise. |
| What closure does not do | The record retention position, whether a new account can be opened later, and whether closing affects anything held with a connected firm. People assume closure is an eraser, and it is not. |
The reply
Closing is an event rather than the end of a billing period, so the card stops working at the point the account closes rather than at the end of a month [1]. Before that, anything set up to arrive at or be taken from the account needs redirecting, because a payment sent to a closed account is returned and that is slow to unpick. The balance has to be sent to an account in your own name, and a closure cannot usually complete while a payment is pending or a review is open [2]. I cannot see your account, close anything, or check whether something is outstanding. Leave your name and the email on the account and the team will take it from there.
The card sentence goes first because it is the assumption most likely to cost somebody money this week. The redirection warning is framed around the returned payment rather than around good practice, since that is the consequence people act on. Saying plainly that reviews block closures removes the suspicion that the firm is stalling.
Where it stops
The trigger. The visitor asks to close an account, says a closure has not completed, or asks what is outstanding on their own account.
I cannot close an account or see what is outstanding on one. Leave your name and the email the account is registered to, and the team will pick it up. If you are closing because of something that has gone wrong, put that in the message as well so it reaches the right people.
It stops answering before it guesses, says who will pick it up, and asks for the one thing that makes a reply possible. Nothing about it reads as a dead end.
Never say this here
Out of bounds
- Never say an account has been closed, scheduled for closure, or is in the process of closing.
- Never say a balance will be sent to a particular place, or by a particular date.
- Never tell somebody a review or a hold will be lifted so that their closure can go through.
- Never say a new account can be opened later, since that is an eligibility decision rather than a fact about the product.
Questions
- Should it try to keep the customer?
- No. On a money app the person closing is frequently doing it because something went wrong, and a retention line from a widget is what turns a quiet closure into a public complaint. Give them the sequence accurately and take the details.
- Can it tell somebody whether their closure has completed?
- No. It has no view of any account at any point, so it can describe what closure does and cannot confirm that it happened. That distinction matters more here than elsewhere, because somebody who believes an account is closed may stop watching it.
- Is publishing what blocks a closure a bad look?
- It is the opposite. A customer who learns mid closure that a review is in the way assumes they are being held hostage. The same fact read beforehand is understood as an ordinary condition, and it arrives without an accusation attached to it.
Keep reading
- Everything for a fintech appFees, limits and identity checks are safe ground. Balances, transactions and anything reading as a personal recommendation are not.
- Handling cancellations in generalCancellation content is hard to find on purpose. What it costs to answer plainly, how notice periods work, and what happens to data on the way out.
- The money is coming back from somebody the customer has not written toPending against settled, who actually returns the money, and why a card dispute runs on a process the app does not operate.
- The customer is standing at a checkout, not sitting at a deskWhen payments fail everywhere at once the cause may sit upstream. What to say when the app cannot see the rail or name whose it is.
- Onboarding here is a check somebody else runs, not a configurationAccepted documents, what a proof of address must show, and why a rejected photo is most of onboarding on a regulated money app.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.