Outlaw Payments Declines and Error Messages

When you charge a client’s card through Outlaw Payments and the charge does not go through, you will see a short message explaining what happened. That message comes from the client’s bank (the card issuer), not from Outlaw, and the reason matters: some failures are worth retrying, while others will keep failing until the client fixes something on their end.

This guide groups the common outcomes into four plain-English buckets so you can tell at a glance what a message means, whether trying again is worth your time, and what to say to your client.

The Short Version

• The bank said no. If the bank declined the charge, retrying almost never helps. The client needs to call their bank or use a different card.
• The card details were wrong. If the card number, expiration, security code, or billing address did not match, re-enter the correct details and try again.
• Something was temporary. If the network timed out or hit a momentary processing error, waiting a little while and retrying usually works.
• Watch for duplicates. If you see a duplicate-transaction message, check whether the payment already went through before you charge again.

When to Tell Your Client

Most of the time, you are the one running the charge and your client is the one who has to fix it. When a charge is declined by the bank, you generally cannot do anything from your side, and neither can Outlaw Support: the decision is the bank’s. The fastest path is to tell your client plainly:

Your card was declined by your bank. We do not see the reason on our end, so please call the number on the back of your card and ask them to approve the charge, or give us a different card to use.

You never need to share the technical code or guess at the reason. Keep it simple, hand the problem to the person who can solve it, and offer to try a different card.

Declined by the Bank

These are the most common results, and they all mean the same thing in practice: the client’s bank chose not to approve the charge. Outlaw passed the charge along correctly; the bank turned it down. Retrying the same card usually produces the same decline, so the real fix is for the client to contact their bank or pay with another card.

• Declined (no reason given). The bank declined the charge without telling us why. This is the catch-all decline. Have the client call their bank or try a different card.
• Do not honor. The bank specifically asked us not to complete this charge. This is a firm no from the bank, not a card-data problem. The client must contact their bank.
• Insufficient funds. The account does not have enough available to cover the charge. The client can add funds, wait, or use another card. A smaller charge may go through if the client agrees to split it.
• Card not active, closed, or frozen. The card is not currently usable. It may need activation, may have been closed, or may be frozen due to a fraud alert. The client needs to call their bank.
• Card reported lost or stolen. The card was flagged as lost or stolen and cannot be used. The client must use a different card and follow up with their bank.
• Restricted card. The bank has placed limits on what this card can be used for (by location, type of business, or spending limits), or the card is blocked. The client should ask their bank to allow the charge.
• Card not permitted for this charge. The bank does not allow this kind of charge on this card under the cardholder’s terms. The client should contact their bank.
• Call your bank. The bank wants the cardholder to call them before the charge is retried. Ask the client to call, then try again once the bank clears it.
• Limit reached. The card has hit a daily limit, a per-charge limit, or a similar cap. Trying again the next day, or using a different card, is usually the answer.

For every item above, the realistic next step is the same: the client contacts their bank, or you run the charge on a different card. Re-running the identical charge on the identical card rarely changes the outcome.

Card Data Problems

These failures mean something about the card entry did not match what the bank has on file. Unlike a bank decline, you can fix most of these yourself by checking the card details and re-entering them.

• Expired card. The card’s expiration date has passed. Ask the client for a current card and remove the expired payment method.
• Wrong card number. The card number entered is not valid. Re-enter it carefully, digit for digit.
• Security code (CVV) does not match. The three- or four-digit code on the card does not match what the bank expects. Re-enter the code from the card. For American Express, it is the four-digit code on the front.
• Billing address does not match (AVS). The street address or ZIP/postal code entered does not match the address the bank has on file for the card. Confirm the exact billing address with the client and re-enter it. A charge can still be declined when the address does not match, even if the card itself is good.
• Expiration not valid for this card. The expiration date entered does not fit the card. The card may have been reissued with the same number but a new expiration date; ask the client for the current expiration.

When you see one of these, double-check the details with your client and re-enter them before retrying. If the details are correct and it still fails, treat it like a bank decline and have the client contact their bank.

Temporary and Processing Issues

These are the failures where trying again is the right move. They are usually short-lived: a network hiccup, a momentary system error, or a processor that was briefly unavailable. Wait a short while and run the charge again.

• Try again later / network unavailable. The processing network or the client’s bank was momentarily unreachable. Wait a few minutes and retry.
• Processing error / system error. A temporary error occurred while completing the charge. Retry shortly. If it keeps happening, contact Outlaw Support.
• Re-submit the transaction. The charge could not be processed as submitted. Double-check the card fields are correct, then try again.
• Batch closed for the day. The day’s processing batch has already closed. Run the charge again a little later.

If a charge in this group fails repeatedly over a longer stretch, it stops being “temporary.” At that point, reach out to Outlaw Support so we can look into it.

Duplicate Transaction

A duplicate transaction message is a safeguard, not a true failure. It means a charge with the same amount and card was submitted more than once in a short window, so the system stopped the second one to protect your client from being charged twice.

Before you do anything else, check whether the first charge already succeeded. Look at the matter’s payments or the payment history. If the payment is there, you are done, do not charge again. If you are certain this is a genuinely separate charge (for example, a second invoice for the same amount), wait a short while and submit it again.

A Note on Verification Prompts

Some payment systems ask the cardholder to complete an extra verification step (a code from their bank, sometimes called 3D Secure). Outlaw Payments does not use this step, so your clients will not be asked to verify a charge that way. If a client expects a verification prompt and does not get one, that is normal, nothing is wrong.

When to Contact Outlaw Support

Most declines are between your client and their bank, and Support cannot override a bank’s decision. Reach out to Outlaw Support when:

• A temporary or processing error keeps happening over a longer period and retrying does not clear it.
• You believe a charge succeeded but it is not showing up, or a client was charged and you cannot find the payment.
• A message points to a setup issue on your account (for example, a payment type that is not enabled) rather than the client’s card.

When you contact Support, include the date and time of the attempt, the amount, and the message you saw. That lets us match it to the right charge quickly.