Verification fails because the document is incomplete or unreadable
Start with the rejection in the provider’s account and the exact file submitted. Compare that file with the requested document type and the requirements for originality, legibility, complete content, expiry, and relevant reverse-side information. Correct the named defect using an acceptable original or a fresh complete scan or photograph, rather than editing the document’s facts or repeatedly submitting the same deficient file. Stripe verification documents go through the Dashboard, not email or Prism’s inquiry form. If the reason is unclear or the required document is unavailable, ask Stripe support which correction or alternative it will accept.
For: An authorized representative of a research-only business whose genuine verification document was rejected for a file-quality or completeness problem.
Match the rejection to the file that was actually sent
Open the outstanding requirement and its rejection reason in the provider’s account. Record the document category, relevant country, and the wording of the problem without copying personal identifiers. Locate the exact submitted file in your authorized records. Inspect that version: the clear original on your desk does not establish that the file uploaded was complete or readable.
Decide whether the rejection actually concerns image quality or completeness. A blurred field, missing content, expired document, and wrong document type call for different corrections. A mismatch between the account information and the document is also a different issue; making the image clearer will not resolve inconsistent names. Keep the provider’s stated reason distinct from your own suspicion.
Stripe’s acceptable-verification-documents guidance makes country and document purpose relevant. Its common requirements are a starting point, but they do not make every genuine document acceptable for every request. Use the instructions for the account and request in front of you, rather than reuse a document just because it was accepted for a different purpose.
Restore readability and completeness from the original
Stripe distinguishes original scans or photographs from screenshots or processed files. When the submitted copy is a screenshot or otherwise unsuitable derivative, return to the acceptable original source. For a paper document, a fresh scan or photograph can address capture problems without changing what the document says. For an original digital document, preserve the original file when it is the format the request accepts instead of substituting a screen capture.
Inspect the proposed replacement at a size where the text can actually be read. Check the area named in the rejection, then the rest of the required content for blur, glare, shadow, or cropping. Capture the full document and every page the request requires. A replacement that repairs one unreadable field but cuts off another part remains incomplete.
Do not reconstruct text, change dates, paste in a missing section, or combine parts from different documents to make a cleaner-looking record. The correction is a faithful complete file of the genuine document. If the original itself is damaged or missing necessary content, a better photograph cannot supply that content; resolve the document problem with the issuer or ask the provider what it will accept.
Check validity and reverse-side content separately
Stripe’s common rules require unexpired documents and relevant information from the reverse side. Check an expiry date where the document has one, and follow the validity requirements for that document category. A sharper image does not make an expired document current. Do not invent an expiry date for a document that does not state one; use the provider’s requirements for that type.
Inspect the reverse side instead of assuming the front contains everything. Where relevant information is on the back, include it in the manner the request specifies. Also check whether the requested document is complete across its required pages. The number of files and the upload arrangement should follow the actual instructions, not a guessed rule that one image is always enough.
Keep file quality separate from documentary meaning. A readable, complete file can still be the wrong evidence for the request, and a legitimate identity document does not automatically satisfy several different requirements. If the provider asks for a different category, a replacement original, or clarification you cannot supply, record that need explicitly. Do not keep improving the appearance of a file that cannot answer the stated request.
Resubmit a specific correction and preserve the outcome
Before submitting, compare the replacement with the rejection one last time: identify what changed and why that change addresses the stated defect. Record the document type, correction, submission date, and a private file reference. The worksheet needs that index, not the document image, identifier, or sensitive file link. Preserve the original evidence according to the business’s authorized record-handling process.
Upload Stripe verification documents through the Stripe Dashboard. Stripe’s guidance says not to send these sensitive documents by email. Another provider must supply its own verified submission channel. After submission, keep the requirement’s actual status; a sent file is not an accepted file. If the same reason remains without a clear explanation, use the provider’s support process with the rejection and correction history instead of submitting unchanged copies again.
A Prism processing-preparation consultation can help organize the question. Describe the website, research-only products, document category, and non-sensitive rejection summary, without attaching identity documents. Scope, responsibilities, fees, and terms are discussed before work, with email follow-up to the inquiry. A request does not book an appointment, purchase a service, or submit a processing application. The provider decides whether the documents satisfy its request and separately whether it can support the business.
Document-quality correction record
Use this for one rejected requirement. Compare the exact submitted version with the proposed replacement inside your authorized records, then enter only non-sensitive findings here. Each correction must answer a stated defect. Missing evidence or an unclear reason remains open; uploading a file does not close it.
Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.
Document-quality correction record. The last column is for temporary notes.
Correction check
Where to inspect
Action the finding supports
Your finding
Rejection reason
Where to inspectThe outstanding requirement and exact rejection wording in the provider account.
Action the finding supportsIdentify quality, completeness, validity, or a different problem before changing the file.
Requested category and country
Where to inspectThe document instructions for this account and requirement.
Action the finding supportsConfirm that this document type can answer the request before preparing a clearer copy.
Original-file status
Where to inspectThe actual uploaded file compared with the acceptable original document or original digital file.
Action the finding supportsReplace an unsuitable screenshot or processed derivative with the accepted original, scan, or photograph.
Missing or unreadable area
Where to inspectThe named defect and the full required content of the replacement.
Action the finding supportsRecapture blur, glare, cropped content, or missing pages without altering the document’s information.
Expiry status
Where to inspectAny stated expiry and the provider’s validity requirements for this document type.
Action the finding supportsUse current acceptable evidence when required; better image quality does not renew a document.
Required reverse side
Where to inspectThe original back of the document and the request’s instructions.
Action the finding supportsInclude relevant reverse-side information in the specified upload arrangement.
Correction and submission
Where to inspectNon-sensitive reference to the replacement, the defect corrected, and the provider’s submission destination.
Action the finding supportsFor Stripe use the Dashboard, not email; record the date without copying the document here.
Provider outcome
Where to inspectThe requirement’s status or later rejection after the correction was submitted.
Action the finding supportsDistinguish submitted from accepted; ask for clarification when the remaining reason or required alternative is unknown.
These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.
Limits
Stripe document requirements depend on country and request. The source does not establish acceptance of translations or a universal alternative document.
Do not alter identity information, dates, or document content to obtain acceptance. A quality correction is not a change to the underlying facts.
Do not put identity documents, government identifiers, full bank details, card data, passwords, or customer records in worksheets, email to Prism, or the public consultation form.
A readable document, a successful upload, and accepted verification are different outcomes. None by itself establishes processing eligibility.
Stripe acceptable verification documents — checked 2026-09-29. Common rules distinguish original scans or photographs from screenshots and processed files, require readable complete unexpired documents and relevant reverse-side information, and vary by country and document purpose. The Dashboard rejection guides correction; unknown or unavailable documents go to Stripe support. Sensitive verification documents are uploaded through the Dashboard, not email. Translation acceptance was not established.
Prism solutions — checked 2026-09-21. Prism can help organize a processing question. Scope, fees, and terms are discussed before work; the provider decides document requirements, eligibility, and account terms.
Prism contact — checked 2026-09-21. The public inquiry asks for the website, products, and question and excludes payment-card details, passwords, and customer records. Follow-up is by email; the request is not an appointment, purchase, or processing application.
Discuss my processing options
Want to talk through your own processing situation?