Unicorn Currencies
Unicorn Currencies
How it worksBusiness AccountsFXPricingFAQOpen Account
Home / Payment Problems / Payment held for purpose code
Payment problem — Document hold

A payment is held because of a purpose code issue

You are in the right place if a payment is held because of a purpose code issue.

The issue is usually not whether the payment was sent.

The bank is waiting for a document, purpose, declaration, or trade explanation before it releases the funds.

A document hold is rarely about producing more paper for its own sake. The bank is trying to connect the payment to a clear commercial event: who paid, who receives, what goods or services are involved, and why the amount makes sense. For this case, gather correct business purpose, invoice, goods or services, country requirements, and bank instruction. That gives the bank a clean release pack and gives treasury enough context to challenge a vague or repeated document request.

01What it usually meansThe bank is usually trying to connect the payment to the underlying trade: invoice, purpose, sender, beneficiary, goods or services, and amount. In this case, a payment is held because of a purpose code issue. In practice, the receiving side may need the payment classified correctly for reporting before crediting funds.
02Evidence neededPrepare a clean pack with invoice, purpose of payment, goods or services description, sender and beneficiary relationship, source of funds or source of wealth if requested, and trade explanation. The details should match the beneficiary, invoice, payment reference, currency, amount, and commercial purpose.
03What not to doDo not send inconsistent or incomplete explanations to different banks or counterparties.
04Correct next actionRespond with one structured document pack, confirm which bank owns the release review, and note the timeline. Escalate when the request is unclear, repeated after documents were supplied, or no bank will own the release status. The immediate goal in this case is to provide a purpose classification that matches the underlying transaction.
05How Unicorn Currencies helpsUnicorn Currencies helps organise the payment proof, references, beneficiary details, supplier messages, and timeline so the next action is clear. Depending on the payment state, that may mean waiting inside the rail window, requesting a trace, preparing a proof pack, supporting escalation, coordinating an amendment, or preparing a recall request. Unicorn Currencies does not control SWIFT, correspondent banks, beneficiary banks, or partner banks, and cannot guarantee recall, recovery, release, or bank action.
A payment is held because of a purpose code issue usually means the bank needs to connect the payment to a real commercial transaction before funds are released. Start by matching the payment to the invoice, purpose, sender, beneficiary, amount, currency, and trade context, then respond with one clean document pack instead of disconnected attachments.
Related payment states