A required file attachment conflicts with express checkout

Identify what the field actually collects

Write down why the attachment is required and who requires it: a documented merchant procedure, a provider request, or another applicable requirement. Record when it must be received and who evaluates it. A required setting in a plugin does not explain the business purpose, and receiving a file does not prove its contents were reviewed.

Next identify the extension that creates the upload control, its installed version, the field type and whether it belongs to the product page or checkout. A text field holding a filename or a link is not evidence that the original attachment was collected. Do not replace the upload with an ordinary text answer unless the responsible owner has confirmed that the revised collection method satisfies the real requirement.

Separate upload compatibility from missing-field validation

WooCommerce’s Stripe express-checkout documentation lists file-upload fields in its compatibility exclusions: these are among the cases where express methods will not be shown. A missing button in such a configuration therefore has a documented compatibility question to investigate before anyone assumes an account restriction or a wallet outage.

The same document describes additional checkout fields separately. Supported values entered on the checkout page can be saved; the documented product and cart express paths do not display those additional fields and can send them empty. Required-field checks can then stop the payment after wallet-sheet approval. That describes collection and validation of those fields. It does not remove the separate file-upload limitation.

Moving an express button to the checkout page is therefore not sufficient evidence that an upload will work. Match the upload extension’s documentation or written vendor confirmation to the checkout type, version and entry point in use. Record both what is supported and what remains unconfirmed. Do not generalize this Stripe extension limitation to every wallet integration.

Choose a supported collection point without losing the control

First assess the ordinary checkout route that currently owns the upload. It is a candidate only if the installed upload extension supports that route and the stored record can be retrieved by the authorized reviewer. Record where receipt is recorded, which order or account it belongs to, and what prevents the workflow from passing the required stage without it. A visible upload button alone does not establish those behaviors.

A separate collection step can be considered only when the requirement owner permits that timing and the responsible maintainer confirms the complete handoff. Define the destination, the record used to link the file, the reviewer and the action held until review. Do not assume that collection after payment is acceptable when the real requirement must be satisfied before payment or order acceptance.

If no supported route is established, leave the affected express path unavailable rather than suppressing a required check. The next decision is to resolve that particular compatibility gap with the extension owner. Do not add a code workaround that merely discards required-field handling, nor force a button to appear as evidence that attachment collection works.

Record enough evidence to approve the workflow

Use the worksheet to make one decision for each affected entry point. Compare the documented behavior with the actual field settings and existing authorized order records. Distinguish file selected, file received, file linked to the correct record, and file reviewed. Mark any stage you cannot establish as unverified; do not create a fictional attachment or order to fill the gap.

For a Prism checkout-review consultation, describe the website, research-only products, upload extension, checkout type and affected button location. Summarize the document purpose without sending the document, customer records or credentials through the public form. Prism confirms the requested review or implementation scope, responsibilities, fees and terms before work. The inquiry receives email follow-up; it does not purchase a change or submit a processing application.

Attachment collection decision

Use one sheet per required attachment and repeat the entry-point row for each real path under review. A route remains unverified until evidence covers collection, linkage and the required decision stage. Record document types and non-sensitive references, never the attachment contents.

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.