## TL;DR

Wise holds a transfer until the recipient's details are verified: the transfer is stuck, not lost. Open the transfer in the Wise dashboard, complete the verification step for the recipient (confirming name, account details, or identity as requested), and the transfer releases. Build recipient verification into your payout flow so transfers are never created against unverified recipients.

```text
wise transfer stuck: recipient details need verification before release
```

## Use this when

- Wise transfer is stuck awaiting recipient verification
- A first-time recipient has not been verified
- You need to release a held transfer

## Not for this skill when

- The transfer failed for insufficient balance
- The recipient details are wrong (that needs correction, not verification)
- You are debugging Wise API authentication

## Steps

1. Open the stuck transfer in the Wise dashboard and read the verification request.
   Expected: You know what Wise needs.
2. Contact the recipient and collect the required verification (details confirmation or identity as requested).
   Expected: You have what Wise asked for.
3. Submit the verification in the Wise dashboard or API.
   Expected: Verification is recorded.
4. Confirm the transfer status moves to sending.
   Expected: The hold is released.
5. Add a recipient-verification step before transfer creation in your flow.
   Expected: Future transfers do not stall.

## Tool compatibility

Wise transfers API and dashboard; recipient verification requirements vary by corridor and amount.

## Variant phrasings

### wise transfer pending recipient verification

The status-view phrasing.

### wise recipient details verification stuck

The data angle.

### wise transfer held verification

The hold framing.

## Why it happens

Wise verifies recipients to meet anti-fraud and regulatory obligations before money moves, especially on first-time or high-risk corridors. The verification hold is a compliance checkpoint: the transfer exists and the funds are earmarked, but release waits on confirmed recipient identity. This protects both Wise and the sender from misdirected payments. Completing verification is the only release path; the transfer cannot be forced through.

## Edge cases / pitfalls

- Verification requests expire: respond promptly or the transfer may be cancelled and need re-creation.
- The recipient's legal name must match their account; nicknames stall verification.
- For recurring recipients, verification persists; the stall is typically a first-payment phenomenon.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_7nEYig-59eMZm8oUJUEMHw