Decide Carefully During the Ripper Reversal Window
Ripper help results describe a delay before payout processing begins. During that interval, funds may remain reversible. The useful decision is whether the original request is correct and complete—not whether the balance could be played again. Document the consequences before pressing cancel because a replacement may receive a new start time.
Open Ripper and inspect the pending requestCalculate the window endpoint
Write the submission timestamp, operator timezone and stated business-day rule, then mark weekends and public holidays. Keep the displayed countdown if one exists. A calendar forty-eight hours and two working days can end at different moments.
Audit the request before touching it
Confirm destination, currency, amount, minimum, applicable limit and completed verification. If every field is correct, record that no change is required. Do not reverse simply because the cash becomes visible again.
Price the cancellation consequence
Ask whether cancellation returns funds immediately, restarts compliance checks or resets the pending period for a replacement. Record whether the old amount still counts against weekly or monthly capacity. Obtain the answer before acting.
Preserve both IDs if replacement is necessary
Keep the cancelled request, reason and balance return, then give the corrected payout its own identifier and start time. Never overwrite the old row. This chronology shows whether a later delay belongs to the original request or the new queue position.
Frequently asked questions
Are two days always forty-eight clock hours?
Not when a business-day rule controls.
Should reversible funds be replayed?
No; that changes the balance and evidence.
What happens after replacement?
Confirm whether a new pending period and limit allocation begin.
Last reviewed: 3 August 2026