Disputed prediction trade settlement results? How the platform reconciles prices, times, and fund flows
"The price in the screenshot clearly went up, why does this price prediction show as a miss?" When customer service receives this type of inquiry, they should first ask the user for the order number and keep the screenshot. The order number helps the team retrieve the acceptance conditions, and the screenshot helps confirm which instrument, price type, and moment the user was viewing at that time.
The platform needs to check two things. First, whether the order was judged according to the rules applicable at the time of acceptance. Second, whether the fund processing following that judgment is complete. Investigating these two matters separately is necessary to give the user a specific response.
1. If the screenshot and result do not match, first confirm the price basis
All three gameplay types of 6MM prediction trading use the platform contract mark price as the pricing basis. The latest transaction price on the page or external market charts may display a different price. Even when viewing the same type of price, the display precision, update time, and sampling interval may differ.
For example, a user opens the market chart after the session ends and sees that the price is higher than the session opening price. Customer service should retrieve the opening price, settlement price, and corresponding time from the session associated with the order, and then compare them with the price type, instrument, and time on the screenshot. When the screenshot shows the latest transaction price a few seconds after the session ends, the two records describe different market points in time and price bases. When replying to the user, you can explain which price the session used, when it was sampled, and how this price corresponds to the judgment result.
2. Find the correct time and judgment evidence based on the gameplay
- Trend Prediction is checked by session. First find the session number, then compare the opening price and settlement price of that session. When the prices are equal, check the flat price handling rules applicable to that session.
- Custom Prediction is checked by individual order. Even if two users choose the same instrument and direction, the opening price, expiration time, and settlement price of their respective orders must be checked separately.
- Prediction Grid is checked according to the price range and valid time window at the time of acceptance. View the price path within the window to confirm whether it touched or crossed the range according to the applicable rules. A single screenshot at the end cannot determine whether the price entered the range previously.
When the price happens to fall on the boundary, the time刚好 expires, or there is a market gap within the window, the order number, affected time period, and available price records should be retained, and the processing result should be queried according to the applicable rules. When grid sampling is missing, existing records may not be sufficient to determine whether a hit occurred, and the case should enter abnormal verification.
3. The result is already displayed, why hasn't the balance changed yet?
Result determination answers "whether order conditions are met," and fund settlement answers "how much funds are processed and which transaction flow it corresponds to." For orders that have already displayed results, first check the final status of the order, actual refund, and settlement records, and then query fund account changes by transaction serial number. When there are questions about the refund amount, use the odds, applicable fees, and rounding rules recorded in the order to recheck.
Cancellations and refunds must also be confirmed separately. Cancellation describes the invalidation of an order, and refund describes fund processing. When handling this type of ticket, you should simultaneously check the reason for cancellation or refund, actual fund changes, and whether there is still a frozen balance. When replying to the user, you can clarify whether the current status shows results confirmed, funds being processed, or available settlement transaction flows that can be verified.
4. How can the platform reduce back-and-forth checking?
The order details page and customer service backend can organize information around the same order number. The user side prioritizes displaying the gameplay, the price and time used for judgment, results, and settlement progress. The customer service and technical sides then view price evidence, acceptance conditions, anomaly reasons, and associated transaction flows based on permissions. Taking "results released, funds being processed" as an example, this type of stage prompt lets users know the current progress and allows customer service to continue checking directly from the fund stage.
Launch acceptance can cover three types of cases: page market prices and settlement mark prices differing, results already issued but transaction flows not yet completed, and rechecks caused by flat prices or boundaries. During acceptance, have operations, customer service, and technical colleagues walk through the same order number to confirm that all teams can locate the same record and explain the current status.
6MM provides prediction trading technology infrastructure for partner platforms. During integration, platforms can use these dispute scenarios to confirm the criteria for front-end display, customer service handovers, and anomaly handling, ensuring that post-launch issues have verifiable evidence.
Build, Empower, and Drive Your Digital Asset Business
Choose a time with our product team to discuss integration needs, liquidity options, and deployment timelines.
Book a Demo