Skip to content

Merchant Portal

Investigate a returned or declined payment

Find the reason and confirm what happened before another collection attempt.

Menus and available actions depend on your role and enabled services. In the local demos, use sample records only; no real payments or messages are sent.

Returns & Declines gathers problem transactions. Declines and returns are different events, so start with the actual history.

Review the exception

  1. Open Returns & Declines.
  2. Review Returned ACH and Declined separately.
  3. Match customer, amount, date, and masked method.
  4. Read Reason, then open the record for available responses, timestamps, and identifiers.
  5. Check related Transactions before requesting another payment.

A declined attempt was not approved. A returned eCheck may have appeared settled before the return arrived. A record's fee estimate is not a guarantee of final fee treatment; check the monthly statement.

Follow up

If an issuer decline code was not provided, ask the operator for available details. Do not guess the cause. Agree on another supported method only after the original outcome is clear.

For a bank return, record the return code and review your account's authorized recovery process with the operator before retrying. An unauthorized-payment dispute may also appear in Disputes and needs separate review.

Missing or incomplete records

A notice that only the first records are shown means the table is capped. Use the offered Export CSV in an enabled live account for the complete filtered set. No rows can mean no matching exceptions or an unavailable feed; check errors and freshness before concluding.

Demo exceptions are synthetic and export is blocked. For an ambiguous attempt, follow payment statuses.