Start with the existing unpaid order and choose one payment request whose result you can match back to it. A native WooCommerce order-payment link leads to payment for that store order. A Stripe Invoice is addressed to a specific customer; a reusable Stripe Payment Link can be used by anyone who has it. Provider-side collection needs an explicit connection to the store record unless your installed integration already makes one. Record the selected request, its amount and currency, the resulting provider payment, and the customer message separately. Sending a request does not establish that the order was paid.
For: An owner or order administrator of a research-only store collecting payment for an existing order entered by staff.
Open the manually created order and establish what remains payable before sending anything. Confirm the items, total, currency, customer assignment, and any earlier payment references. WooCommerce documents both checkout-created orders and orders added by staff in WP Admin. Manual creation tells you how the order entered the store; it does not identify how money will be collected.
For an existing WooCommerce order, the native order-payment route keeps the request attached to that order. The paying-for-orders guide documents payment flows for Draft and Pending payment orders. From the Edit order screen, Order actions > Send order details to customer sends payment instructions with an order-payment link. The order also exposes a Customer payment page link that can be shared with its intended customer. A registered customer can use the Pay action on unpaid orders assigned to them in My Account.
Check the provider record for any earlier attempt before replacing the request. Do not send several active collection routes for the same balance merely because an email was not received. Keep a dated record of which request is current and which earlier message it replaces. The store document describes one payment per order; it is not a basis for constructing a deposit or installment arrangement.
Customer assignment changes the payment-link instructions
An order assigned to a registered WooCommerce customer prompts that customer to sign in if they open the payment link while logged out. A guest order uses a different check: after the documented default ten-minute grace period from order creation, the visitor must verify the email address on that order. The grace period can be customized, so record the installed behavior when explaining an older link.
The same guide warns that a guest order without an email address can be paid by anyone with its payment link. Keep order-payment URLs inside the intended customer conversation. Do not remove the email address, change the customer assignment, or disable verification to make a link easier to open. If the assignment is wrong, an authorized store administrator should resolve that record accurately before another request is sent.
Tell the customer which access step belongs to their order without requesting passwords or authentication codes. Guest payment-page verification does not itself attach the order to a customer account. A complaint about sign-in is therefore a question about the order assignment and payment route, not evidence that the payment failed.
A provider invoice and a reusable link leave different records
Stripe describes an Invoice as a collection instrument for a specific customer that cannot be reused for another customer. Choose that pattern when the request needs its own customer-specific invoice record, subject to the payment arrangement actually available to the business. Keep the invoice reference and its eventual payment reference connected to the existing store order in the authorized systems.
A Stripe Payment Link can be used by anyone holding the link. Its reusable identity is not enough to identify which use paid this manual order. If this is the documented option you use, establish how the resulting individual payment will be associated with the order before sending the link. Matching only the amount or the fact that the buyer received a link leaves the association unresolved.
A provider-created invoice or link does not, by its existence, prove that WooCommerce received a payment update. Conversely, the phrase invoice in a WooCommerce order email does not mean a separate Stripe Invoice was created. Read the actual store and provider records to identify which product supplied each document.
Provider-side keyed entry is a separate channel to establish with that provider, not a fallback procedure supplied here. Use it only when the provider documents the facility and confirms that the business and channel may use it. Do not collect card details in order notes, email, or a worksheet while that question is unresolved.
Close the request with a three-record comparison
After payment, compare the existing store order with the individual provider payment and the message actually sent to the customer. In the restricted order record, retain the non-secret identifiers needed to find the payment again, along with amount, currency, status, and relevant timestamps. Check whether the integration updated the store and whether any manual reconciliation remains. Do not mark a request paid simply because the buyer opened it or received an invoice.
Stripe receipts follow successful payment; invoice receipts are sent after payment completes. Successful-payment receipt emails depend on the setting or a manual send. A missing receipt email therefore does not establish failure, and an invoice sent before payment does not establish success. The store order message and provider receipt should describe the same purchase without being treated as the same document.
If only the provider has the payment, assign the missing store association to the authorized integration or order owner. If the provider result is unknown, leave the balance unresolved and do not ask for another payment yet. For a Prism checkout-review consultation, summarize the request type and the missing association. Prism publishes storefront review, processing preparation, and help with provider website questions; agree the investigation, any implementation responsibilities, fees, and terms before work. Keep customer documents and private payment links out of the public inquiry. Follow-up is by email; the request does not book an appointment, purchase a service, or submit a processing application.
Manual-order payment record map
Complete this for one existing order. Record whether each association is confirmed, absent, or still unknown. Keep detailed payment references in your authorized systems; enter only non-sensitive record labels and findings here. A row is resolved only when the request can be traced to an individual payment and that payment to the order.
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.
Manual-order payment record map. The last column is for temporary notes.
Request or record
Evidence to compare
Decision the evidence permits
Your finding
Existing store order
Evidence to compareOrder total, currency, customer assignment, current status, and any earlier payment association.
Decision the evidence permitsIdentify the actual unpaid balance before choosing or replacing a request.
Native WooCommerce order-payment route
Evidence to compareOrder email or Customer payment page route, Draft or Pending payment status, and the gateway identified on the order.
Decision the evidence permitsUse the route for that existing order when its documented payment flow fits; verify the provider result afterwards.
Customer access step
Evidence to compareRegistered-account assignment or guest assignment, email presence, and the applicable verification behavior.
Decision the evidence permitsGive the correct sign-in or email-verification instructions without weakening the control.
Provider invoice for a specific customer
Evidence to compareThe provider invoice and its individual payment, compared with the store order.
Decision the evidence permitsA Stripe Invoice identifies a customer-specific request; confirm the store association separately.
Reusable payment link
Evidence to compareThe individual payment created by the link and the actual order association.
Decision the evidence permitsThe shared link alone does not identify which payment settled this order.
Provider-side keyed entry, if available
Evidence to compareThe provider documentation and written channel permission, plus the resulting payment record if this channel was actually used.
Decision the evidence permitsLeave unavailable or unconfirmed channels unused; do not record card data or invent an entry procedure.
Records held in only one system
Evidence to compareWhether a provider payment lacks a store association, or a store status lacks a verified provider result.
Decision the evidence permitsAssign the missing association to an authorized owner before another request or order-state change.
Customer message and receipt
Evidence to compareWhich request was sent, whether payment completed, and whether a receipt was generated or emailed.
Decision the evidence permitsDistinguish a request to pay from confirmation that payment succeeded.
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 product functionality does not establish eligibility for a research-only business or authorization for a new sales channel. Use the actual approved payment arrangement.
Native WooCommerce payment-link checks are distinct from reusable Stripe Payment Links. Do not bypass customer verification.
Keep card numbers, security codes, passwords, customer documents, and private payment or receipt URLs out of this worksheet and the public consultation form.
WooCommerce managing orders — checked 2026-09-21. WooCommerce orders can be created at checkout or added manually in WP Admin.
WooCommerce paying for orders: customer verification — checked 2026-09-29. Documents one payment per order, native payment routes for Draft and Pending payment orders, registered-customer sign-in, and guest email verification after a default ten-minute grace period. Guest orders without email lack that email check; payment-page verification does not link guest orders to an account.
Stripe Invoicing — checked 2026-09-21. An invoice collects from a specific customer and cannot be reused for another; a Payment Link is usable by anyone with the link.
Stripe receipts — checked 2026-09-21. Invoice receipts follow completed payment. Successful-payment receipt email depends on enabled settings or a manual send; failed or declined payments do not produce a receipt email.
Prism solutions — checked 2026-09-21. Public support includes storefront review, card-processing preparation, and help with provider website questions. Scope, fees, and terms are discussed before work. The provider decides eligibility and account terms.
Prism contact — checked 2026-09-21. The form asks for the website, products, and question and excludes card details, passwords, and customer records. Follow-up is by email; a request does not book an appointment, purchase a service, or submit a processing application.