Verify an unfamiliar document request before sending records

Separate the email’s claims from the account’s request

Record the provider name, document type, stated purpose, deadline and case reference claimed in the message. These are details to compare, not evidence that authorizes an upload. First establish whether your actual provider made the request; selecting a suitable document comes later.

Open the account through your established sign-in route rather than a link in the message. Confirm that it is the account for the relevant business and service. Compare any outstanding request with the email. A genuine account request does not automatically validate a different attachment destination supplied by an outside message. The request and the channel both need to agree.

Resolve an absent or conflicting request

If the account contains no matching request, the email remains unverified. That absence does not by itself establish fraud or prove that no further information is needed. Reach support through the account or another route your business has already established. Ask whether the provider issued the named case, requested that document type for this account, and can identify its authorized submission instructions.

Keep the confirmation with the request record. If the case exists but its document list, deadline or destination differs, ask support to resolve that specific difference before sending files. A case reference helps match records; a number printed in an email does not prove that the sender controls the case. Do not disclose a secret or send a document as a way of asking the sender to prove who they are.

Follow the confirmed upload route

Stripe’s acceptable-verification-documents guidance says sensitive verification documents must be uploaded through the Dashboard and must not be emailed. When a purported Stripe request asks for an email attachment, confirm the requirement through the established account route and use the Dashboard for the documents. Another provider must identify its own authorized submission channel.

Stripe’s account setup guidance also directs teams to use limited-access invitations instead of sharing passwords and to keep secret API keys private. A document request does not justify disclosing either. After authenticity is established, follow the requirements for the actual document and country. Keep a receipt with the document type, date and destination; do not turn the authenticity record into a second collection of identity documents.

Record the outcome and scope any further help

Close this check when the provider, account request or verified support confirmation, case reference if issued, and authorized destination can be connected. Leave an unmatched item unresolved with the account owner. Confirming that a request is genuine does not establish that the document will be accepted or that processing will be approved.

For a research-only processing consultation, describe the website and unresolved request in ordinary language. Prism can discuss processing preparation and a provider’s website questions; confirm scope, responsibilities, fees and terms before work. The public inquiry is not a document upload channel. Follow-up is by email, and sending it does not book an appointment, purchase a service or submit a processing application.

Request authenticity check

Use one sheet for one actual message. Record document types and non-sensitive references only. An unmatched request or destination keeps submission unresolved; completing this sheet does not establish provider approval.

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.