Return-to-source ledger
Separate RocketPlay Card Refunds From Winnings Payouts
RocketPlay-related terms in live results allow card-funded withdrawal requests up to the deposited amount to be processed as refunds against purchases. Winnings above that amount can require another supported route and separate verification.
Open RocketPlay payment optionsReconcile card deposits
List each successful card deposit, currency, date, masked suffix, processor reference and any prior refund. Determine the refundable principal remaining.
Do not treat bonus credits or winnings as card purchase value. Keep chargebacks and reversed deposits separate because they can trigger account review.
- Deposit principal
- Masked card
- Purchase references
- Prior refunds
- Remaining refundable amount
Map the payout split
Ask how much will return as card refund and which method receives residual winnings. Confirm whether an expired or replaced card changes the route and what issuer evidence is required.
Record two expected transactions with separate references and delivery windows. A completed refund does not prove the winnings portion has been released.
Close both destinations
Match refund to the card statement and residual payout to its receiving account. Record conversion and intermediary fees separately.
If one part is missing, escalate that transaction ID rather than reopening the full withdrawal. Preserve KYC and payment-ownership confirmation.
Questions players ask
Why can a withdrawal appear as a card refund?
Return-to-source controls can return deposited principal against card purchases.
Are winnings refunded to the card automatically?
Not always; a separate supported route may be required.
Should both parts share one ledger row?
No. Track refund and winnings payout separately.
Last reviewed: 10 August 2026