SWIFT statuses

Learn about the compliance document requirements for international SWIFT payouts.

Overview

All international SWIFT payouts require compliance document submission before funds are processed. Payouts remain on hold until documents are submitted and approved by our compliance team.

Why document verification?

International transfers via SWIFT require additional compliance documentation to meet regulatory requirements. This verification process ensures all cross-border payments are properly documented and compliant with international banking standards.

Payout flow for SWIFT

When you create a SWIFT payout, the flow is:

  1. Payout created → Status is on_hold
  2. Waiting for documentstracking_documents.status: waiting_documents
  3. Documents submittedtracking_documents.status: compliance_reviewing
  4. Compliance approved → Payout proceeds to processing, fiat is sent
  5. Compliance rejected → Status returns to waiting_documents, submit new documents

Providing documents upfront

You can skip the waiting step by providing documents when creating the quote:

Bash

When documents are provided upfront, the payout is created directly in compliance_reviewing status.

Submit payout documents endpoint

Bash

Fields:

FieldTypeRequiredDescription
transaction_document_typestringYesinvoice, contract, purchase_order, delivery_slip, customs_declaration, bill_of_lading, first_party, others
transaction_document_idstringConditionalDocument identifier (e.g., invoice number). Not required when transaction_document_type is first_party
transaction_document_filestringConditionalURL to the uploaded document. Not required when transaction_document_type is first_party
descriptionstringNoPayment description/memo (max 128 chars)

Tracking documents field

All payout responses and webhooks now include tracking_documents:

JSON

Status values

StatusDescription
waiting_documentsAwaiting document submission
compliance_reviewingDocuments submitted, under review
nullDocuments approved, payout processing

Step values

StepDescription
processingDocument verification in progress
completedDocument verification complete

Webhook examples

Documents submitted

JSON

Compliance approved

JSON

Compliance rejected

JSON

Timeouts

EventTimeout
Document submission30 days from payout creation
Compliance review8 days from document submission

Accepted documents

  • Invoice
  • Contract
  • Purchase Order
  • Delivery Slip
  • Customs Declaration
  • Bill of Lading
  • First Party
  • Others

Important: Documents must show the relationship between the sender and the receiver. If the document doesn't clearly establish this relationship, the payment will be rejected.

First party payouts

If you are sending funds to your own bank account (i.e., the sender and the receiver are the same person or entity), use first_party as the transaction_document_type. When first_party is selected, transaction_document_id and transaction_document_file are not required.

This is common when consolidating funds across your own accounts internationally.