Reconcile conflicting refund promises in one owned case
Preserve each agent’s actual message, including time, channel, promised amount and any stated condition or date. Match both messages to the same order and the actual provider refund records. A promise to refund, an internal note and a provider refund status establish different facts. Put the conflict under one authorized case owner before anyone makes another payment action or commitment. The owner should identify what can be confirmed, which earlier statement needs correction and what decision is still open.
For: A research-only merchant’s support lead handling contradictory refund messages about the same order.
Preserve both commitments before choosing an answer
Retrieve each original message from the authorized support record. Separate what the agent promised from what the customer requested and what another staff member later summarized. Record the message time and time zone, channel, author, affected order and exact promise in the restricted case. The worksheet should hold references and a limited summary, not copied customer correspondence.
Compare amount and currency, scope of the promised refund, any condition and any promised action or arrival date. Identify the precise conflict: different amounts, different conditions, incompatible dates, or one statement that an action already happened while another says it is still awaiting a decision. Do not flatten those differences into a single entry saying refund agreed.
A later message may clarify an earlier one, but its timestamp alone does not establish that the buyer was told the earlier commitment no longer applied. Preserve any clarification actually sent and record whether the conflict remains. Deciding which commitment should be honored is a separate authorized decision; deleting the inconvenient message does not reconcile it.
Match the promises to the provider’s actual refund record
Identify the original payment in the account that processed the order, then inspect the refund records associated with it. Record each existing refund’s reference, amount, currency, observed status and observation time. Do not treat a support message saying done as a substitute for opening that record. Likewise, a store note can record an agent’s intention without establishing the provider’s result.
For Stripe, the Refund object’s documented statuses are pending, requires_action, succeeded, failed and canceled. Preserve the exact observed status. Pending or requires_action should not be rewritten as succeeded to make a promise appear fulfilled; failed and canceled should remain visible in the case. Where a reason or next action is not documented in the actual record, mark it unknown rather than infer it from the status word.
If multiple refund records exist, keep them separate and account for their individual amounts and statuses before considering another action. If no matching record was found, state which payment, account and time range were checked. That is more precise than claiming no refund exists anywhere. An unresolved match is a reason to finish the reconciliation before an additional payment action, not a reason to submit another refund to see what happens.
Give the conflict one decision owner and one communication record
Name a person authorized to decide the merchant’s response and identify who is authorized to perform any provider action. The case owner should bring together the commitments, the actual payment record, relevant order policy and any unresolved condition. Establish a next internal decision or update time. That is a team commitment to follow up, not a new promise that money will reach the buyer by then.
The next customer communication should acknowledge the conflicting information, state the provider result that was actually checked and identify what remains under review. When an earlier claim was inaccurate, describe the correction directly instead of merely replacing one status word with another. Keep any new remedy or payment action tied to the owner’s recorded authorization.
WooCommerce distinguishes system, private and customer order notes; customer notes are emailed. Choose the note type deliberately when recording internal deliberation or communicating the resolved position. Do not put internal discussion into a customer note on the assumption that writing from admin makes it private. Preserve the customer-facing correction as its own message, linked to the two original commitments.
Close the contradiction separately from the financial outcome
The communication conflict is reconciled when both original promises are accounted for, the authorized decision explains the difference and the corrected position has a recorded communication. The refund may still have an unresolved provider status. Keep that financial follow-up open with its own owner rather than marking everything complete because support has agreed on wording.
If the provider status later changes, append the new observation and assess whether the customer needs an update. Do not use a status to invent the reason an agent was wrong or a date for the buyer’s bank record. This process organizes operational evidence; it does not decide the legal effect of a promise or determine an unseen merchant’s refund obligation.
For a Prism checkout-review consultation, describe the website, research-only products and the workflow that allowed contradictory commitments. Keep original messages, customer records and payment details out of the public form. Prism’s published support includes storefront review, processing preparation and help with provider website questions; confirm the requested support-workflow scope, responsibilities, fees and terms before work. Follow-up is by email, and an inquiry does not book an appointment, purchase a service or submit a processing application.
Commitment reconciliation
Use the message rows once for each genuine commitment and retain the originals in the authorized case. Complete the provider comparison before authorizing another action. A resolved communication conflict and a completed refund are separate findings; keep an owner for either one that remains open.
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.
Commitment reconciliation. The last column is for temporary notes.
Case element
Evidence to preserve
Reconciliation decision
Your finding
Message reference
Evidence to preserveInternal reference, author, channel, timestamp and time zone for each original message.
Reconciliation decisionWhether both statements concern the same order and have been read in their original context.
Promise made
Evidence to preserveRestricted original wording, summarized here by amount/currency, condition, scope and stated date.
Reconciliation decisionWhich promise is about an intended action, an action claimed complete or an expected arrival.
Buyer-facing clarification
Evidence to preserveAny actual later message that addresses the earlier commitment.
Reconciliation decisionWhether a correction was communicated or only discussed internally.
Actual refund record
Evidence to preserveOriginal-payment match and each provider refund’s reference, amount, currency, status and observation time.
Reconciliation decisionWhich portion of a commitment has a matching provider record and which does not.
Outstanding conflict
Evidence to preserveThe exact mismatch between the promises or between a promise and the provider evidence.
Reconciliation decisionThe question the case owner must decide; retain unsupported reasons as unknown.
Authorized case owner
Evidence to preserveNamed decision owner, authorized payment operator and next internal update time.
Reconciliation decisionWho may decide, who may act and who will stop conflicting instructions from continuing.
Correction and note visibility
Evidence to preserveApproved customer wording and actual channel or WooCommerce note type.
Reconciliation decisionCustomer notes are emailed; confirm the intended audience before saving the correction or internal discussion.
Action and remaining follow-up
Evidence to preserveReference for any authorized action, its observed result and the next unresolved task.
Reconciliation decisionClose the messaging conflict separately from a provider outcome that is still pending or otherwise unresolved.
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’s status names describe Stripe Refund objects. Another provider’s status must be read using its own record and documentation.
This reconciliation does not decide legal obligations, promise bank-arrival timing or authorize a further refund.
Keep full customer messages, card data, authentication codes, credentials, bank details and private payment links out of the worksheet and public consultation form.
WooCommerce order page — checked 2026-09-21. Distinguishes system, private and customer order notes and states that customer notes are emailed. This supports choosing the audience deliberately when recording a correction.
Stripe Refund object — checked 2026-09-21. Documents the refund statuses pending, requires_action, succeeded, failed and canceled. The list does not establish the cause or result of this merchant’s particular case.
Prism solutions — checked 2026-09-21. Published support includes storefront review, processing preparation and provider website questions, with scope, fees and terms discussed before work.
Prism contact — checked 2026-09-21. Requests website, products and question without card details, passwords or customer records. Follow-up is by email; a request is not an appointment, purchase or processing application.
Get help with store operations
Need help with the order, email or fulfillment step itself?