## TL;DR

Related Wise integration facts from the same study: the V1 sandbox URL (api.sandbox.transferwise.tech) was deprecated June 30 2026, use api.wise-sandbox.com; 429 responses carry Retry-After plus an X-Rate-Limited-By header, so back off per the header rather than fixed sleeps. A BLOCKED notice means this quote must not back a transfer; check quote.Notices after CreateQuote and refuse to proceed on BLOCKED before calling CreateTransfer.

## Fix

1. Related Wise integration facts from the same study: the V1 sandbox URL (api.sandbox.transferwise.tech) was deprecated June 30 2026, use api.wise-sandbox.com; 429 responses carry Retry-After plus an X-Rate-Limited-By header, so back off per the header rather than fixed sleeps.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are setting up or using this Wise Platform feature.
- The symptom matches: quote with BLOCKED notice must not back a transfer.

## When NOT to use

- Unrelated Wise Platform issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Wise Platform. Source: https://github.com/larsartmann/wise-go/blob/HEAD/docs/reviews/2026-08-08_api-docs-study.md.

## Variant phrasings

### quote with BLOCKED notice must not back a transfer

## Why it happens

A Wise Platform quote comes back with a BLOCKED notice in its notices array. Using it to create a transfer fails or produces a bad transfer.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.

## Source

https://github.com/larsartmann/wise-go/blob/HEAD/docs/reviews/2026-08-08_api-docs-study.md