What to do when your Wise account is under review

Start here if your Wise account is under review#

If your Wise account is under review and payments are affected, treat it as a cashflow problem first, not just a status label. Focus on what you can verify, document it, and keep operations moving while the review is active.

A transfer delay, temporary account restriction, suspension notice, and closure notice can require different responses. Start with the notice that applies to your account rather than assuming every review has the same restrictions.

Start with a clean record before you do anything else:

• Capture the exact notice shown in your account and when you saw it.
• Note your last successful account activity and any related email subject line or reference number.
• Separate urgent commitments in the next few business days from items that can wait.
• Save screenshots, emails, and support replies in one place so you can track one consistent timeline.

If you are already stressed, do not skip this logging step. A review gets harder to manage when the facts are spread across inboxes, chat messages, and half-remembered screen states. You want one timeline you can reuse in every reply instead of rebuilding the story each time someone asks what happened first.

For platform-specific action, rely on your in-account notices and the Wise Help Centre. If a detail is not confirmed there, do not treat it as confirmed. From there, decide whether the issue appears limited to a single transfer or broader account access.

Identify your exact Wise status before you act#

Do not act on assumptions. Classify the issue by what you can prove in your account so your next step matches what is actually happening. Use these labels as working shorthand, not official Wise definitions:

• Transfer paused: one transfer appears delayed, pending, or under review.
• Account suspension: the issue appears account-level, not limited to one transfer.
• Account closure: the notice suggests the account relationship is ending.

Treat your label as provisional until you have the exact in-app notice language.

Check the affected transfer and account notice without creating new transactions. Record whether Wise is waiting for documents, showing a delivery estimate, or announcing a restriction or closure.

Do not send test payments or make card withdrawals to diagnose a restriction. Opening a card screen does not establish that incoming transfers or withdrawals are permitted.

Record observed facts: the notice text, transfer reference, request deadline, and which payment functions the notice restricts. Avoid guessing the review’s cause from a screen that still opens.

At this stage, keep the goal simple. Name the issue narrowly, verify only what you can confirm in-product, and log facts you can prove.

Run first-hour checks in the right order#

For an account review, check the notice and information requests immediately. For a transfer that is merely late, compare its delivery estimate and sender details. These are separate paths; do not wait for a transfer estimate to pass before answering a review request.

Check timing before you assume a hold#

Start with the transfer's estimated delivery time as your baseline. Confirm the send date and time, then count only working days, since Wise processes most transfers on working days and estimates use Monday to Friday.

Use this order:

1. Confirm the original send date and time.
2. Count working days only.
3. Check whether the estimate has actually passed.
4. Only then move to deeper checks.

Transfer transit and account review use different clocks. An outside-bank Swift or wire transfer can take 2–6 working days to reach Wise, but that estimate does not predict when an account restriction will end.

This check can rule out false alarms. If the estimate has not passed, you may not have a review problem yet. If it has passed, you now have a clear reason to move from watching to collecting evidence. Make a note of the exact time you concluded the estimate was exceeded so later follow-ups stay consistent.

Clear account-side prompts in Home first#

Once timing is clear, go to Home and check the activity list, pending tasks, and notifications. Wise says transfers may be paused while it asks for more information, so this is the first in-account checkpoint that can actually move the case forward.

Answer the identity, address, or source-of-funds requests that apply to your case. Wise says calling support cannot remove a temporary restriction or accelerate the review. Support can still help with access or upload problems; use the official channel when you cannot submit a requested file.

Do not clear one request and assume the case is moving. If there are multiple prompts, finish all of them and capture what you submitted. A simple screenshot before and after upload can save time later if you need to show that the request was completed.

Verify sender-side facts, not just "we sent it"#

If your side is clear, verify what the sender actually did. Ask whether they sent with Wise or from an outside bank.

If they used Wise, ask for the Tracking link so you can see where the transfer is. Then confirm the beneficiary details they used. Wrong details can cause rejection and return, and name typos can matter for some currencies, including JPY.

