On this page

A $20 reward does not necessarily cost the merchant exactly $20 to deliver. The program may include fixed charges and fees triggered by specific events. A cost model that multiplies face value by recipients and stops there can miss those charges or apply them to the wrong count.

The useful question is not simply “what is the fee per card?” It is which event creates each charge, how often that event occurs and which denominator the merchant uses when reporting unit cost.

Separate customer reward value from program charges

Use a fictional schedule solely to demonstrate the method. Assume a $200 setup charge, a $100 campaign-period service charge, $0.60 for each issued reward instrument and $3 for each documented exception event of the specified type. None of these figures is a RebateCardX price or a market quote.

The campaign issues 500 instruments with $20 of face value each. Of those, 480 reach the model’s defined successful-delivery point within the reporting window. Ten chargeable exception events occur. The distinction between issued and delivered is part of this example’s model; the actual provider must define its own events and billing terms.

The reward face value funded for the 500 issued instruments is $10,000. Do not reduce that figure to $9,600 merely because only 480 meet the chosen delivery definition during the window, unless the actual arrangement establishes a corresponding release or avoided funding obligation. An incomplete delivery outcome does not automatically reverse issued value.

The RebateCardX terms and regulatory disclosures provide context for a program discussion. Obtain the actual commercial schedule before applying any real fee assumptions. Public product descriptions should not be used to invent specific charge events.

Map each charge to its event and frequency

Build the fee-event table from the documented or explicitly hypothetical schedule.

Cost component Event or basis in this fictional schedule Event count Unit amount Modeled cost
Reward face value Each issued instrument funded at the stated amount 500 $20 $10,000
Setup charge One campaign setup 1 $200 $200
Period service charge One defined service period 1 $100 $100
Issuance charge Each issued instrument 500 $0.60 $300
Specified exception charge Each documented chargeable exception event 10 $3 $30
Total - - - $10,630

The table keeps frequency separate from unit price. A $3 exception fee charged ten times costs $30; it should not be multiplied by all 500 instruments unless the schedule actually says every instrument triggers it. Likewise, the setup charge is incurred once, not once per recipient.

The $630 above face value consists of $200 setup, $100 period service, $300 issuance and $30 exceptions. This is 6.3% of the $10,000 face-value funding in the example. That ratio is descriptive of this scenario, not a general markup for reward programs.

A difficult case is a charge described as applying per request. If one intended reward requires two requests because of a documented retry event, the billable count may differ from the number of ultimately issued instruments. The merchant needs the actual event definition before assuming one customer always equals one charge.

Another case is an exception included in a service package rather than separately billed. The model should not add a hypothetical charge simply because the event exists operationally. Include fees only when the actual schedule or clearly labeled scenario defines them, and keep unknown items unresolved rather than pretending they are either free or chargeable.

Calculate cost per delivered reward under stated assumptions

Divide the total by the chosen outcome count. In the fictional schedule, $10,630 divided by 480 successfully delivered rewards equals approximately $22.15 per delivered reward. Dividing by 500 issued instruments instead gives $21.26 per issued instrument.

Both unit costs are mathematically valid, but they answer different questions. The first allocates the campaign’s modeled cost across the completed delivery outcome. The second allocates it across issuance events. Label the denominator so reviewers do not compare the two as though one were an arithmetic error.

A useful third measure is non-face-value cost per issued instrument: $630 divided by 500 equals $1.26. This shows the modeled delivery overhead without combining it with the $20 customer benefit. It can help the merchant see how fixed and event-based charges contribute to the total.

Do not interpret the $22.15 figure as the face value the customer receives. The customer benefit remains $20 in this example. The additional amount is the merchant’s modeled cost allocation, including costs associated with events that did not meet the defined delivery outcome during the window.

If the 20 pending deliveries later complete without additional cost, the same $10,630 spread across 500 delivered rewards becomes $21.26. That change reflects the denominator and timing window, not necessarily a provider price change. The model should state its outcome definition and observation period alongside the unit cost.

For the fictional campaign, the decision record could read: “Modeled cost is $10,630 for 500 issued $20 instruments, including the specified fixed and event charges. At 480 completed deliveries in the chosen window, cost per delivered reward is about $22.15. Validate the event definitions and actual schedule before approval.”

The practical output is a fee-event model that traces every dollar to a defined trigger. It prevents face value, issuance counts, successful delivery and exception frequency from being combined into an unexplained single price.

Discuss the complete cost assumptions behind your proposed reward delivery model. Discuss program fit.

Source references

Back to contents

General information only

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.