On this page
A Shopify order passes through the reward approval process, then new payment-risk information arrives. The reward team now has two moving records: the original purchase review and the award’s current stage. Acting on an outdated award status can produce an instruction that the receiving team cannot perform or should not perform.
The immediate task is a precise handoff. Establish what the new information means, who owns the payment decision and what has actually happened to the award. A risk signal is a reason for review, not automatic proof that the purchase was unauthorized.
Confirm the source and meaning of the new risk information
Record the source, timestamp and exact operational meaning of the information. Is it an updated merchant risk assessment, a payment-provider notification or a customer report? Is the status preliminary, confirmed or awaiting investigation? Those distinctions determine the appropriate decision owner.
Shopify provides fraud-analysis information to support order review; it should be interpreted through the merchant’s authorized payment process. Shopify’s fraud-prevention guidance describes that review context. A reward operations team should not turn a signal into a different finding merely because it arrived after approval.
In a hypothetical case, order O-830 receives a new review notification at 11:20 UTC. Award AW-830 was approved at 10:00 UTC. The support screen still says “approved,” but the latest provider record has not yet been checked. The handoff must identify the current stage before requesting a specific action.
Preserve the original approval record. New information may justify a later decision under the applicable process, but it does not mean the earlier record should be overwritten as though it never existed. The timeline explains why the award progressed and when the new concern became available.
Locate the current award state
Check the controlling award and provider records at a stated cutoff. Distinguish approved unissued, issuance requested but outcome unknown, confirmed issued and any later provider-controlled state relevant to the case. An interface label alone may not establish whether value has moved.
| Confirmed award stage | Key question for handoff | Appropriate instruction boundary |
|---|---|---|
| Approved, not confirmed issued | What authorized action applies before the next award step? | Request decision from responsible program owner |
| Issuance requested, outcome unknown | Did issuance complete or remain unresolved? | Establish outcome before assuming a retry, stop or reversal |
| Confirmed issued | Which provider-controlled actions, if any, are permitted? | Request provider review; do not assume merchant control |
| Later adjustment already recorded | Does the new information change an existing case? | Connect to the existing decision and movement references |
The table is a handoff model, not a promise that a particular state can be paused or reversed. Actual available actions depend on the approved program and provider authority.
For AW-830, suppose the provider confirms issuance at 11:10 UTC, ten minutes before the new risk notification. The useful request is now a provider review of an issued reward in connection with payment case PR-830. An instruction to stop an unissued award would describe the wrong state and could delay the real review.
A difficult case occurs when the payment review later clears the purchase. The award handoff should preserve that update and identify any pending operational action that now needs reconsideration. If a temporary review status remains in the reward queue after the concern is resolved, the customer can be delayed for a reason that no longer applies.
Do not assume that confirmed card use changes the merchant’s authority. If the reward has been spent, the provider must still identify the permitted treatment. The merchant should not promise recovery of spent value or create an offset in another system without a separately authorized basis.
Coordinate the authorized response and later review
Send a compact handoff with four linked references: original order, payment review, award and provider case if one exists. Include the relevant timestamps, current confirmed stage and the precise decision requested. This gives each team enough context to act without receiving unnecessary customer or card information.
A sample request is: “Order O-830 has payment review PR-830 open following new information at 11:20 UTC. Award AW-830 was confirmed issued at 11:10 UTC. Please confirm the permitted provider response and the evidence required for the next decision. The payment finding remains preliminary.” That last sentence prevents an unresolved signal from becoming a reported fact.
Assign an owner to update the case when the payment decision changes. The owner should track both the decision and any resulting reward movement, because an acknowledgment of the handoff does not establish that an action occurred. If the provider takes no action, record that outcome and its reason rather than leaving the request indefinitely labeled “pending.”
Customer communication should follow the confirmed situation and the approved process. A recipient may need a factual delay or review notice, but the support team should not invent an allegation or promise an outcome. Keep the explanation specific to the current milestone and provide the appropriate route for relevant corrections.
After closure, review whether the timing gap exposed an operational weakness. Perhaps the award team lacked a clear way to identify an in-flight issuance outcome, or payment updates did not reach the correct owner. These are process findings to improve. They do not justify rewriting the historical record or treating all future risk signals as confirmed violations.
The completed handoff should show what was known at each point, who made each decision and which actions actually occurred. That sequence allows the merchant to coordinate a late-arriving concern while keeping the original purchase review and the reward’s financial state accurate.
Explore how changing purchase information can inform your existing award review process.
Source references
This guide is general information, not financial, legal, tax or regulatory advice. Eligibility, card availability, permitted use and responsibilities depend on the applicable offer and card terms.
