Free Credits Dispute: Calculate a Missing Wager Before Contacting Support

Suppose a hypothetical offer gives you PHP 200 in Free Credits and requires eligible wagers equal to ten times that amount. Your target is PHP 2,000. After playing, the progress counter shows PHP 1,900, but your round history includes a PHP 100 wager that appears to be missing. Should the counter read PHP 2,000? That depends on whether the round qualified and how much that game contributed. The same PHP 100 stake could add PHP 100, PHP 50, or nothing. Work out that difference before asking support to investigate it.

These are invented figures for a worked example, not the terms of a real offer. Your own offer may use a different target, contribution rule, or no wagering target at all. When something looks wrong, the useful question is which recorded event and which written rule produced the number you see.

A PHP 100 wager with three possible values

Start with the hypothetical terms: PHP 200 in Free Credits, a 10x wagering requirement measured against the credited amount, and a displayed eligible-wager total of PHP 1,900. The wager you are checking has a PHP 100 stake. Its outcome does not change the stake used in this calculation; the offer's contribution rule does.

Multiply PHP 200 by 10 to get the hypothetical PHP 2,000 eligible-wager target. Keep that target separate from your account balance.

Subtract the displayed PHP 1,900 from PHP 2,000. The counter says another PHP 100 of eligible wagering is needed.

If the disputed PHP 100 round qualifies at 100% contribution, add PHP 100 to the counter. It reaches PHP 2,000.

If that game contributes 50%, add PHP 50 instead. The corrected total would be PHP 1,950, leaving PHP 50.

If the round is excluded under the hypothetical terms, add nothing. The displayed PHP 1,900 would remain consistent with those terms.

This is why a stake receipt alone cannot prove that a playthrough counter is wrong. It proves a wager was recorded, while the applicable rule decides its eligible value. Likewise, reaching the target would settle only this one condition. A separate withdrawal limit, identity check, or treatment of remaining credit could still affect what happens next if the actual offer includes one.

Capture the counter before another round changes it

A useful record ties the disputed round to the counter you saw at that point. Capture it before placing another wager, because a changing balance or counter makes the sequence harder to reconstruct. Keep the original images or files rather than editing them; you can point out the relevant entries in your message.

Save the offer terms visible when you claimed the credits, especially the target formula, eligible games, contribution rates, and any expiry condition.

Capture the Free Credits balance and progress counter together when possible, so support can see which offer state you are questioning.

Keep the round-history entry showing the stake, game, round identifier, and recorded result, using whatever details the account actually provides.

Preserve the credit or claim record that connects this offer to your account; include a Promo Code entry screen if one was involved.

Record the order of events in your own words, including whether the counter changed after the round or after you reopened the account.

Do not publish account details or full screenshots in a public comment to seek help. Use the site's account support channel and share only what it needs to locate the event. A payment receipt is useful when the complaint concerns a payment, but it usually cannot establish how a particular game round contributed to Free Credits playthrough.

Give support one calculation to reproduce

Contact support through the help route available inside your account or on the site you used. Identify the offer and the disputed round, then show your arithmetic. You are asking for a transaction-level explanation: did the PHP 100 wager qualify, what contribution rate applied, and where did its eligible value appear in the counter?

A concise request might say: “My hypothetical target calculation is PHP 200 × 10 = PHP 2,000. The counter shows PHP 1,900. I see a PHP 100 round in my history that I expected to contribute. Please confirm whether that round was eligible, its contribution rate, and the counter total before and after it.” Replace every example figure with your actual records. If the offer came with a separate Bonus balance, name the balance shown in your account so support checks the right ledger.

Provide the account reference support requests through its secure channel, along with the offer or claim reference if your account displays one.

Identify the disputed round using its recorded identifier and game, rather than relying on a description such as “my last spin.”

State the target formula, displayed total, and contribution you expected, then attach the screenshots that show each underlying figure.

Ask which written term and transaction entry explain any difference, so the reply can be checked against your own record.

A broad complaint such as “my credits disappeared” can cover several unrelated events: an expired offer, a losing round, a balance conversion, or an uncounted wager. A specific calculation helps support find the relevant ledger entry and gives you a way to assess its answer.

When waiting protects the evidence

Consider pausing play while the disputed counter is being checked. Another round might complete the requirement, change the balance, or create a second question that obscures the first. Waiting is especially useful when you have the round identifier and a clear screenshot but do not yet know the contribution rule.

Continuing can make sense if the actual offer has a deadline and you understand that additional play has its own cost. It does not make the earlier discrepancy disappear. Compare the possible cost of further wagering with the value you could actually withdraw under the offer's terms, and do not place extra bets merely to make an unexplained counter look right. If expiry is relevant, save the displayed expiry condition and ask support how the disputed round affects it.

Keep ordinary cash, remaining Free Credits, eligible wagering, and withdrawable funds as separate figures. They can move differently after one round. For example, a losing PHP 100 wager may reduce the playable balance while adding PHP 100 to eligible wagering under a 100% contribution rule. A winning round may raise a displayed balance without completing a wagering condition. The counter measures qualifying activity; it does not promise a payout.

Match the reply to one of the possible outcomes

A useful resolution identifies the round and applies the relevant term to it. If support confirms 100% contribution and finds the round missing, the hypothetical counter should rise from PHP 1,900 to PHP 2,000. Ask to see the corrected total in your account before treating the case as closed.

If support shows that the game contributes 50%, the expected total is PHP 1,950. That answer resolves the PHP 100-versus-PHP 50 difference only if the rule applies to this offer and the round is the one you reported. If support says the game was excluded, the PHP 1,900 total may be correct, but the response should identify the exclusion that governed the round.

Sometimes a delay or display error explains why the counter and round history briefly disagree. In that case, compare the later account view with the original screenshot and check that the change equals the eligible value support described. A reply that merely repeats the current counter leaves the original calculation unanswered.

If the figure still has no explanation

Reply in the same case thread when possible. State the remaining difference in one sentence and refer to the evidence already supplied. If the site offers a formal dispute or complaint route, use that route with the case reference. Keep copies of your submissions and replies, including any corrected counter view.

Compare the round identifier in the reply with your saved history, because a correct rule applied to another round cannot settle this one.

Check that the contribution rate cited appears in the terms for the offer you claimed, rather than in an unrelated offer.

Recalculate the stated correction yourself: multiply the stake by the contribution rate, then add that value to the earlier counter.

Ask for the exact ledger entry or reason for exclusion if the response still does not account for the numerical gap.

The dispute is resolved when the recorded round, applicable rule, and resulting counter agree. That conclusion does not depend on whether the answer is favorable. It gives you a defensible basis for deciding what to do next, without guessing from the size of the Free Credits balance.