Wallet and KYC
Documents, holds, and proofs on a Speedwin wallet
Wallets usually ask for a government photo ID and a payment instrument in the same name. Holds start when those names diverge, or when a reversal lands after a payout request.
Documents a Speedwin wallet usually asks for
Why holds happen
A hold usually has one of three causes: a name mismatch, a back-dated document, or a reversal after a payout request. Screenshot the hold text on the live screen. Two identical retries usually fail a third time.
Where to continue
Why holds happen
A hold usually has one of three causes: a name mismatch, a back-dated document, or a reversal after a payout request. The three causes are the three things the desk names because the three things are the three things a reader can fix.
A hold that names none of the three causes is a hold that the desk treats as a stop sign. The reader should pause after the second retry and use in-product care.
A hold that names one of the three causes is a hold the reader can fix. Fix the named cause and only the named cause. Resending the same file usually fails the same way.
Discipline before the third attempt
- 01
Match the names exactly
The name on the document and the name on the payment instrument should match letter for letter.
- 02
Use a current document
A document with a current issue date is the right document. A back-dated document is the wrong document.
- 03
Keep the upload sharp
A blurry upload is the wrong upload. Re-scan rather than re-photograph where possible.
- 04
Stop the third identical retry
Two identical retries usually fail a third time. Use in-product care after the second.
What the desk will not invent
This desk does not print a Speedwin payout time. A payout time that is copied from a forum is the wrong number.
This desk does not print a Speedwin KYC SLA. A KYC SLA that is copied from a forum is the wrong number.
This desk does not print a Speedwin hold duration. A hold duration that is copied from a forum is the wrong number.
Why a name mismatch is the most common cause
A name mismatch is the most common cause because a wallet asks for two names. The two names are the document name and the payment instrument name. The two names should match letter for letter. The matching is structural; the structural matching is the rule.
A reader who matches the names before the third retry has read the rule. A reader who retries three times without matching has not read the rule.
Why a back-dated document is the second most common cause
A back-dated document is the second most common cause because some wallets reject documents older than a stated window. The window is a house line; the house line is not a statute. The reader uses a document with a current issue date.
A document with a current issue date is the right document. A document with a back-dated issue date is the wrong document.
Why a reversal after a payout is the third cause
A reversal after a payout request is the third cause because the reversal changes the wallet balance. The wallet places a hold on the next payout until the reversal is settled. The hold is not a complaint; the hold is a structural response to the reversal.
A reader who waits for the reversal to settle has read the rule. A reader who retries the payout without waiting has not.
Why the three causes matter
Cause one is a name mismatch. Cause two is a back-dated document. Cause three is a blurry upload. The three causes are the three things the desk names because the three things are the three things a reader can fix.
A hold that names none of the three causes is a hold that the desk treats as a stop sign. The reader should pause after the second retry and use in-product care.
Why the discipline matters
Two identical retries usually fail a third time. The fix is not a third retry. The fix is a different file, a different name, or a different date. The fix is a one-time change, not a three-time repeat.
A reader who treats the discipline as the method has read the rule. A reader who treats the discipline as decoration has not.
Why the in-product path is the verified route
The in-product path is the verified route because the in-product 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 discipline matters
Two identical retries usually fail a third time. The fix is not a third retry. The fix is a different file, a different name, or a different date. The fix is a one-time change, not a three-time repeat.
A reader who treats the discipline as the method has read the rule. A reader who treats the discipline as decoration has not.
Frequently asked about Speedwin KYC and wallet
What documents does a wallet ask for?
A government photo ID, a payment instrument in the same name, sometimes an address proof, sometimes a selfie.
Why do holds happen?
A name mismatch is the most common cause. A back-dated document is the second. A reversal after a payout is the third.
What is the verified route?
In-product care is the verified route. The on-site chat at /contact/ is the second verified route.
Discipline before a third attempt
- 01
Match the names
Letter for letter, including middle name order.
- 02
Use a current document
Back-dated documents are the second most common rejection cause.
- 03
Keep the upload sharp
Re-scan rather than re-photograph where possible.
- 04
Stop the third identical retry
Use in-product care after the second.
Why the three causes matter, in two paragraphs
The three causes matter because the three causes are the three things a reader can fix. Cause one is a name mismatch. Cause two is a back-dated document. Cause three is a blurry upload. The three causes are the three things the desk names because the three things are the three things a reader can fix.
A hold that names none of the three causes is a hold that the desk treats as a stop sign. The reader should pause after the second retry and use in-product care.
Why a name mismatch is the most common
A name mismatch is the most common cause because a wallet asks for two names. The two names are the document name and the payment instrument name. The two names should match letter for letter. The matching is structural; the structural matching is the rule.
Why a back-dated document is the second most common
A back-dated document is the second most common cause because some wallets reject documents older than a stated window. The window is a house line; the house line is not a statute. The reader uses a document with a current issue date.
Why a reversal after a payout is the third cause
A reversal after a payout is the third cause because the reversal changes the wallet balance. The wallet places a hold on the next payout until the reversal is settled. The hold is not a complaint; the hold is a structural response to the reversal.
Why the three causes matter
The three causes are the three things a reader can fix. Name mismatch is the first. Back-dated document is the second. Blurry upload is the third. A hold that names none of the three is the wrong kind of hold; the reader should pause after the second retry and use in-product care.
The fix is a one-time change, not a three-time repeat.
Why the three causes
The three causes are the three things a reader can fix. Name mismatch is the first. Back-dated document is the second. Blurry upload is the third. A hold that names none of the three is the wrong kind of hold; the reader should pause after the second retry and use in-product care.
Why the discipline matters
Two identical retries usually fail a third time. The fix is not a third retry. The fix is a different file, a different name, or a different date. The fix is a one-time change, not a three-time repeat. The fix is the method.