Western Union Error Codes -

Western Union Error Codes — Complete Report

✅ Complete "Full Verification" immediately.

• Upload driver’s license + selfie.
• Link a bank account (not just a credit card).
• Add your phone number and confirm it.

Scenario A: You are trying to pay online with a credit card.

| Error Code | Likely Cause | 5-Minute Fix | | :--- | :--- | :--- | | E2065 | Bank decline | Call bank | | AMOUNT_EXCEEDS_LIMIT | Over daily cap | Send smaller amount | | CVV_INCORRECT | Typo | Re-enter CVV (3 digits on back) |

When to Give Up and Use an Alternative

Sometimes, Western Union’s system will simply never accept your transaction due to your bank’s risk profile, your country’s regulations, or your personal credit history. If you have tried three different payment methods, two different channels (app and in-person), and called support twice without resolution, accept the block as permanent. western union error codes

In that case, consider:

• MoneyGram (similar service, different risk algorithms)
• Remitly (better for smaller amounts and mobile wallets)
• PayPal/Xoom (good for bank-to-bank)
• Wise (formerly TransferWise) (best for mid-sized transfers and transparent exchange rates)

3. Common error codes (examples, typical message, causes, and steps)

Note: code values below are representative patterns (numeric or alphanumeric) observed across payment systems; exact vendor codes vary. Western Union Error Codes — Complete Report ✅

1. 100 — INVALID_REQUEST

• Message: "Invalid request parameters"
• Cause: Missing required fields or malformed JSON/parameters.
• Troubleshooting: Validate payload against API schema; confirm required fields (amount, currency, sender/receiver IDs, country codes). Return detailed field-level errors to client.

2. 101 — AUTH_FAILED / INVALID_CREDENTIALS

• Message: "Authentication failed"
• Cause: Wrong API key, expired token, clock skew for signed requests.
• Troubleshooting: Verify credentials, refresh tokens, check server time & signature. Rotate keys if compromised.

3. 102 — PERMISSION_DENIED

• Message: "Insufficient permissions"
• Cause: Merchant account lacks permission for action (e.g., cross-border transfers).
• Troubleshooting: Check account settings, scopes, and entitlements.

4. 200 — AMOUNT_EXCEEDS_LIMIT

• Message: "Amount exceeds allowed limit"
• Cause: Sender or channel limit (per transaction/day).
• Troubleshooting: Inform user of permitted limits and next steps (split payments, increase KYC).

5. 201 — INSUFFICIENT_FUNDS / CARD_DECLINED

• Message: "Card declined"
• Cause: Issuer declined, insufficient balance, suspected fraud.
• Troubleshooting: Advise user to contact bank or use alternative funding method; log issuer decline code.

6. 300 — AML_KYC_REQUIRED / VERIFICATION_NEEDED

• Message: "Identity verification required"
• Cause: Missing KYC, name mismatch, watchlist hit, enhanced due diligence needed.
• Troubleshooting: Request required documents, perform manual review, or block if sanctioned.

7. 301 — SANCTIONS_MATCH / BLOCKED

• Message: "Transaction blocked for compliance reasons"
• Cause: Sanctions/screening match for sender or receiver.
• Troubleshooting: Escalate to compliance team; do not provide sensitive screening details to customers beyond standard messaging.

8. 400 — ROUTING_FAILURE / BENEFICIARY_ACCOUNT_INVALID

• Message: "Beneficiary account invalid or unreachable"
• Cause: Wrong bank details, closed account, incompatible rail.
• Troubleshooting: Validate beneficiary details, retry with corrected info, fallback rails if available.

9. 500 — GATEWAY_TIMEOUT / EXTERNAL_SERVICE_UNAVAILABLE

• Message: "Service temporarily unavailable"
• Cause: Downstream provider outage, network partitions.
• Troubleshooting: Implement retries with exponential backoff, circuit breaker, and clear customer messaging with estimated retry/timeout behavior.

10. 501 — DUPLICATE_TRANSACTION

• Message: "Duplicate transaction detected"
• Cause: Same idempotency key or repeated request within dedup window.
• Troubleshooting: Display prior transaction status, allow refund/cancel if needed.

11. 900 — INTERNAL_SERVER_ERROR / UNKNOWN_ERROR

• Message: "An unexpected error occurred"
• Cause: Unhandled exception, DB error, configuration issue.
• Troubleshooting: Capture full diagnostic logs, generate incident, return correlation ID to user for support.

12. DEVICE_OFFLINE / PRINTER_ERROR (agent terminals)

• Message: "Terminal offline / Printer error"
• Cause: Network down, paper jam.
• Troubleshooting: Advise agent on reconnect steps; provide manual fallback receipt process.

---