Close account
Close-account checklist, in the order that avoids a leftover
A wallet zero is not the last step. Pending KYC and confirmation receipts come after. If the in-app close-account path is unpublished, this page says so.
Five steps in the right order
- 01
Wallet zero
Withdraw any balance to a payment instrument in your own name.
- 02
Pending KYC cleared
Wait for any in-flight KYC review to clear, or contact care if it has stalled.
- 03
Confirmation receipt
Ask for a confirmation receipt inside the app. Screenshot it.
- 04
Data leftovers
Check the privacy page for what data remains after close. Some records are kept by law.
- 05
Uninstall
Uninstall after the confirmation receipt. An uninstall before confirmation is not a close.
If the in-app path is unpublished
If the live Speedwin app does not show a close-account path, this page says so. Use in-product care or the on-site chat at /contact/ to request a close. Keep the ticket date and the request text in a screenshot.
Where to continue
The five steps in plain words
Step one is wallet zero. Withdraw any balance to a payment instrument in the reader's own name. A wallet that still has a balance is not a wallet that can be closed.
Step two is pending KYC cleared. Wait for any in-flight KYC review to clear, or contact care if it has stalled. A KYC that is in flight is a KYC that can hold a withdrawal.
Step three is confirmation receipt. Ask for a confirmation receipt inside the app. Screenshot it. A close without a receipt is the wrong kind of close.
Step four is data leftovers. Check the privacy page for what data remains after close. Some records are kept by law. The desk names the law; the desk does not delete the data.
Step five is uninstall. Uninstall after the confirmation receipt. An uninstall before confirmation is not a close.
If the in-app path is unpublished
If the live Speedwin app does not show a close-account path, this page says so. Use in-product care or the on-site chat at /contact/ to request a close. Keep the ticket date and the request text in a screenshot.
A close request that arrives at the desk is not a close; the desk does not file a close. The desk points to the verified path; the verified path does the close.
What the desk will not do
This desk does not file a close-account request. The verified route is in-product care or the on-site chat at /contact/. The desk points to the verified route; the verified route does the close.
This desk does not guarantee a confirmation receipt. A confirmation receipt that arrives inside the live product is the source; a confirmation receipt that arrives by email is the wrong place for a rule.
Why the five steps matter
Step one is wallet zero. A wallet that still has a balance is a wallet that can hold a withdrawal. The reader withdraws the balance before the close. Step two is pending KYC cleared. A KYC that is in flight is a KYC that can hold a withdrawal. The reader waits for the KYC to clear before the close.
Step three is confirmation receipt. A close without a receipt is the wrong kind of close. The reader asks for a receipt inside the app; the reader screenshots the receipt. Step four is data leftovers. Some records are kept by law; the desk names the law; the desk does not delete the data.
Step five is uninstall. An uninstall before confirmation is the wrong kind of uninstall. The reader waits for the receipt, then uninstalls.
What if the in-app path is unpublished
If the live Speedwin app does not show a close-account path, this page says so. The reader uses in-product care or the on-site chat at /contact/ to request a close. The reader keeps the ticket date and the request text in a screenshot.
A close request that arrives at the desk is not a close; the desk does not file a close. The desk points to the verified path; the verified path does the close.
Why the five steps matter, in two paragraphs
Step one is wallet zero. A wallet that still has a balance is a wallet that can hold a withdrawal. Step two is pending KYC cleared. A KYC that is in flight is a KYC that can hold a withdrawal. Step three is confirmation receipt. A close without a receipt is the wrong kind of close.
Step four is data leftovers. Some records are kept by law; the desk names the law; the desk does not delete the data. Step five is uninstall. An uninstall before confirmation is the wrong kind of uninstall.
Why the receipt is the proof
The receipt is the proof because the receipt is the document that names the close. A close without a receipt is the wrong kind of close; a close with a receipt is the right kind of close.
The reader screenshots the receipt. The reader saves the screenshot in a folder. A folder that does not have the receipt is a folder that is missing the proof.
Why the in-app path is the verified route
The in-app path is the verified route because the in-app path is the path the live product publishes. The on-site chat is the second verified route. A path that the live product does not publish is the wrong path.
Why the receipt is the proof
The receipt is the proof because the receipt is the document that names the close. A close without a receipt is the wrong kind of close; a close with a receipt is the right kind of close.
The reader screenshots the receipt. The reader saves the screenshot in a folder. A folder that does not have the receipt is a folder that is missing the proof.
Frequently asked about deleting a Speedwin account
What if the in-app close-account path is unpublished?
This page says so. The reader should use in-product care or the on-site chat at /contact/ to request a close.
What is data leftover?
Some records are kept by law. The desk names the law; the desk does not delete the data.
Why is the receipt the proof?
The receipt is the proof because the receipt is the document that names the close. A close without a receipt is the wrong kind of close.
Close-account checklist
- 01
Wallet zero
Withdraw any balance to a payment instrument in your own name.
- 02
Pending KYC cleared
Wait for any in-flight KYC review to clear.
- 03
Confirmation receipt
Ask for a confirmation receipt inside the app. Screenshot it.
- 04
Data leftovers
Check the privacy page for what data remains.
- 05
Uninstall
Uninstall after the confirmation receipt.
Why the five steps matter, in two paragraphs
The five steps matter because the five steps prevent a leftover. A leftover is a balance that did not get withdrawn, a KYC that did not get cleared, a receipt that did not arrive. The leftover is what the reader will discover months later, when the reader has forgotten the original close. The five steps are the prevention; the prevention is what the reader owes the future reader.
The five steps are wallet zero, pending KYC cleared, confirmation receipt, data leftovers, uninstall. The order matters. A reader who skips a step has not finished the close.
What a leftover looks like
A leftover looks like a small balance that the reader has forgotten. The small balance is usually the difference between a deposit and a withdrawal; the difference is what the reader has to clear before the close. A leftover that is not cleared is a leftover that the reader has to clear later.
Why the receipt is the proof
The receipt is the proof because the receipt is the document that names the close. A close without a receipt is the wrong kind of close. The reader screenshots the receipt; the reader saves the screenshot in a folder; the folder is the proof.
Why the order matters
The order matters because the order is the rule. Wallet zero first. Pending KYC cleared second. Confirmation receipt third. Data leftovers fourth. Uninstall fifth. The order prevents a leftover. The leftover is what the future reader discovers months later.
A reader who follows the order has done the close right. A reader who skips a step has not finished the close. The desk points to the verified route; the verified route does the close.
One more rule for the close
The close is not the close without the receipt. The receipt is the proof; the proof is the document that names the close. A close without a receipt is the wrong kind of close. The reader screenshots the receipt; the reader saves the screenshot in a folder; the folder is the proof.