Troubleshooting Seller Pay-outs

Known common reasons payouts fail

Common Pay-Out Issues and Suggested Responses

Use this page as a support response bank for common payout failures, pending states, and post-acceptance returns.

1) Beneficiary account data problems

Invalid or incomplete IBAN/account number

What it means
The beneficiary bank account details failed validation.

What to check

  • IBAN/account number format
  • Missing characters
  • Country format rules

Your payout could not be processed because the beneficiary account number/IBAN appears invalid or incomplete.
Please verify the full account details exactly as issued by the beneficiary bank and submit the payout again.

Wrong or missing BIC/SWIFT (where required)

What it means
Required routing identifier is missing or incorrect.

What to check

  • Whether the destination country/rail requires BIC/SWIFT
  • BIC/SWIFT format and value

The payout was rejected because the BIC/SWIFT code is missing or invalid for this transfer route.
Please confirm the correct BIC/SWIFT with the beneficiary bank and try again.

Beneficiary name mismatch

What it means
The beneficiary name does not sufficiently match the receiving bank records.

What to check

  • Legal/account-holder name
  • Abbreviations, punctuation, transliteration differences

The beneficiary name did not match the receiving bank’s account records.
Please update the beneficiary name to the exact account-holder name registered with the bank, then resubmit.

Closed, blocked, or non-creditable recipient account

What it means
The destination account cannot receive funds.

What to check

  • Account status with the beneficiary bank

The receiving bank could not credit the beneficiary account (account may be closed, blocked, or not eligible for incoming transfers).
Please provide an active creditable account and submit a new payout request.


2) KYC/KYB or compliance not complete

Seller wallet/account not fully verified

What it means
Account verification status does not allow payouts yet.

What to check

  • Verification status
  • Outstanding onboarding steps

Payouts are currently unavailable because account verification is not complete.
Please complete the required KYC/KYB checks in your account, and payouts will be enabled once verification is approved.

Missing or expired compliance documents

What it means
Required compliance documents are missing, outdated, or expired.

What to check

  • Missing docs
  • Document expiry dates

Your payout is blocked because one or more compliance documents are missing or expired.
Please upload valid, up-to-date documents in the verification section, then retry the payout.

Account under review/restricted/suspended

What it means
Compliance or operational review is ongoing.

What to check

  • Restriction/review flags
  • Any pending requests for information

Payouts are temporarily unavailable while your account is under review/restricted.
If additional information is required, we’ll notify you in your dashboard. Payout capability is restored once the review is cleared.

Payout blocked by AML/sanctions screening

What it means
Transaction or profile triggered regulatory screening.

What to check

  • Screening outcome
  • Escalation path/manual review requirement

This payout has been held due to regulatory screening controls.
Our compliance team may require additional information before release. We’ll contact you if further documents are needed.


3) Insufficient or unavailable balance

Insufficient wallet balance

What it means
Available funds are lower than the requested payout amount (and fees if applicable).

What to check

  • Available vs total balance
  • Pending debits

The payout could not be created because your available wallet balance is insufficient.
Please lower the payout amount or wait until additional funds are available.

Funds reserved/locked (reserve, dispute, security hold)

What it means
Part of the balance is not currently payout-eligible.

What to check

  • Hold reason
  • Release timeline

Some funds in your wallet are currently reserved and cannot be paid out yet (e.g., reserve/dispute/security hold).
Once those funds are released, you can submit the payout again.

Payout requested before settlement/clearing completes

What it means
Funds are not yet cleared for payout.

What to check

  • Settlement timeline by payment method

The payout was requested before funds completed settlement/clearing.
Please retry after the settlement window has passed.

Currency mismatch (wallet vs payout currency)

What it means
Available wallet funds are in a different currency than requested payout.

What to check

  • Wallet currency
  • Payout currency
  • Conversion capability (if enabled)

The payout currency does not match the available wallet funds.
Please submit the payout in the wallet’s available currency (or perform currency conversion if enabled).


4) Amount and limit violations

Payout amount below minimum or above maximum

What it means
The requested amount is outside the configured thresholds.

What to check

  • Account min/max payout settings

The payout amount is outside the permitted range for your account.
Please submit an amount within your configured minimum and maximum payout limits.

Daily/weekly/monthly payout limit exceeded

What it means
Period-based cumulative cap has been reached.

What to check

  • Current period usage
  • Limit reset timing

Your payout could not be processed because the period limit (daily/weekly/monthly) has been reached.
Please retry after the limit resets, or contact support if you need a limit review.

Velocity/frequency limits exceeded

What it means
Too many payout attempts in a short time window.

What to check

  • Recent payout attempt volume
  • Cooldown period

We detected too many payout requests in a short period, so this request was blocked by velocity controls.
Please wait briefly and try again.

Precision/rounding error (invalid minor units)

What it means
Amount precision is invalid for the currency.

What to check

  • Decimal places for currency minor unit rules (e.g., 0-decimal currencies)

The payout amount format is invalid for this currency (minor unit/decimal precision issue).
Please correct the amount format and resubmit.


5) Status/lifecycle timing issues

Account not in payout-eligible status (e.g., not ACTIVE)

What it means
Source account status does not allow payout initiation.

What to check

  • Current account lifecycle status

Payouts are not available from the current account status.
Please ensure the account is in an eligible status (for example, ACTIVE) before retrying.

Duplicate payout attempt while previous payout is processing