When you ask the sender for confirmation, ask for specifics in one message so you do not lose another day to back-and-forth. You want the amount, currency, send date, estimated delivery time, and payment route they used. "We sent it yesterday" is not enough to reconcile anything.

If the estimate has passed, switch to evidence collection#

If the estimated delivery time has passed after those checks, stop rechecking the same screens and collect Proof of payment. Ask the sender for a bank document that includes:

• sender's name and account details
• recipient's name and account details
• date and amount
• currency

This is the document Wise asks for to help trace missing funds.

At this point, your job changes from monitoring to documentation. Mark the transfer as "awaiting trace evidence" in your own log. Save the document when it arrives, and keep it attached to the same case timeline as the original notice and any Home prompts you completed.

Build the document pack once and submit cleanly#

Keep one case record, but submit files through the specific channel Wise requests. A missing-transfer trace may need bank proof of payment; an account review may need identity or source-of-funds evidence. Do not upload unrelated card-limit screenshots as a standard review pack.

Match each requested file to the relevant transfer or account request, record its submission time, and keep a readable copy. Send the information needed for that request rather than a broad dump of private documents.

What to assemble before upload#

• The exact account or transfer notice and reference
• The requested identity, address, or source-of-funds document, where applicable
• For a missing transfer, bank proof containing both parties, date, amount, and currency
• A record of what was submitted and when

Check document validity, readability, and consistency with the account and transfer. Follow the case request for format and submission channel.

Common artifacts and purpose#

Before sending, do a quick quality check so each file is readable and clearly mapped to the same case. Share only what is needed for that case.

Keep a local index of requested files, submission dates, and responses. Restrict access to identity and bank documents, and share them only through the verified channel for the case.

Understand what is blocked during suspension and closure#

A temporary restriction is not the same as Wise’s documented suspension process. The suspension Help Centre page describes a mandatory compliance check concerning politically exposed person status. Follow the exact account notice and requested response for your case.

For new payments, notify clients before they send to a route that cannot receive. Review Direct Debits and urgent bills tied to the affected account. Use another permitted account only after confirming it can fund the payment; do not evade the restriction or resubmit a payment whose outcome is unknown.

For a planned closure, use the full-close date in the email. Wise says the usual period to move money out is 90 days from the first email, or 30 days for accounts registered in Brazil. Download needed statements while access remains available and follow the notice’s specific instructions.

For pending transfers cancelled on account closure, Wise publishes refund estimates based on the original funding method. These estimates are separate from returning an existing account balance after checks:

• 2-3 working days for bank or wire transfer
• 3-10 working days for card
• Up to 90 working days for bank debit or ACH while due diligence checks are carried out

Wise’s closed-account guidance says it cannot provide the specific reason and Support cannot view it. Preserve the notice, remaining-balance details, and transfer records. Appealing does not automatically reverse the decision.

Escalate and appeal without losing your position#

Escalate in sequence, not by volume. A review is easier for the next person to assess when your record is complete, consistent, and easy to follow.

Use the appeal route and deadline stated in the closure email where applicable. For a temporary restriction, respond to the information request; repeated support calls cannot accelerate review. A formal complaint concerns service and agreement handling and does not itself reverse closure or speed security checks.

When you escalate, make the handoff fast for the next reviewer. Include concise context such as:

• Case ID or reference number (if available)
• A short timeline of key dates and prior replies
• Relevant status screenshots or documents you already submitted
• One clear ask, such as confirming receipt or requesting a review

Keep the ask narrow. "Please confirm whether the uploaded document is sufficient for review" is easier to handle than a long message that mixes complaints, speculation, and three different requests. A concise escalation does not minimize the problem. It makes your file easier to move forward.

If you need to complain about service or handling, use Wise’s official complaint process for your region. Keep it separate from the appeal and refund requests, and save the response and escalation instructions.

Keep client cashflow moving while review is open#

When receipts are disrupted, the immediate job is cashflow control. Keep money moving in and out with a clear plan for the current period.

