spribe api: Build an Evidence Trail for Cashout Disputes

A spribe api integration needs a defensible answer to a difficult support question: “I pressed cash out before the crash, so why was I not paid?” A screenshot may show what the player saw, but it does not necessarily establish whether the game accepted the cashout. Before launch, operators should build an evidence trail that separates player actions, authoritative game outcomes and wallet postings—without assuming their integration exposes every event.

This guide focuses on cashout-dispute handling for crash-style games. It is not a description of undocumented SPRIBE endpoints. Confirm the actual message types, identifiers, reporting tools and escalation process available through your contracted integration route.

Define what each piece of evidence proves

Cashout disputes become expensive when support treats every timestamp or transaction as proof of the same thing. Four distinct facts may need establishing:

• Player intent: the player attempted a manual cashout or configured an automatic cashout.
• Game acceptance: the authoritative game system accepted or rejected that action under its rules.
• Recorded outcome: the game recorded a result and any payable amount for the relevant wager.
• Wallet execution: the operator posted the corresponding financial transaction.

A browser event can support the first fact. It cannot, by itself, establish the other three. Similarly, a wallet credit proves that money was posted, not that the displayed multiplier was accurate.

Where the game runs in a provider-controlled client, the operator may have no direct visibility into the cashout request. Document that limitation rather than implying that operator logs contain evidence they never received.

Name the authority before an incident

Ask the integration partner which source establishes a wager’s accepted cashout and final outcome. It might be an authenticated server message, a transaction report or a provider investigation result. Do not assume that the first callback received is final or that a dashboard always reflects corrections immediately.

Record how conflicting sources are resolved, who can confirm a correction and which reporting delays are expected.

Build a spribe api cashout evidence map

Create a small evidence dictionary before writing support procedures. The names below are internal concepts, not claimed provider field names.

| Evidence | What to preserve | Why it matters | | --- | --- | --- | | Integration context | Environment, brand and provider route | Prevents cross-environment or cross-brand confusion | | Wager identity | Player reference, game, round and individual wager reference | Distinguishes bets within the same round | | Game outcome | Outcome reference, status, amount and currency, where supplied | Links the disputed wager to its recorded result | | Message receipt | Receipt time, authentication result and payload digest | Shows what the operator received and checked | | Wallet posting | Ledger reference, amount, currency and commit status | Establishes whether value actually reached the wallet | | Investigation | Case reference, source and resolution history | Preserves later clarifications without rewriting history |

A round identifier alone may be insufficient if the game permits multiple wagers in one round. Verify the supported identity model and preserve the narrowest available wager reference.

Keep original external identifiers alongside any normalized identifiers. A normalization rule that changes case or strips leading zeros can make a later provider search fail.

Minimize sensitive material

Retain only the payload fields necessary for financial reconciliation and dispute handling. Exclude launch tokens, authorization secrets and unnecessary personal data. Restrict access to original evidence, set retention according to applicable obligations and log staff access.

A digest helps detect changes to retained content; it does not prove who originated it. Preserve authentication-verification results separately, using the mechanism actually supported by the integration.

Capture time without inventing an ordering guarantee

One dispute can involve a device timestamp, provider event time, gateway receipt time and database commit time. These clocks describe different events and may not be synchronized.

Store each timestamp with its source, timezone and available precision. Monitor operator infrastructure clock synchronization, but do not assume this aligns the player’s device with the game server.

Avoid these shortcuts:

• Comparing a browser click time directly with an unrelated server timestamp to declare a winner.
• Using callback arrival order as the game’s event order.
• Treating a delayed payout message as evidence that cashout was accepted late.
• Treating the displayed animation or multiplier as an authoritative acceptance record.

If the upstream system supplies an ordering field, confirm its scope before relying on it. A counter scoped to one connection may not order events across a reconnect.

Separate game resolution from wallet resolution

Track two questions independently: “What outcome is authoritative?” and “Has its financial effect been applied?”

A wager can have a confirmed payable outcome while its wallet posting remains unresolved. Conversely, a wallet posting can exist while a conflicting upstream report requires investigation. Collapsing these into one success flag hides the work support and finance must perform.

Preserve the receipt-to-ledger chain

For each financial message, retain a traceable path from authenticated receipt to processing attempt to committed ledger entry. Follow the contracted acknowledgment and retry semantics. Do not acknowledge success merely because an in-memory task was created if that task can disappear before durable processing.

Duplicate deliveries should resolve to the same intended financial effect under the documented transaction-identity rules. Record each delivery attempt without generating duplicate player credits.

If a payable outcome is confirmed but the wallet posting is missing, use the approved reconciliation process. Do not create an unrelated manual credit that a later retry could duplicate.

Turn disputes into a repeatable support workflow

Support should not need database write access or a developer’s interpretation of raw logs. Provide a read-only case view with explicit evidence gaps.

1. Locate the exact wager. Collect approximate play time and game name, then identify the wager through trusted records. Treat screenshots as supporting material.
2. Check the authoritative outcome. Use the agreed report, message or escalation route. Mark unavailable or contradictory evidence as unresolved.
3. Trace the wallet effect. Verify the amount, currency and committed ledger entry rather than relying on a cached balance display.
4. Classify the case. Separate unconfirmed cashout claims, confirmed unpaid outcomes, display discrepancies and conflicting records.
5. Resolve through controlled actions. Reconcile a missing posting or request upstream clarification. Apply approval controls to any adjustment.
6. Explain the finding. Tell the player which records were checked, what they establish and any remaining review or complaint options.

Keep goodwill compensation separate from game settlement, with its own reason and approval. It should not silently rewrite the wager outcome or conceal a reconciliation defect.

Test the evidence trail before launch

Use supported sandbox scenarios or agreed partner-assisted tests. Where upstream failure simulation is unavailable, test your internal processing boundary and document the remaining coverage gap.

Include these cases:

• Delayed outcome delivery: support can distinguish an unresolved outcome from a confirmed loss without inventing a cashout time.
• Repeated settlement message: one financial effect appears, while all receipt attempts remain traceable.
• Ledger failure after receipt: the case shows unresolved posting and can be recovered through controlled processing.
• Multiple wagers in one round: evidence attaches to the correct wager, not merely the shared round.
• Browser clock skew: device timing cannot override the authoritative outcome.
• Conflicting report and callback: the case remains open until the agreed authority resolves the difference.

For launch approval, require support and finance to reconstruct each test from the case view without developer assistance. Also test an evidence export: it should contain relevant references and a clear chronology without exposing credentials or unrelated players’ data.

Confirm the commercial integration boundary

GamingAPI offers 16,000+ games from 150+ studios through one API, with a seamless wallet, multi-currency support and USDT deposits. Commercial terms are $350 one-time setup plus 10% of positive GGR; review pricing when scoping the integration.

Those platform capabilities do not establish specific SPRIBE availability, market entitlement or cashout-level visibility. Before committing to launch, contact to confirm the contracted game route, available evidence and escalation responsibilities. Technical readiness does not replace licensing, market permissions or player-protection obligations.

FAQ

Does a cashout screenshot prove the player must be paid?

Not by itself. It can support the investigation, but acceptance and payout depend on the authoritative game record and applicable rules. Preserve it alongside server-side evidence.

What if no cashout-request event reaches the operator?

Do not manufacture one from wallet timing. Use the available outcome records and escalate through the agreed provider or aggregator process when those records cannot resolve the claim.

Should support immediately credit a disputed payout?

Not as an assumed game settlement. First verify the outcome and existing ledger entries. Any interim or goodwill credit needs separate authorization, labeling and safeguards against later duplicate compensation.