One identity file is being used for several verification requests

Organize the list by requirement, not by uploaded file

Start with the account's current request list and create a separate entry for each item. Record the subject, the purpose and the requested evidence. The subject identifies whose information is being checked; the purpose identifies what the provider needs to establish. Two requests referring to the same person can still be separate requirements.

Now connect each submission to the item it was intended to answer. A folder containing one clear identity scan does not describe the whole request list. Nor does a count of uploaded files tell you which requirements remain. The useful record is the association between a requirement, a submission and the provider's response to that submission.

Readable evidence can still be wrong for the purpose

Stripe's common document rules include readable, complete, unexpired records and relevant reverse-side information. Those conditions concern the document's acceptability as a file. They do not make an identity document evidence for every other requested purpose. Stripe separately states that an identity document cannot simultaneously satisfy multiple document requirements.

Compare the document category named in each request with the record submitted for it. Even if the file visibly contains information relevant to another item, that does not establish that Stripe permits it to satisfy both. Do not turn a visible address, a name or another field into an assumed alternative-document rule.

Renaming a file, making another copy or uploading the same image into a second slot does not change its purpose or create independent evidence. If the requirement is unclear, ask the provider which evidence belongs to that item. This page does not prescribe a replacement document or a universal number of documents. Country-specific instructions and the actual request determine what is needed.

Read each response before deciding what to correct

For each item, distinguish not yet submitted, submitted with no decision recorded, rejected with a stated reason and confirmed as satisfied. Use the provider's own status text where available. If the response names only one requirement, apply it only there. A confirmation that the upload arrived is not the same as a response accepting the evidence.

Stripe says the Dashboard rejection reason guides the correction. Read that reason before taking a new photograph or replacing a file. A completeness problem requires a different response from using the wrong evidence for the purpose. If another requirement remains open after one is satisfied, read that remaining item on its own terms instead of repeating the earlier upload.

When a requested document is unknown or unavailable, Stripe directs you to support. Ask which evidence it will accept for the named open purpose, referring to the actual request and rejection reason. Keep the item unresolved while that answer is missing. Do not close it internally merely because the rest of the list is complete.

Maintain a status map without copying identity records

Keep document-type descriptions and private file pointers in the map. The original file stays in the business's authorized storage and goes only through the provider's specified channel. Stripe accepts verification documents through its Dashboard and says not to email them. The worksheet needs neither the document image nor its identifier value to show which purpose remains open.

Before handing the task to another authorized person, list the still-open items, the last response on each and the next supported action. That handoff can distinguish a required correction from a support answer still awaited. It avoids reporting the whole account as verified because a single item was accepted.

For a Prism processing consultation, describe the request categories and the remaining question without attaching identity records. A consultation can organize the business's processing question within an agreed scope; responsibilities, fees and terms are confirmed before work. Only the provider decides whether evidence satisfies its requirements, and document acceptance does not itself establish eligibility for research-only processing.

Verification-purpose evidence map

Repeat this map for each separate requested purpose. Keep the provider's wording and status for that item, even if another requirement is complete. Use document types and private record pointers only; do not enter identity numbers, document images or full addresses. An unanswered requirement stays open.

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.

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.