Build one live tracker with expected inflows, essential outflows, amounts, due dates, payment method, and status. Cashflow management works when you track and analyze all money in and out, and one common risk is a timing mismatch between delayed collections and scheduled payments.

A simple tracker is enough if it answers three questions quickly: what is due soon, what is already at risk, and what you can reroute now without creating reconciliation problems later. The point is not perfect forecasting. It is preventing avoidable missed payments while the review stays open.

Split actions into now and next#

Now#

• Pause new intake to the affected route if you cannot confirm normal receipt.
• Notify clients with open invoices before they send payment.
• Route urgent receivables to a backup route or account you already use and can reconcile.

Next#

• Update payment instructions only where routing actually changed.
• Reconcile payments already sent so you can separate late payments from missing ones.
• Keep one status log with payer, amount, invoice, payment method, send date, and payment proof or reference.
• Prefer electronic invoicing where possible, since it can reduce payment time versus paper invoicing.

A useful operational split is this: for invoices not yet paid, decide whether to reroute or pause; for payments already sent, investigate and document rather than changing instructions midstream. Mixing those two groups can make it harder to tell which money is delayed and which payments were redirected.

Tell clients what changed and what did not#

Keep client messages short and specific:

• What happened
• What is unchanged on your side, such as delivery plan and contact channel
• Whether to pay now with updated instructions or hold payment briefly
• When you will send the next status update

Example: “Wise is reviewing our collection account. Please hold payment for invoice INV-104 until I confirm the payment route through our usual channel. If you already sent it, send the transfer reference and do not pay again. I will update you tomorrow by 3 pm.”

That structure can reduce back-and-forth by making the pay-now, hold, or update decision clear.

Avoid adding extra collection routes unless you can keep records and reconciliation clear in the same tracker.

Keep records ready for future requests#

The best prevention is clarity. Keep your account activity easy to understand, with consistent names, clear payment purpose, and records that match your stated account use.

Wise may carry out further checks after verification. Its temporary-restriction guidance mentions identity, address, source of funds, unusual activity, and policy compliance. Clear records can help you respond; they do not guarantee exemption from review.

Make verification checks easy to pass twice#

Repeat friction often comes from avoidable mismatches. Keep your profile name, invoice name, payer records, and submitted ID details consistent every time.

Before a new client pays, confirm:

• the exact payer name you expect
• the reference format you want used
• purpose wording that matches the invoice

Keep a standing document set ready for follow-up requests. Include:

• current government ID
• proof of address (if requested)
• short description of intended account use
• recent invoices or payment context
• business tax ID and payment information that match your books (if you operate as a business)

Think of this as reducing explainable confusion. If the payer name on the transfer, the invoice name in your records, and the identity details on file all line up, you have fewer moving parts to explain if questions come later.

Separate flows so your records tell one story#

Separate business and personal flows to reduce audit friction on your side. Cleaner books and cleaner naming can make activity easier to explain if a review happens.

Mixed records can create costly delays, especially when manual data entry is involved. Align account naming with bookkeeping categories, and keep the same verification discipline you use in vendor onboarding. That includes payment information and tax IDs before normal operations. If you need a deeper reset, read Separating Business and Personal Finances: A Important Step for LLCs.

A good test is whether an outsider could understand the purpose of a payment from your records without asking you for background. If not, the activity may still be legitimate, but it is harder to review quickly.

Recheck policy when your activity changes#

When your client mix or transfer pattern changes, recheck your account setup and documentation before the new pattern becomes routine.

Review documentation when the client mix or intended account use changes. Keep records accurate and follow the relevant account policy. Do not alter payment descriptions or split transactions to avoid checks.

Use a weekly payment risk checklist before invoices go out#

A short weekly checklist is more useful than a rushed fix after funds go missing. Before you send high-priority invoices, make sure identity details, transfer details, and escalation steps are clear. If payer identity, recipient details, or transfer reference is unclear, pause and fix it first.