What it means
A matching payout is already in progress.

What to check

  • Existing payout status
  • Idempotency key usage

A payout for the same instruction is already being processed, so this duplicate request was not accepted.
Please wait for the current payout to complete before creating a new one.

Cut-off time missed (execution deferred)

What it means
Request arrived after banking cut-off and moved to the next processing window.

What to check

  • Submission timestamp
  • Route/bank cut-off schedule

Your payout was submitted after the banking cut-off time, so execution was deferred to the next processing window.
This can appear as pending temporarily.

Weekend/bank holiday delay

What it means
Processing delayed due to non-business day schedules.

What to check

  • Banking calendar for destination route

The payout is delayed due to weekend/bank holiday processing schedules.
It remains in queue and will continue on the next banking business day.


6) Technical/API request issues

Missing required fields or invalid parameter formats

What it means
Payload validation failed at API level.

What to check

  • Required fields
  • Data types/enums
  • Country-specific mandatory fields

The payout request could not be accepted because one or more required fields are missing or incorrectly formatted.
Please validate your payload against the API specification and try again.

Idempotency misuse

What it means
Idempotency key reused incorrectly or malformed.

What to check

  • Key uniqueness per payout intent
  • Consistent reuse only for safe retries of same intent

The request was rejected due to idempotency key usage.
Please use a unique idempotency key per payout instruction and avoid reusing keys across different payouts.

Authentication/authorisation error

What it means
Token/credentials/scope problem.

What to check

  • Token validity/expiry
  • Permission scopes
  • API credentials configuration

Authentication or authorization failed for this payout request.
Please verify your API credentials, token validity, and permission scopes, then retry.

Signature/hash validation failure

What it means
Request integrity check failed.

What to check

  • Signing secret
  • Canonical payload string
  • Timestamp window

The request could not be verified due to signature/hash validation failure.
Please review your request-signing process and retry with a correctly signed payload.

Endpoint/environment mismatch (sandbox vs production)

What it means
Mixed credentials/endpoints from different environments.

What to check

  • Base URL
  • API keys
  • Account/wallet identifiers

The request appears to mix environments (e.g., sandbox credentials with production endpoint).
Please ensure keys, endpoint, and account identifiers all belong to the same environment.


7) Banking rail and country constraints

Unsupported payout rail for country/currency

What it means
Selected route is not available for that destination corridor.

What to check

  • Supported rails per country/currency pair

This payout route is not supported for the selected country/currency combination.
Please use a supported payout method for that destination.

Local clearing restriction or correspondent bank rejection

What it means
Downstream banking network rejected the transfer.

What to check

  • Return/reject codes
  • Routing and beneficiary details

The transfer was rejected by downstream banking infrastructure (local clearing/correspondent bank).
Please verify beneficiary details and retry, or use an alternative payout route where available.

Country-specific beneficiary fields missing

What it means
Destination-country mandatory fields are not satisfied.

What to check

  • Local mandatory fields (branch code, tax ID, etc., depending on country)

The payout could not be processed because required beneficiary fields for the destination country are missing or invalid.
Please complete all country-specific fields and submit again.

Destination bank rejects transaction type

What it means
Receiving bank policy does not accept this transfer type/purpose.

What to check

  • Allowed transfer purpose/type at destination bank

The destination bank rejected this transaction type.
Please verify accepted transfer types/purpose requirements with the beneficiary bank and retry with compliant details.


8) Risk and fraud controls

Transaction flagged by risk engine

What it means
Behavioural/velocity patterns triggered risk controls.

What to check

  • Risk event details
  • Escalation or manual review requirement

This payout was held by risk controls due to unusual transaction behavior.
Our team may require additional checks before release.

Device/IP/geography inconsistency

What it means
Security profile mismatch triggered review.

What to check

  • Recent login/access context
  • Security challenge completion

The payout is temporarily on hold because of a security consistency check (device/IP/location pattern).
Please complete any requested security verification steps.

Account takeover suspicion

What it means
Potential compromise detected; payout freeze applied for protection.

What to check

  • Security alerts
  • Credential/session integrity

We detected potential account security risk and temporarily froze payout activity to protect funds.
Please contact support immediately to complete account security verification.

Manual risk review required

What it means
Automated controls escalated this payout to manual review.

What to check

  • Review queue status
  • Requested supporting evidence

This payout requires manual risk review before release.
If additional documentation is needed, we’ll notify you. Processing continues once review is completed.


9) Return/reject after initial acceptance

Bank accepts then later returns funds (return code / R-transaction)

What it means
Transfer was initially accepted but later returned by banking network.

What to check

  • Return code/reference
  • Reconciliation status

The payout was initially accepted but later returned by the banking network.
We are reconciling the return reason and will share the next action (typically beneficiary detail correction and resubmission).

Beneficiary details changed between initiation and execution

What it means
Details were no longer valid when execution occurred.

What to check

  • Beneficiary updates post-initiation
  • Latest bank coordinates

The payout could not complete because beneficiary account details changed between initiation and execution.
Please confirm the latest bank details and submit a new payout request.

Intermediate bank rejection with generic reason

What it means
Intermediary bank rejected with limited detail.

What to check

  • Any available reject reference
  • Full validation of routing + beneficiary fields

The payout was rejected by an intermediary bank with a generic return reason.
Please verify all beneficiary and routing details and retry; if available, use an alternative payout path.