Which Digital Receipts Count as Valid in DataDance Wallet?

 

If you have read our previous article, you already know that DataDance Wallet does not work by scanning receipt images. Instead, it reads the order history page you open and works directly with the structured data shown there.

For a full explanation of how this mechanism works, you can read the detailed overview here:

https://datadancewallet.blogspot.com/2026/02/you-dont-need-to-find-download-or-print.html

This design avoids many problems common in traditional receipt rewards apps. When rewards depend on scanned receipts, even a small issue, like image quality, missing fields, timing limits, can cause a receipt to be rejected. With digital receipt records, these issues do not exist. The order data is complete, standardized, and already verified at the source.

Does this mean that every receipt record in DataDance Wallet will always be accepted and earn points? Not always. In DataDance Wallet, a receipt record can still be marked as invalid under our eligibility rules, and invalid records do not earn points.

To explain this clearly, we use the current Amazon Order History Upload campaign as an example. The same underlying logic applies to other platforms that DataDance Wallet will support in the future. Below, we break down how valid orders are defined and when a receipt record is counted.

General Eligibility Rule in DataDance Wallet

DataDance Wallet applies a general eligibility rule to determine whether a receipt record is considered valid. You can already see this rule in action in current official campaigns, such as Amazon Order History Upload campaign.

Under the rule, a receipt is considered valid as long as it has not been uploaded before. There is no built-in time limit and no category restriction in the base logic.

Using the Amazon Order History Upload campaign as an example, if your order history contains Order A and Order B, and you upload them for the first time, both records are treated as valid and earn points. If you later place new orders, such as Order C and Order D, and start the task again, the system automatically excludes Order A and Order B and only counts Order C and Order D, and previously uploaded records are excluded as duplicates.

This will also be used as the underlying logic for similar order-based tasks on other platforms in the future, such as Booking, Airbnb, and other supported services.

Extra Rules in Specific Campaigns

However, some campaigns may introduce additional rules on top of general logic. These extra rules do not replace the base eligibility rule. They narrow the scope of which receipts are counted within a specific campaign.

This usually happens in two cases: official themed campaigns run by DataDance Wallet, and specific campaigns created by brands. In these cases, receipts still need to be non-duplicated, but they may also need to meet extra conditions.

Time-based rules

Some campaigns only count receipts created within a defined time window.

For example, DataDance Wallet previously ran a Christmas campaign that required users to upload orders placed during December 2025. Only receipts from orders created within that month were considered valid for the campaign. Orders outside the December time range were not counted toward the campaign.

This type of rule is used when a campaign is tied to a specific event or period, and does not change how receipts are evaluated elsewhere in DataDance Wallet.

Product or category-based rules

Some campaigns may focus on specific products or categories instead of all receipts. In these cases, only receipts that match the defined product scope are counted for the campaign.

For example, a brand-led campaign may be limited to a certain category, such as baby products. In that situation, only receipts from orders that include items within the baby product category would be counted. Orders containing other types of products would be excluded from that campaign.

In another scenario, a campaign may be tied to a specific product or promotion. Users may need to purchase a particular item or SKU for the receipt to qualify. Receipts from orders that do not include the specified product would not be counted toward that campaign.

These product or category-based conditions apply only to the specific campaign that defines them. They do not affect the general eligibility of receipts elsewhere in DataDance Wallet too.

How to understand your results in practice

When you upload receipts in DataDance Wallet, a receipt not earning points does not automatically mean it was rejected. In most cases, there are only two things to check.

First, whether the receipt has already been uploaded before, since duplicated records are excluded by the general eligibility rule.

Second, whether the receipt falls within the scope of the current campaign, such as a defined time window or product or category requirement.

If neither of these conditions applies and the receipt still does not earn points, the recommended next step is to reach out through the official DataDance Wallet community channels. Our team can help verify whether the receipt meets the campaign criteria and clarify how it was processed.

If you would like to learn more about DataDance Wallet and upcoming platform support, you can follow the official channels below:

APP | Official Website | X | Facebook | Linkedin