COMPLIANCE_REVIEW_REJECTED error

​

What happened

• COMPLIANCE_HOLD — funds frozen pending a manual review, not a clean decline.
• COMPLIANCE_REJECTED — a payout’s supporting documents were rejected; this one is retryable (it arrives on transaction.rejected — upload new documents and resubmit).

{
  "type": "COMPLIANCE_REVIEW_REJECTED",
  "title": "Transaction declined — compliance review required",
  "status": 422,
  "detail": "This transaction could not be completed due to a regulatory compliance review.",
  "resolution": "Contact support. This transaction cannot be retried without a compliance review.",
  "docs": "/errors#compliance-review-rejected",
  "instance": "/v2/transactions/txn_034A0gCCVmVhsfuR8SfVwM",
  "correlationId": "00469ea4-52c1-4ffa-bd05-9f28b236a5fe",
  "timestamp": "2026-01-15T09:30:00.000Z"
}

​

Common causes

• Compliance review outcome — the transaction or counterparty returned a signal during compliance screening that prevents completion
• Transaction profile — the amount, corridor, or counterparty combination triggered a compliance rule

​

Recovery

curl -X GET https://api.conduit.financial/v2/transactions/txn_034A0gCCVmVhsfuR8SfVwM \
  -H "x-api-key: YOUR_API_KEY"

​

Prevention

• Handle transaction.failed with this code — branch on failureCode === 'compliance_review_rejected' to surface a neutral “this transfer could not be processed” message; never disclose the compliance reason to the end user
• Do not retry automatically — retrying without investigation does not change the outcome

​

Related webhooks

{
  "type": "transaction.failed",
  "data": {
    "transactionId": "txn_034A0gCCVmVhsfuR8SfVwM",
    "failureCode": "compliance_review_rejected"
  }
}

​

Related endpoints

• GET /v2/transactions/:id — read transaction state