A small base-bet number below a slot may differ from the price of a feature purchase. When its confirmation panel quotes 200, that complete purchase price needs checking. Recording only 2 because it appears as the base bet elsewhere would understate the cost.
In the JILI777 PH guides, “bonus buy” names a possible mechanic. It does not promise availability in every game or at every operator. This update does not audit feature availability across the catalogue. The purchase and settlement below are fictional; no real paid gameplay test was performed.
Three records answer different questions
Help describes the feature and its pricing basis. The confirmation panel quotes a price for selected settings. Transaction history shows what was accepted and debited. These records are related, but their roles are not interchangeable.
If a base bet of 2 and a purchase factor of 100× are expressly stated in the exact rules, the expected quote would be 200. Do not borrow that factor from another game. If the panel quotes 240 instead, “perhaps a fee” is only a guess; mode, basis or settings might differ. Stop before confirmation until the discrepancy is explained.
Keep the quote separate from the confirmed charge
| Record | Amount | Meaning |
|---|---|---|
| Quote | 200 | Price shown before purchase |
| Confirmed debit | 200 | Cost actually paid |
| Settled gross return | 150 | Total returned by the feature |
| Net result | 150 − 200 = −50 | Loss under this model |
The return is not “profit of 150”; the purchase first cost 200. With an opening balance of 500 and no other transactions, the closing balance would be 500 − 200 + 150 = 450. Its change of −50 reconciles with the net result.
If the source quotes a stake in euros, read why a converted amount is not a verified PHP minimum.
An unaccepted offer is not a confirmed purchase cost
A quote screenshot does not establish a purchase debit if the offer was never confirmed. Do not add 200 to costs simply because the panel displayed it. If a debit exists without an acceptance record, keep its status unresolved and retain the transaction ID.
A cancellation message is also different from a refund credit. After a debit of 200, record a refund only when the credit is actually confirmed. A promised refund is not money already returned. Keep any unrefunded part separately visible when the credit is partial.
Match one paid action to a clear record
For existing history, match purchase ID, round ID, edition, mode, base bet, pricing factor, quote, debit and final settlement. Preserve confirmation and settlement times rather than rearranging events according to later screenshots. Do not add feature-summary awards to animation counters that are already included in them.
After a connection interruption, use documented history or support to establish the status. Another purchase is not a necessary way to test acceptance of the first one. It might create another paid action rather than continue the earlier one.
Use the ledger to identify an unexplained gap
A quote of 200 and history debit of 240 leave a cost gap of 40 whose cause is not established. Find the accepted settings and an itemised explanation; do not silently subtract the gap from return or label it a commission. If debit is 200, return is 150 and a balance of 500 closes at 440, another movement of 10 remains unexplained by our simple model.
A list of unknowns is more useful than a total forced to reconcile. Redact private account and payment details when preparing support evidence.
Source and limits of the explanation
UK Gambling Commission RTS 3 is a UK standard addressing game information, including rule and financial details needed to understand play. It supports information-reading questions here; it does not verify a domain’s UK or Philippine licence. Our illustrative amounts establish no real-game price, RTP or feature availability.
A clear ledger explains cost; it does not improve the next outcome’s chance. Do not increase a budget to recover a feature purchase. Return to JILI777 PH for other guides before making a decision.