A receipt link can expire while the payment record remains

Separate the old link from the payment it pointed to

Stripe creates receipts for successful payments and refunds. Its receipt links expire after 30 days. The expiry concerns access through that link, so a customer’s inability to open it is not a new payment outcome. Record the original receipt date if known and the exact access message the customer reports. If the page reports something other than expiry, preserve that distinction rather than diagnosing every broken link as the same problem.

Email is a separate fact. Stripe emails successful-payment receipts when enabled or when sent manually; failed or declined payments do not get a receipt email. A message in an inbox, a store order confirmation and the current provider payment record answer different questions. For this request, the goal is to recover access to the correct existing receipt, not to change the order or take payment again.

Find the original payment without asking for card data

Use the order reference and the payment reference already recorded in your authorized systems. Compare the order’s date, amount and currency with the provider entry, retaining the account context if the business has changed providers. An amount or customer name alone is insufficient when several records could match. Keep the request unresolved until the order-to-payment association is clear.

Check whether the customer needs the original purchase receipt or a later refund receipt. Those can concern the same order while representing different events. Record which event you located and whether the provider offers its receipt. Do not substitute an unrelated successful payment when the expected receipt is absent.

PCI SSC’s FAQ prohibits sending unprotected primary account numbers through email, instant messaging, SMS or chat. An old-receipt search is not a reason to request a full card number or security code. Use existing order records and your established customer-verification process instead; do not ask the customer to disclose payment credentials in the support conversation.

Verify the recipient before releasing the document

Confirm the requester’s authority to receive the order’s payment record through your existing support controls. A person who knows an order number has supplied a search clue, not necessarily authority to receive its receipt. A request to send the document to a new address needs its own verification; do not silently replace the recorded recipient because the new message asks you to.

Once the payment and recipient are established, use the provider’s receipt route available to the authorized account user. Stripe documents manual sending from successful payments or refunds. Check the selected payment and recipient before sending, then record that action. Keep receipt-access URLs within the intended customer exchange and authorized systems; do not paste them into a shared worksheet or public consultation form.

If the old provider account is inaccessible, record that access limitation and identify the business owner who can seek authorized access. If the account opens but no appropriate receipt option is available, ask that provider about the specific payment. Do not reconstruct an official provider receipt from memory or promise that historical access can always be restored.

Close the request with the action actually taken

Tell the customer whether you located the payment, whether you sent a receipt using the provider’s available route, or which access issue remains open. A recorded send is evidence of that action; it is not proof that the customer received or opened the message. Name a support owner for any follow-up without promising a provider recovery time.

For recurring receipt-access or store-message problems, a Prism checkout-review consultation can start with the platform, provider, receipt age and observed link state. Keep the receipt itself, customer details and private access links out of the public inquiry. Confirm scope, responsibilities, fees and terms before any work. Receipt access does not establish processing eligibility or authorize account changes.

Receipt request record

Use one sheet for one real request. Keep full references and recipient details in the authorized support system; enter restricted record locations and verification results here. Send only when the order, payment event and recipient have all been matched. Otherwise record the precise unresolved step.

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.