An early warning is not a formal chargeback

Classify the notice from the provider’s current record

Preserve the type, date and wording of the actual event. An email subject or an internal note saying fraud is not enough to identify the provider’s process. Match the notification to the relevant payment in the account and record the status visible there now. Keep the time of that check separate from the time the original notification arrived.

Stripe’s dispute documentation treats an early fraud warning as different from an inquiry or formal dispute. A formal dispute begins when the account owner contests a payment through their bank. Stripe describes the disputed amount and a dispute fee being debited for that process. Do not attribute those formal-dispute consequences to a warning merely because the notice concerns fraud.

An earlier warning does not establish the current case state. Check for a later inquiry or formal dispute on the same payment. Retain both events if they exist, with their dates, instead of renaming the earlier notification. For another provider or payment method, use its actual event labels and instructions rather than importing Stripe’s terminology.

Match the payment before choosing an order action

Use the payment reference to connect the notice with the correct store order in the business’s private records. Confirm the payment method, the original amount and currency, and any current refund or dispute entry. If an order has more than one payment attempt, an order number alone is not enough to identify the affected payment.

For a formal Stripe dispute, the disputed amount can differ from the original charge. Keep those amounts separate when reconciling a later case with the warning. A difference does not, by itself, mean that the notice belongs to the wrong order.

This classification changes which action is available. Stripe says a refund cannot be issued outside the dispute process while a dispute is open. Do not decide to refund from an old warning email without checking the current payment state. If only a warning is present, that fact alone still does not choose a refund, cancellation or fulfillment action for the merchant; the authorized owner needs the provider instruction and the actual order facts.

Read fulfillment separately from the payment status

Find out what can still happen to the order. Record whether fulfillment has not started, is in progress, is on hold, is partial or has completed, using the store’s own status definitions and available fulfillment records. Also identify who controls the remaining fulfillment work. A provider notice does not establish that a warehouse has stopped a shipment.

Shopify documents payment and fulfillment statuses as separate. Paid, Authorized and Payment pending describe payment; they do not say whether goods have shipped. Its fulfillment statuses include Unfulfilled, In progress, On hold, Partially fulfilled and Fulfilled. A fulfillment on hold cannot be fulfilled until it is released.

For a Shopify order already on hold, establish the reason and authorized release owner before treating the order as ready to fulfill. For a partially fulfilled order, distinguish work already completed from the remaining items. Do not mark an entire order unshipped simply because some work can still be stopped. These Shopify definitions do not describe every platform, and they do not establish an automatic connection between a provider warning and a store hold.

Assign a response without making an accusation

Give the authorized owner the classified event, matched payment, current fulfillment state and provider instruction. Record any actual response deadline shown; do not borrow a formal-dispute deadline for a warning. If the notice and current account record disagree or the instructions are unclear, name that exact uncertainty before an irreversible action is authorized.

Keep the decision and its execution separate. Record what the owner authorized, who may perform it and which provider or store record will show the result. A request to hold fulfillment is not a confirmed hold; a refund instruction is not a completed refund. Preserve the resulting status and time in the internal order record.

Describe the event neutrally in support notes. Record that the provider issued an early warning and that review is underway when that is what the records show. Do not convert the notice into a claim that the buyer committed fraud or that a bank has already decided a dispute.

If the gap concerns the store-to-provider handoff, a Prism checkout-review consultation can start with an anonymized description of the event and mismatched statuses. Scope, responsibilities, fees and terms are confirmed before work. A consultation request does not authorize a refund, a fulfillment release or dispute handling, and it does not assume ownership of an active deadline.

Warning event record

Use one record for the actual notice, then compare it with the current payment and order states. Keep exact payment references and customer records in the business’s private systems; enter only an anonymized label, match findings and status descriptions here. A warning with no formal dispute, an inquiry and an open dispute require different instructions, so do not merge their rows into a single risk label.

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.