Check identities before you issue the invoice#

For priority invoices, confirm in one pass:

• the payer legal entity
• the intended recipient details
• the transfer reference format the client should use

Keep account-owner details, beneficiary details, and individual transfer references separate in your records so a support request can be matched to the right payment.

If you use a primary payment route and fallback route internally, define both before the due date and record who can approve a route change.

This matters most when a client pays through a team member who is not the contracting entity, or when the name you see in email differs from the name that should appear on the transfer. Resolve that mismatch before the invoice goes out, not after money is already in motion.

Build the investigation pack before anything goes wrong#

Pre-collect what you would need if funds do not arrive. Include:

• payer entity name and contact
• invoice number
• expected transfer reference
• tracking-link ownership path, if available, including who created it, who received it, and where it was shared

Open the Wise app or type wise.com into the browser yourself before logging in or responding to a request. A link that merely starts with that text can point to a lookalike domain. Wise says it will not ask for passwords, PINs, CVVs, or one-time passwords by email, text, or phone, and will not ask you to transfer money or approve a transaction to help an investigation.

You are effectively prebuilding your first response. When a payment goes missing, response quality usually depends on whether these basic details were gathered before the invoice was sent.

Set trigger points now, not in a panic#

Set internal triggers from observable events: an information request, a missed delivery estimate, or a payment you cannot reconcile. Use the account’s review estimate and case deadline where shown; neither is a guarantee that the restriction will end on that date.

• request Proof of payment when a client says funds were sent but you cannot match the transfer details
• open a case when available details still do not reconcile
• For a sent payment, investigate cancellation, recall, or refund availability with Wise; do not assume both parties agreeing can unwind a completed transfer.

The goal is a fast, documented first response, not perfect prediction. Write these trigger points in the same place as your invoice process, not in a separate emergency note nobody checks. The right move should be obvious when the problem starts, especially if someone else may need to pick up the case.

If you want a backup rail ready before the next invoice cycle, review options such as Virtual Accounts.

Keep a payment record you can reconstruct#

Keep one transfer register, one case timeline, and an action log. Each payment should be traceable to its invoice and current outcome.

For each affected payment, preserve the invoice, transfer reference, provider status, bank evidence, and case correspondence. Distinguish money still in transit from money returned so you do not request or send it twice.

Keep three lightweight artifacts#

You do not need heavy tooling. One lightweight approach is to keep these updated for each transfer event:

Use one quick test: can you trace a transfer from invoice to recipient to current status quickly without checking multiple apps? If not, your records are fragmented.

The transfer register links the invoice to the payment, the status log preserves provider and bank updates, and the action log records decisions. Keep those references together so a sent payment cannot be mistaken for an unpaid invoice and requested again.

Add policy gates before money gets sensitive#

Set one approval rule now, even if the approver is future-you. For example, require a second review for any new recipient, changed bank detail, unusually large payout, or rushed exception against the invoice, recipient record, and prior communication.

The common failure is not lack of effort. It is scattered evidence. During a provider follow-up or compliance review, fragmented screenshots and partial notes make routine payments harder to explain. If you grow into a small team, replace ad hoc chats with named approvals and one evidence pack per case: request notice, transaction details, submitted files, timestamps, and final approver.

The main takeaway for protecting cashflow#

Keep the response tied to the exact notice: answer requested information, trace affected transfers, and protect urgent bills using accessible funds. Your immediate goal is to know where each payment stands and what action is required next.

Before updating an unpaid invoice, verify the alternative account through an established channel and record the change. For a payment already sent, preserve the original reference and trace or confirm return before requesting a replacement.

Keep the invoice, provider transfer record, bank evidence, and case response together. Once money arrives or is returned, update the invoice balance and close the exception. A sent status alone is not proof that the recipient has the funds.

Review affected invoices and bills at a fixed daily time while the case is open. Record the next action and update date for each unresolved payment, then return to normal reconciliation after the restriction or closure is resolved.