Skip to main content

Why your payment was declined (and how to fix it)

Read the decline code, fix the card, and get your Recruiterflow subscription back on track.

Written by Amritanshu Anand

If your Recruiterflow subscription payment failed, the error message includes a decline code from the card issuer. Most declines are quick fixes you can handle yourself — usually a card update in your billing settings. Here's how to read the code and what to do next.

What to do first

  1. Go to SettingsBilling and confirm the card on file is current — correct number, CVC, expiry, and ZIP/postal code.

  2. If everything looks right, retry the payment. Some declines are temporary and clear on the second attempt.

  3. If the retry fails, replace the card with a different one. A card from a different issuer is often the fastest fix.

  4. Still failing? Contact your card issuer — only they can lift a block on their end.

Common decline reasons

Something's wrong with the card details. Codes: incorrect_number, incorrect_cvc, incorrect_zip, invalid_expiry_year, expired_card. Re-enter the card details carefully or use a different card.

The issuer blocked the charge. Codes: do_not_honor, generic_decline, call_issuer, transaction_not_allowed. Your bank declined the charge but didn't say why. Call the number on the back of the card and ask them to allow it.

Not enough funds or over the limit. Codes: insufficient_funds, card_velocity_exceeded, withdrawal_count_limit_exceeded. Use a different card or wait for funds to settle.

The card needs extra verification. Code: authentication_required. Re-run the payment and complete the 3D Secure prompt the bank shows you.

The card was reported lost, stolen, or restricted. Codes: lost_card, stolen_card, pickup_card, restricted_card, fraudulent. Switch to a different card.

Temporary processor issue. Codes: processing_error, issuer_not_available, try_again_later. Wait a few minutes and retry.

Practical example

A recruiter sees a "payment failed: do_not_honor" banner at the top of Recruiterflow. The card is valid and not expired. They call the bank, who confirms a fraud flag was tripped on a recurring SaaS charge and lifts it. The recruiter goes to SettingsBilling, retries the payment, and the subscription clears.

When to contact Recruiterflow support

Reach out via in-app chat if the card is valid, the issuer confirms the charge should go through, but the payment still fails — or if your account has been suspended for non-payment after you've already updated the card. Include the decline code you saw so support can trace the attempt.

Things to know

  • Decline codes come from the card issuer, not from Recruiterflow. The message reaches you through our payment processor.

  • Saving a new card in SettingsBilling doesn't automatically retry the failed payment — trigger a new payment after the card is saved.

  • Repeated declines on the same card can lead to a temporary account hold. Replacing the card clears the hold.

Did this answer your question?