Separate request, account debit, sending and receipt. Use a status checklist, a worked USD500 reconciliation and a written complaint to investigate missing funds.
A withdrawal request, a debit to your trading account, a provider's “paid” message and a credit to your bank account are different events. Evidence of one does not establish the others. The practical question is who owns the next step and which record would show where the payment went.
Preserve what you already have before changing or cancelling requests. Pause unnecessary extra transfers demanded because of the delay. Do not deposit more money to test reliability or open hurried trades to satisfy a newly announced turnover target. A processing status alone does not establish fraud; equally, it is not evidence that a payment was sent.
| Visible status | Ask for this record | What it does not yet establish |
|---|---|---|
| Submitted, not reviewed | Request ID, receipt time, applicable process and document list | A request screenshot does not show that review started |
| Document review | The specific missing item, verified upload channel and next written update | Providing identity documents does not guarantee approval |
| Approved or trading balance debited | Approved amount, currency, fees, payment route and actual sending status | A ledger debit is not a bank transfer confirmation |
| Sent, but not received | Route-appropriate reference, sending date, net amount and recipient details | “Successful” in a dashboard is not recipient-side settlement |
| Rejected, returned or cancelled | Reason, contractual basis, return reference and balance restoration | Cancellation alone does not restore an available balance |
| Extra tax, upgrade or unlock payment required | The complete written demand, calculation, legal entity and payee | An official-looking logo does not establish collection authority |
Ask the payment provider which tracking identifiers it can actually use. Card refunds, bank transfers and on-chain transactions do not all generate the same reference. A traceable identifier helps investigation; it does not guarantee recall or reimbursement.
Consider a fictional USD withdrawal of 500 with a previously disclosed handling fee of 5. The provider should explain a net payment of 495. If a receiving institution separately charges 10, the eventual credit could be 485, but that additional fee needs its own record. Do not assume an unexplained shortfall is an intermediary-bank charge.
| Reconciliation step | Example USD amount | Supporting record |
|---|---|---|
| Gross withdrawal request | 500 | Request receipt and trading-account debit |
| Disclosed provider fee | −5 | Applicable terms and transaction-level fee entry |
| Claimed net payment sent | 495 | Payment confirmation and tracking reference |
| Additional payment-chain charge | −10 | Actual payment or receiving institution record; otherwise unverified |
| Recipient account credit | 485 | Recipient statement, not the trading dashboard |
Under those assumptions, 500−5−10=485. It is not a loss of “500 plus 15”. If nothing arrived, record “claimed payment of 495 not received; additional charge of 10 not established” rather than filling gaps with imagined evidence. Separate trading losses, currency conversion and multiple withdrawal requests into dated entries. A total dashboard balance cannot explain the path of each payment.
Choose a consistent time zone for submission, document requests, approval, sending and the recipient institution's reply. Retain original timestamps as well. Number attachments: E01 contract, E02 funding statement, E03 withdrawal receipt, E04 provider response and E05 recipient-side response. Refer to those numbers in the timeline instead of pasting an entire chat archive into the opening complaint.
Match the legal entity in the contract with the account website, masked account identifier, payment recipient and independently verified contact details. If the provider changes its domain or payee, preserve both versions. Keep originals unchanged and create separate redacted copies for sharing. Never publish identity documents, full payment-card details, passwords, verification codes or wallet recovery phrases. Verify a recipient before sending sensitive case material privately.
Use the official-register verification guide to identify the contact. Another licensed company in the same group does not necessarily operate your account. A customer-support ticket and a formal complaint may follow different procedures, so request a complaint reference and responsible department.
Adapt this wording to facts you can support:
“Please register a formal complaint. I requested [amount/currency] on [date/time zone], reference [ID]. The established status is [fact]. The missing information is [payment reference/rejection reason]. Please provide the applicable term, outstanding documents, actual sending date and amount, and the next written response date. My requested resolution is [trace payment/explain rejection/correct balance/pay disputed amount]. Attachments E01–E05 are listed. Please identify the applicable independent dispute route.”
Say “I have not received evidence of sending” when that is the fact, rather than claiming no customer can withdraw. The complaint evidence template explains attachment organisation and redaction.
“Offshore” is relative to a location, not a finding about a particular withdrawal. Check the contracting company, jurisdiction, service permissions, payment arrangements and whether an independent dispute body covers that entity and customer category. Displaying a licence held elsewhere does not transfer your account into that protection regime.
A successful small withdrawal establishes only that an earlier payment occurred. It does not establish future liquidity, custody arrangements or enforcement prospects. Do not send additional funds to test an account already in dispute. Complex jurisdiction also does not prove recovery is impossible: identify an authority with actual remit and check its eligibility and deadlines.
For a UK procedural example, FCA guidance generally provides an eight-week written-outcome period for most complaints within its rules; some payment-service complaints have different periods. FOS usually applies a six-month referral deadline following a firm's final response, subject to eligibility and exceptions. These are not permission to delay an ordinary withdrawal for eight weeks and are not worldwide rules.
If you suspect fraud, promptly ask your bank or payment provider about reporting, tracing and dispute options rather than waiting for that complaint period to expire. Refund availability depends on the route, facts and time limits. Do not describe a transfer you authorised as unauthorised. Seek qualified advice for substantial losses or decisions between legal procedures.
Do not give remote access, passwords or recovery phrases to someone offering to retrieve funds. An upfront payment paired with a guaranteed-unlock claim needs independent verification; knowledge of your loss does not establish legitimacy. For a tax-labelled demand, use the pre-withdrawal tax verification checklist.
FXCN is not a bank, regulator or adjudicator and cannot order repayment or determine a complaint from a broker score. Official references: FCA complaints process, FOS time limits and FCA recovery-room warning.
For a new approach promising to retrieve lost funds, use the recovery-offer verification checklist to separate the caller's identity, tracing claims, authority and fees from the original withdrawal dispute.