Stripe verification rejected a screenshot. How to choose a direct scan or photo

· 3 min read

Stripe distinguishes a direct scan of an original document from a screenshot, an edited picture or an image embedded in a substitute file. If verification has rejected the previous submission, check the rejection reason before doing anything to the file. The Stripe document guide says copies and scans should be in PDF and taken directly from the original. A photo of a physical document should be the original, unprocessed JPEG or PNG. Turning a screenshot into a PDF changes the container while leaving the source of the image unchanged.

Match the file to the rejection reason

Open the verification request and note which document category it covers. The country document guide separates identity, address, entity, bank account and other evidence categories. If the error concerns an expired identity document, supplying a more legible image of the same expired document will not resolve it. If the reason is an incomplete scan, start again from the original so the next file shows the complete record. The guide distinguishes a missing side, a name mismatch, an unsuitable format and poor image quality. One problem can coexist with another.

For a photo ID, check that the color photo or scan shows all the borders and any required reverse-side information. For scans of paper records that are not photo IDs, Stripe's guide allows black-and-white scans, while photos of paper documents are required to be in color. Confirm that any additional pages with relevant fields are included. Do not crop away a page edge to make the text larger. Review the output directly at a readable size so you can see whether the name, number, expiration or address survived the scan clearly.

Keep document choice and upload mechanics separate

Say an operator received a photo of a document pasted into a message. They can read the business name, but the image lacks the corners of the page and an entire supporting page. Saving that image as a PDF is not the same as creating a new scan of the original document. Retrieve the original first or ask the authorized party to provide an eligible original image. Make the replacement file from that version and confirm its content before uploading.

If you tell a person to send both identity and address evidence, remember that Stripe’s common requirements say a single document cannot fulfill both requests at once. Organize the checklist by requirement, with a separate file for each as applicable. A file matching the required format still has to show the expected name and other details. Check account details against the evidence without editing the evidence itself. Only correct an account value when it is genuinely wrong.

Recheck the outcome in the applicable channel

For a dashboard request, Stripe directs users to the appropriate upload in Settings under Account status and says not to send the document by email. An integration responsible for collecting requirements can review the API error associated with the affected requirement and follow Stripe's documented upload flow. In either case, track whether the next status is accepted, pending review or asking for more evidence. Ask for another file only when the status gives you a reason to do so. That reduces repeated sharing of sensitive material and helps preserve a clear record of which submission answered each request.

Official sources

  1. Acceptable verification documents by country
  2. Handle verification with the API