On this page
An award can be approved while no card has been issued. A card can exist while the recipient has not received the intended delivery message. Funding can be available while a purchase still lacks a required eligibility finding. Calling all three situations complete makes operational records difficult to trust.
A useful lifecycle map names the business event behind each award state and keeps card and money status alongside it as separate information. The objective is to show what the team may do next, not to describe every issuer state or build a bank ledger.
Name the business event behind each award state
Start with the decisions the merchant needs to understand. Has a candidate purchase been identified? Have the campaign conditions been evaluated? Has an authorized person approved release? Has the provider confirmed the requested outcome? Has the recipient delivery obligation been completed under the program?
RebateCardX’s public platform positioning describes an approval-to-reconciliation journey subject to program and provider terms. The state names below are an original illustrative model; they are not a claim that an account uses these exact fields or that every transition is automatic.
Imagine award AW-301 linked to qualifying Shopify order O-2401. The operational team uses the following map to describe its business progress.
| Award state | Business fact established | Prerequisite for the next transition | Responsible owner | Permitted next action |
|---|---|---|---|---|
| Candidate | A purchase has entered review | Required purchase evidence | Eligibility team | Evaluate the disclosed conditions |
| Qualification pending | A specific purchase fact remains unresolved | Named evidence or interpretation | Assigned evidence owner | Resolve the missing condition |
| Qualified | Campaign purchase conditions are supported | Release prerequisites and authorized decision | Award approver | Approve or hold release |
| Approved | Release is authorized for the current case | Current readiness and permitted provider handoff | Award operations | Submit through the approved process |
| Handoff unresolved | A request exists without a confirmed outcome | Authoritative provider result | Provider operations owner | Resolve outcome before repeating value creation |
| Issued, delivery pending | Issuance confirmed; recipient delivery incomplete | Correct delivery outcome | Recipient operations | Complete delivery against the existing award |
| Completed | Defined award obligation completed | Any later event requiring a separate review | Program owner | Retain the completion evidence |
A separate closed-ineligible outcome can end a candidate that fails a published condition. An approved cancellation can end a pre-issuance case when the program permits it. These are business outcomes with reasons, not generic error bins for every unresolved event.
Separate award, card and money status
For AW-301, suppose the award is Approved, the provider has no confirmed issued card reference, and funding readiness is confirmed for the intended release. The team may proceed with the permitted handoff. It should not tell the recipient that a card already exists merely because the award is approved.
Now suppose the provider confirms issuance but the delivery message fails. The award’s next task is delivery resolution. The card record may already be active under provider terminology, and the corresponding value may already have been committed. Creating another award to make the delivery status green can duplicate value without solving the original communication issue.
Finally, suppose funding is available but eligibility remains pending because a required return outcome is unresolved. Available money does not satisfy the missing purchase condition. A funding dashboard should not function as a shortcut around the qualification decision.
Represent these dimensions explicitly in a working case: award state, provider card reference and reported status, and funding reference or readiness finding. The actual provider defines its own card states and permitted actions. Do not translate a familiar label into a guarantee that a recipient can use a card in every context.
The relationships should be traceable even when there is no card yet. AW-301 remains the award reference from qualification through issuance and delivery. A later provider reference attaches to that business case; it does not replace the original purchase relationship.
Assign the permitted next action
Every nonterminal state should answer three questions: what fact is missing, who can establish it, and what action is allowed now. “Pending” without those answers tells an operator almost nothing. “Handoff unresolved; provider outcome required; no duplicate submission until reconciled” is an operational instruction tied to a real uncertainty.
A filled snapshot might read: “AW-301 is issued with recipient delivery pending. Provider issuance reference PR-902 is confirmed. Delivery attempt DL-11 failed. Recipient operations will correct the permitted delivery issue using the existing issued record. This case does not authorize another funded award.”
A difficult case is a return arriving between approval and provider confirmation. The lifecycle map should direct the team to establish whether issuance occurred and which action is still permitted. It should not jump directly from Approved to Canceled when the handoff may already have created an issued reward.
Another difficult case is a provider status update arriving late. Preserve the business sequence and the authoritative event evidence. A late message about an earlier stage should not automatically move a completed award backward or erase a later confirmed outcome. The operational review needs to understand what the event means for the actual case.
Define completion according to the program’s obligation. It might require a confirmed delivery or another agreed outcome. Do not call the award complete solely because an internal job finished successfully. A completed software task and a completed customer obligation are different facts.
The finished map gives each award an understandable path, distinct from the card’s status and the money’s state. It shows where work remains, who owns it, and what actions are permitted without allowing approval, issuance, delivery, and funding to collapse into one misleading status.
Discuss the award states your team needs to manage from purchase through completion.
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.