Withdrawal History and Tracking
Finding your history
The transaction list lives in the account or balance area alongside the cashier, and it can normally be filtered so payouts are separated from deposits and trades.
This is the screen most traders never open until something goes wrong, at which point it usually answers the question immediately. Getting familiar with it while nothing is urgent is a small investment with an outsized return.
The transactions tab
Look in the account or balance section rather than on the trading view. The same list is available from the web cashier, the desktop client and the mobile app, since all three read the same record. If entries appear in one client and not another, the cause is a cached view rather than missing data.
Filtering by type
Separating withdrawals from deposits makes the picture much clearer, particularly on an active account where trades dominate the list. Filtering by date range as well is what turns a wall of entries into an answer.
Status labels explained
- Pending: accepted and in the operator review queue, not yet on a payment rail.
- Processed or sent: released by the operator; any remaining wait belongs to the receiving side.
- Declined: blocked by a condition that is normally named in the message.
- Cancelled: withdrawn by you, or not completed.
Reading the label literally saves a great deal of wasted effort. A pending request has not reached your bank, so asking your bank about it is pointless; a processed request has left the platform, so asking the platform where it is achieves little.
The single most useful check this screen offers is also the simplest: confirming that a request exists at all. A form that failed silently leaves you waiting for something nobody received, and ten seconds here rules that out.
The second most useful is checking for duplicates. Where a cashier misbehaved and you pressed submit several times, more than one request can appear once the connection recovers, and duplicate payout requests attract exactly the manual review you were hoping to avoid. Cancel the extras before they reach the queue rather than explaining them afterwards.
Open the transaction list first when a payout goes quiet, because it tells you which party to ask.
Reading a payout entry
Each entry carries an amount, a method, a timestamp, a status and a reference. Together those five fields answer most questions without anybody needing to be contacted.
They are also exactly the fields a support agent will ask for, which is why quoting them in a first message resolves in one reply what a vague report takes several exchanges to resolve.
Amount and method
The amount shown may differ from what you expected if a deduction applied, since the payment policy allows commissions to be set per method and changed at any time. It may also be smaller than the total you requested if the payout split — a card refund cannot exceed what that card deposited, so the excess travels separately.
Timestamp and status
Count elapsed time from the timestamp in business days rather than calendar days. Against the published figures — three business days for processing, extendable to fourteen, and five business days for funds leaving the account — most requests that feel late turn out to be inside the documented range.
Reference numbers
- Save the reference outside the platform, not just in a browser tab.
- Quote it in any support message, in the first line.
- Give it to your bank if they query an incoming credit.
- For crypto, keep the transaction hash as independent evidence.
The transaction hash deserves special mention because it is the only piece of payout evidence that does not depend on anybody trusting a screenshot. Anyone can verify it on a public explorer, which makes it decisive in a way that a dashboard image never is.
Get in the habit of reading the entry immediately after submitting rather than only when something feels wrong. Confirming at that moment that the amount, method and destination are what you intended costs five seconds and catches the small number of mistakes that are still cheap to correct while a request is pending.
Amount, method, timestamp, status and reference answer most questions, and they are what support will ask for anyway.
Using records well
The history serves three purposes beyond troubleshooting: settling disputes, supporting a tax conversation, and telling you honestly whether the activity has cost you money.
All three depend on records you kept at the time. None of them can be assembled afterwards from memory and a bank statement.
Dispute evidence
If the platform shows a payout as sent and your bank says nothing arrived, the person holding a dated confirmation, a reference and a matching statement resolves it in a day. The person reconstructing the story does not. That asymmetry is the whole argument for record-keeping.
Tax documentation
Treat gains as reportable unless a qualified professional in your own jurisdiction tells you otherwise. This site is not a tax adviser and will not summarise anyone rules. What it can say usefully is that you should be able to reconstruct what you deposited, what you withdrew and when — which is trivial if you save as you go.
Personal accounting
- Total deposits against total withdrawals over a period.
- Fees and deductions taken along the way.
- Which method proved cheapest and fastest for you specifically.
- Whether the account has cost you money overall.
That last line is uncomfortable and worth doing anyway. Short-horizon contracts can and often do cost people what they put in, and a clear deposit-versus-withdrawal total is the least sentimental way to find out where you actually stand.
Do it on a schedule rather than in a bad week, because the numbers read very differently depending on when you look at them. A quarterly total, calculated from records rather than recalled, is one of the few actually objective things available to a retail trader, and it costs nothing beyond the discipline of keeping the confirmations in the first place.
Keep records for disputes and tax, and use the deposit-versus-withdrawal total as an honest scoreboard.
Tracking a live request
A request in flight moves through a small number of states, and knowing which one it is in tells you whether to wait, to act, or to ask somebody else.
The sequence is short and it only ever runs in one direction.
Pending to processed
- Submitted: confirm the entry exists in the history with a reference.
- Pending: in the operator review queue; verification and screening happen here.
- Processed or sent: released to the payment rail by the operator.
- Credited: arrived at your bank, wallet or wallet address.
- Declined: blocked by a named condition, which needs action rather than waiting.
Rail confirmation
Once the status shows processed, the operator has done its part and the remaining wait belongs to the receiving institution. For crypto you can verify this yourself on a public explorer using the transaction hash. For a card or a bank transfer there is no visibility, which is why the issuer or bank is the right party to ask.
Follow-up triggers
- Still pending past the published window with no message: open a ticket.
- Declined with a stated condition: fix the condition, do not wait.
- Processed but not credited: ask the receiving institution first.
- No entry at all: the request was never created; submit again on a clean session.
Banks and wallet providers routinely hold a first credit from a new source pending a routine question, without notifying the customer prominently. A single message to them resolves more of these than any number of tickets to the platform.
Resist the urge to act on every state change. The only two that call for anything from you are declined, which needs the named condition fixed, and a missing entry, which needs the request submitting again. Everything else resolves by waiting out a window that has already been published.
Match your next action to the status: wait on pending, act on declined, ask the bank on processed.
History takeaways
Keep your own copies, match them against the receiving side, and the records do the work whenever anything needs explaining.
Three habits, none of which take more than a few seconds at the time.
Keep your own copies
Screenshot each confirmation showing amount, method, any deduction and the reference. Store them outside the platform. Access to an account is not guaranteed forever, and a record that lives only inside a service you may lose access to is not really a record.
Match with bank records
Pair each payout confirmation with the receiving institution own record of the credit. That pairing is what turns a delayed payout from an argument into a single message, because it shows both ends of the transfer with dates attached.
Records ease disputes
- Include the reference in the first line of any ticket.
- State elapsed time in business days, not calendar days.
- Attach evidence rather than describing it.
- Keep the whole exchange in one thread.
Registration is free and verification can be completed before any deposit, which is where most payout problems are prevented rather than documented. If you are still weighing the platform up, the demo side needs no funding and generates nothing to record.
Save confirmations outside the platform and pair them with the receiving record; nothing else makes disputes short.
What readers ask about payouts
Where do I find my Pocket Option withdrawal history?
In the account or balance area alongside the cashier, usually under a transactions tab that can be filtered by type and date. The same record appears in the web cashier, the desktop client and the mobile app, since all three read the same data.
What do the withdrawal statuses mean?
Pending means the request is in the operator review queue and has not reached a payment rail. Processed or sent means it has been released and the remaining wait belongs to the receiving institution. Declined means a condition blocked it, normally named in the message. Cancelled means it was not completed.
My withdrawal is not in the history at all. What happened?
The request was probably never created. A form that failed silently, a session that expired mid-submission or a confirmation screen closed too early all leave you waiting for something nobody received. Submit again on a clean session, then check the history to make sure only one request exists.
Do I need to keep my own records?
Yes. Access to an account is not guaranteed forever, and a payout dispute is resolved in a day by someone holding a dated confirmation, a reference and a matching bank record. The same material is what any tax conversation needs, and none of it can be reconstructed afterwards from memory.