SM Pay Australia · Account and offer guide
Trace a casino payment reference
A payment reference connects a bank-side transfer with the account provider’s record. When a deposit is missing, matching the identifiers and amounts gives support a precise issue to investigate.
View partner site ↗The detail that changes the comparison
Record the payment time with timezone, source amount, currency and status. Distinguish a bank reference from a processor reference and an internal cashier ID. They may refer to different stages of the same payment and should not be assumed to be interchangeable.
A pending payment should be investigated as the existing transaction. Sending another payment can create a second transaction without resolving the first. The useful support request asks which stage has the funds and which identifier the next party needs.
A worked comparison
Example conditions
A bank receipt may show reference ABC123 while the cashier shows order 456789. A clear report lists both, the matching A$250 amount and the exact time, rather than saying only that the money is missing.
Use the same assumptions on both sides of the comparison. If one proposal uses a different currency, period or balance category, translate that difference explicitly before comparing its result. A numerical example answers the arithmetic question; the written terms answer whether those inputs apply to the account.
For an actual record, keep the original amount and the calculation alongside the result. Rounding can be applied at different stages, particularly with percentage charges, exchange quotes and reward points. When a small difference remains, the rounding rule is a more useful next question than replacing the source figure with an estimate.
Four fields to keep together
| Required detail | Action | What the record should establish |
|---|---|---|
| Bank-side identifier | Identify the starting record | Keep the original label and its amount, currency or event identifier. A rewritten summary can omit the unit that makes the value comparable. |
| Cashier or processor identifier | Apply the actual condition | Use the condition attached to this specific transaction or offer. Record the calculation basis and the point at which the condition is evaluated. |
| Amount, currency and timestamp | Compare the matching result | Compare the outcome with the same category in the account record. A pending entry and a settled entry may describe different stages of one event. |
| Current status on each side | Keep the unresolved item precise | If this field is absent, ask for it directly and retain the answer with the corresponding reference. This makes the next comparison reproducible. |
These fields form one compact comparison record. Keep them together with the date and the relevant transaction, offer or case reference. That prevents a condition from one version being attached to a result from another. When a service changes its wording, the saved record also shows which condition was visible for the event being discussed.
Use a consistent accounting basis
Choose a starting balance and a precise interval. Distinguish settled transactions from pending holds, and gross returns from net changes. If a history already reports the net result of a round, subtracting its stake again creates an error. A simple ledger is often enough to reveal which category needs clarification.
Use identifiers rather than dates alone to connect records. Several payments or rounds can share the same date and amount. A bank reference, cashier order and game round ID identify different stages. Preserve each in its own column and state which stage is unresolved when asking for an explanation.
A payment comparison you can reconcile
Create one row for each stage: source account, payment processor, destination wallet and receiving account for a withdrawal. Amounts should have explicit currency codes and each stage should retain its own reference. This is particularly useful when a single payment involves both a fixed charge and an exchange rate.
Once the amounts reconcile, compare the conditions governing the route. Method availability, ownership requirements and any qualifying promotion are separate fields. If a field is missing, identify the exact question it prevents you from answering rather than filling the gap with an assumed policy.
Practical questions
Which reference should be sent?
Send the identifiers relevant to that provider, with unnecessary account details redacted from supporting screenshots.
What information makes this comparison usable?
Keep bank-side identifier, cashier or processor identifier, amount, currency and timestamp, and current status on each side in the same record. Those fields connect the headline condition to an identifiable account event.
Does an example establish the current account terms?
The examples explain a calculation or decision with stated assumptions. The current offer, cashier quote or account response supplies the applicable figures. Keep that source with the date and reference used for the comparison.
Related decisions
Use the comparison above to read the current account details and available options on the partner site.
Open partner site ↗Reference for this decision
This guide explains account terminology and hypothetical calculations. No operator-specific processing time, supported payment route or live reward is inferred from the example.
Editorial method · All account and offer guides · VIP proposal comparison