Skip to main content

Credit card error / decling codes

Updated today

CODE

PROCESSOR

CUSTOMER DISPLAYED REASON

EXPLANATION

1

CCBill

Bank Decline

A bank decline means the issuing bank refused the transaction.

Common reasons:

  • Insufficient funds.

  • Card expired.

  • Card reported lost or stolen.

  • Bank security or fraud prevention block.

  • Card not authorized for online or international use.

Fix:

  • Confirm there are enough funds available.

  • Check that the card hasn’t expired.

  • Contact the bank to lift restrictions or verify the charge.

  • Try a different card or payment method.

2

CCBill

Expired Card

An expired card error means the expiration date entered doesn’t match the bank’s records or the card is no longer valid.

Common causes:

  • The card has already expired.

  • Typo in the expiration month or year.

  • The bank issued a replacement card with a new expiry date.

Fix:

  • Double-check the expiration date entered.

  • Use a valid, non-expired card.

  • Contact the bank if unsure of the current expiry date.

4

CCBill

Pickup card (lost or stolen)

Meaning: The issuing bank has flagged the card as lost, stolen, or otherwise restricted.

Fix:
Customer should contact their bank for clarification

Use a different, valid payment card

5

CCBill

Do Not Honor

Meaning: The issuing bank refused the transaction but didn’t provide a specific reason.

Possible causes:
- General bank decline
- Suspicion of fraud or unusual activity
- Bank restrictions on certain merchants or transaction types

Fix:
- Ask the customer to contact their bank to approve the charge
- Suggest trying a different card or payment methodDo Not Honor

51

CCBill

Insufficient Funds

Meaning: The cardholder’s account does not have enough available funds to cover the transaction.

Fix:
- Ensure sufficient funds are available
- Try again after depositing funds
- Use another card or payment method

54

CCBill

Expired Card

Meaning: The card’s expiration date is invalid or the card has expired.

Fix:

- Double-check the expiration date entered

- Use a valid, non-expired card

- Contact the issuing bank if unsure about the current expiry date

57

CCBill

Transaction not permitted – Card restricted

Meaning: The issuing bank has blocked the type of transaction being attempted (e.g., online, international, or merchant-specific restrictions).

Fix:

- Ask the cardholder to contact their bank to allow the transaction

- Suggest using another card or payment method

65

CCBill

Activity limit exceeded

Meaning: The cardholder has exceeded a withdrawal/transaction limit set by their bank (e.g., daily or monthly spending cap).

Fix:

- Ask the cardholder to contact their bank to lift or adjust the limit

- Retry the transaction later

- Use another card or payment method

93

CCBill

Transaction cannot be completed. Violation of law

Meaning: The issuing bank blocked the transaction because it considers it invalid under regulations, or it violates the bank’s policies.

Fix:

- Cardholder should contact their bank for clarification

- Try a different card or payment method

7

CCBill

Pickup card (special condition)

Meaning: The issuing bank has blocked the card, often due to it being reported lost, stolen, or restricted.

Fix:

- Cardholder should contact their bank for details

- Use a different, valid payment card

41

CCBill

Lost Card – Pickup Card

Meaning: The issuing bank has flagged the card as lost and blocked its use.

Fix:

- Cardholder should contact their bank immediately

- Use a different, valid card for the transaction

43

CCBill

Stolen Card – Pickup Card

Meaning: The issuing bank has reported the card as stolen and blocked its use.

Fix:

- Cardholder must contact their bank for assistance

- Use another valid card or payment method

R0 & R1

CCBill

Stop Payment Order

Meaning:

The cardholder has instructed their bank to stop recurring billing with this merchant.

R0: Customer requested to stop a single recurring payment.

R1: Customer requested to stop all recurring payments with the merchant.

Fix:

- The cardholder must contact their bank if this was done in error.

- Use another valid card or payment method if they wish to continue service.

12

CCBill

Invalid Transaction

The processor rejected the request because the submitted data was incorrect or incomplete.

Possible causes:

  • Wrong or missing card number, CVV, or expiration date.

  • Invalid or unsupported currency.

  • Corrupted or incorrectly formatted request sent to CCBill.

  • Transaction type not supported by the card.

Fix / Next Steps:

  • Double-check the card details.

  • Make sure the billing currency and country are supported.

  • If you’re the merchant, verify your integration/API request format with CCBill.

  • If the customer still has issues, suggest trying a different card.

13

CCBill

Invalid Amount

The transaction was declined because the purchase amount was missing, set to zero, or outside the allowed limits.

Causes:

  • The amount field wasn’t sent correctly in the request.

  • The amount was 0.00 or less.

  • The amount exceeded the processor’s maximum limit.

  • A formatting error occurred (e.g., commas instead of decimals).

Fix:

  • Ensure the transaction request includes a valid, non-zero amount.

  • Use the correct format (e.g., 12.34, not 12,34).

  • If you’re the merchant, check your integration or API request.

  • If you’re the customer, retry using the correct package or price point.

14

CCBill

Invalid Card Number (no such number)

The transaction was rejected because the credit/debit card number entered is not valid.

Causes:

  • The card number was entered incorrectly.

  • Extra spaces, characters, or missing digits were included.

  • The card isn’t recognized by the payment network.

Fix:

  • Re-enter the card number carefully, without spaces or dashes.

  • Ensure the card is valid and supported by CCBill.

  • If it still fails, try a different card.

15

CCBill

No such issuer

The transaction was declined because the first digits of the card number (the BIN) don’t match any recognized card issuer.

Causes:

  • The card number was mistyped.

  • The card is invalid or unsupported.

  • The card issuer isn’t recognized in the processing network.

Fix:

  • Ask the customer to carefully re-enter the card number.

  • If it still fails, suggest trying a different card.

  • As the merchant, make sure your integration isn’t altering the card number before submission.

19

CCBill

Re-enter transaction

This error means the processor couldn’t complete the authorization, usually due to a temporary communication or formatting issue.

Causes:

  • A glitch while transmitting the request.

  • Timeout or network error during authorization.

  • Incorrectly formatted data in the request.

Fix:

  • Retry the transaction.

  • If you’re the merchant, verify that your integration request is correctly formatted.

  • If the customer continues to see this error, advise them to try again later or use a different card.

28

CCBill

File update file locked out

This error means the update request couldn’t be processed because the file or subscription record is currently locked.

Causes:

  • Another update is already being processed on the same record.

  • A temporary system lock was applied to avoid conflicts.

  • The record is flagged for review or in a restricted status.

Fix:

  • Wait a short time and try again (locks are often temporary).

  • If it continues, contact CCBill Merchant Support to release the lock or check the record’s status.

  • Ensure you’re not sending multiple update requests at the same time for the same subscription.

58

CCBill

Transaction not permitted to terminal

The card issuer blocked the payment because this type of purchase isn’t allowed for the card.

Causes:

  • The bank/card issuer does not allow online or adult-related transactions.

  • The card has restrictions based on merchant category codes (MCC).

  • The transaction type isn’t permitted (e.g., cross-border or recurring billing).

Fix:

  • Ask the customer to contact their bank to request approval for this type of purchase.

  • Suggest trying a different card or an alternative payment method.

  • As the merchant, confirm your account setup and MCC are correct with CCBill.

62

CCBill

Restricted card

The card issuer declined the payment because the card isn’t allowed for this type of merchant or transaction.

Causes:

  • The bank has blocked the card for adult, online, or international transactions.

  • Restrictions are in place for certain merchant category codes (MCCs).

  • The card may only be valid for domestic use.

Fix:

  • Ask the customer to contact their bank to check if restrictions can be removed.

  • Suggest using another card (credit/debit) or an alternative payment method.

  • As the merchant, verify with CCBill that your MCC setup is correct.

63

CCBill

Security violation

The card issuer declined the payment because the CVV/CVC security code didn’t match what they have on file.

Causes:

  • The CVV (3-digit Visa/Mastercard or 4-digit Amex) was mistyped.

  • The issuer flagged the code as incorrect.

  • The card data may no longer be valid.

Fix:

  • Ask the customer to carefully re-enter the CVV/CVC.

  • If it’s correct and still declined, suggest using another card.

  • If the problem continues, the customer should contact their bank.

91

CCBill

Issuer or switch is inoperative

This error means the card issuer’s system (or the network between CCBill and the issuer) was unavailable, so the payment couldn’t be authorized.

Causes:

  • The customer’s bank network was temporarily down.

  • Communication failure between CCBill and the issuer.

  • Issuer offline for maintenance or experiencing an outage.

Fix:

  • Ask the customer to retry after a few minutes.

  • If it still fails, suggest another card or payment method.

  • No action is needed from the merchant—this is usually on the issuer’s side.

96

CCBill

System malfunction

Error 96: Transaction could not be processed due to a temporary issue with the card network, issuer, or processor.

Causes may include:

  • A technical error on the bank or processor side.

  • Timeout or communication failure during processing.

  • In rare cases, malformed transaction data.

Fix:

  • Ask the customer to retry after a short wait.

  • If the error continues, suggest another card or payment method.

  • As the merchant, if multiple customers encounter this at the same time, contact CCBill support to confirm.

CV

CCBill

Card Verification Error

The CVV/CVC security code you entered didn’t match what your bank has on file.

This can happen if:

  • There was a typo when entering the CVV.

  • The card is old or damaged, and the code is hard to read.

  • The bank declined it due to a mismatch or possible fraud flag.

What to do:

  • Re-enter the CVV carefully.

  • Make sure the card is valid and active.

3

CCBill

Invalid merchant

This error means the merchant account details are invalid or not recognized by CCBill.

It can happen if:

  • The account is closed or suspended.

  • The account number or sub-account is incorrect.

  • The payment link is outdated or misconfigured.

Fix: The merchant should contact CCBill to confirm the account status and update the correct account/sub-account details in their payment settings.

6

CCBill

Error

Your bank has placed restrictions on this card, so the payment couldn’t go through.
This can happen if:

  • The card isn’t allowed for international or online use.

  • The bank blocked it as a high-risk transaction.

  • Spending or transaction limits were exceeded.

What you can do:

  • Contact your bank to ask why the transaction was blocked.

  • Try another payment method (different card, prepaid card, or other option).

  • If this is for a subscription, confirm your card allows recurring billing.

8

CCBill

Honor with identification

Your bank has requested extra identification before approving this transaction.

What you can do:

  • Contact your bank to ask why the transaction needs verification.

  • If you prefer not to wait, try using another card or payment method.

  • Once your bank confirms your details, the payment should go through.

9

CCBill

Request in progress

“Request in Progress” means your payment is still being processed.
It’s a temporary status, not a decline. Usually, the bank just needs a little extra time to respond.

What to do:

  • Wait a moment and check again.

  • If it doesn’t go through, please try the payment again.

10

CCBill

Approved for partial amount

CCBill Response: “Approved for Partial Amount”

  • The bank only approved part of the charge (e.g., $20 out of $50).

  • Since the full amount is required, CCBill treats this as a decline.

What to tell the customer:

  • Make sure the card has enough funds/credit.

  • Try again once funds are available.

  • Use another payment method if needed.

11

CCBill

Approved (VIP)

CCBill Response: “Approved (VIP)”

  • This means the bank approved the transaction.

  • The “(VIP)” note is just wording from the processor — nothing unusual.

  • Funds are secured, and CCBill will settle the payment as normal.

👉 In short: “Approved (VIP)” = Approved Transaction 🎉

16

CCBill

Approved, update track 3

CCBill Response: “Approved, Update Track 3”

  • This is an approved transaction from the bank.

  • The “update track 3” note is just technical wording used for card terminals and doesn’t apply to online payments.

  • CCBill treats it the same as a normal approval.

👉 In short: “Approved, Update Track 3” = Approved Transaction 🎉

17

CCBill

Customer cancellation

CCBill Response: “Customer Cancellation”

  • The customer stopped the payment (clicked Cancel or closed the window).

  • No charge was sent to the bank, so nothing was billed.

  • It’s not an error — just the buyer backing out.

👉 In short: “Customer Cancellation” = Signup not completed.

18

CCBill

Customer dispute

CCBill Response: “Customer Dispute” ⚠️Invalid response

  • The cardholder disputed the charge with their bank.

  • This usually triggers a chargeback (funds pulled back).

  • Reasons can include unrecognized charge, dissatisfaction, or suspected fraud.

🔹 What it means for you:

  • The payment is marked as disputed/chargeback.

  • CCBill manages the process, but you may need to provide evidence (purchase proof, access logs, communication).

👉 In short: “Customer Dispute” = The bank reversed/contested the payment.

20

CCBill

Invalid response

CCBill Error: “Invalid Response” ⚠️

  • The bank sent back a reply CCBill couldn’t read or process (may be due to timeout, network glitch, or unrecognized code).

  • Since no valid approval came through, it’s treated as a decline.

🔹 What to do:

  • Ask the customer to retry the payment.

  • If it continues, suggest using another card or payment method.

  • Merchants can also check with CCBill Support in case of gateway issues.

👉 In short: “Invalid Response” = Bank reply unreadable, so the payment was not approved.

21

CCBill

No action taken

CCBill Response: “No Action Taken” ⚠️

  • The bank received the request but didn’t process it — no approval or decline returned.

  • This is treated as a decline since no approval was issued.

🔹 What to do:

  • Have the customer retry later.

  • Suggest another card if it keeps happening.

  • If many users see it, it may be a temporary bank/processor issue.

👉 In short: “No Action Taken” = Bank didn’t process, so the transaction fails.

23

CCBill

Suspected malfunction

CCBill Response: “Suspected Malfunction” ⚠️

  • The bank’s system had a technical error during authorization.

  • It’s not fraud or a card problem — just a network/processor issue.

  • Since the reply can’t be trusted, CCBill treats it as a decline.

🔹 What to do:

  • Have the customer retry after a few minutes.

  • If it continues, suggest another card or payment method.

  • If many users see it, check with CCBill Support for possible outages.

👉 In short: “Suspected Malfunction” = Bank system hiccup, payment not processed.

24

CCBill

File update not supported by receiver

CCBill Message: “File Update Not Supported by Receiver”

  • Your bank doesn’t allow automatic updates of your card details (like new expiration dates).

  • This doesn’t mean your card is blocked — it just means updates can’t happen automatically.

  • To keep your subscription active, please re-enter your payment details.

✅ In short: Your card is fine, but you’ll need to update it manually so rebills can continue.

25

CCBill

Unable to locate record on file

CCBill Message: “Unable to Locate Record on File”

  • Your bank couldn’t find a matching account for the card.

  • This usually means the card number is invalid, expired, or the account was closed.

  • The payment is declined — you’ll need to enter a valid or new card.

✅ In short: The bank no longer recognizes this card, so the charge can’t go through.

26

CCBill

Duplicate file update record, old record replaced

CCBill Message: “Duplicate File Update Record, Old Record Replaced”

  • Your bank updated the card details on file.

  • It just replaced the old info with the new one.

  • This isn’t an error — billing will continue as normal.

  • No action is needed unless the card itself is later declined.

✅ In short: The card details were successfully updated, and billing will keep running smoothly.

27

CCBill

File update field edit error

CCBill Message: “File Update Field Edit Error”

  • Your bank didn’t accept the automatic update of your card details (like expiration date or account info).

  • This doesn’t mean your card is blocked — just that the update failed.

  • To keep billing active, you’ll need to re-enter your card details manually.

✅ In short: The automatic update didn’t work — please update your card info yourself.

29

CCBill

File update not successful, contact acquirer

CCBill Message: “File Update Not Successful, Contact Acquirer”

  • The bank did not allow the automatic update of your card details.

  • This doesn’t mean your card is blocked — just that the update didn’t go through.

  • To keep your subscription active, please re-enter your payment details manually.

✅ In short: The automatic update failed — you’ll need to update your card info yourself.

30

CCBill

Format error

The CCBill error “Format Error” means the bank couldn’t read the payment request, so it was declined.

  • The customer can retry the payment (sometimes it works on the second attempt).

  • If it keeps happening, they should use another card or payment method.

  • If several customers see this, it may be a temporary processor issue—contact CCBill Support to confirm.

31

CCBill

Bank not supported by switch

The CCBill error “Bank Not Supported by Switch” means the payment network can’t connect to the customer’s issuing bank.

🔹 Why it happens:

  • The bank isn’t supported by the network handling the transaction (common with smaller or certain international banks).

🔹 What it means for the customer:

  • The transaction is declined.

  • They should try a different card, use another payment option supported by CCBill, or check with their bank about online/international payments.

In short: The payment network can’t reach the bank, so the transaction is declined.

32

CCBill

Completed partially

The CCBill error “Completed Partially” means the bank only approved part of the charge (e.g., $20 of a $50 payment).

🔹 Why it happens:

  • Not enough funds or credit to cover the full charge.

  • Bank restrictions or transaction limits.

🔹 How CCBill handles it:

  • Since the full amount is required, CCBill treats it as a decline.

🔹 What to tell the customer:

  • Make sure they have enough funds/credit for the full amount.

  • Retry once funds are available or use a different payment method.

In short: The bank approved only part of the amount, so CCBill declines the transaction.

33

CCBill

Expired card

The CCBill error “Expired Card” means the card is past its expiration date, so the bank won’t approve the charge. ❌💳

🔹 What it means:

  • The transaction is declined automatically.

🔹 What the customer should do:

  • Update the card with the new expiration date (if it’s the same card).

  • Use a new card if the bank already issued a replacement.

🔹 For subscriptions:

  • If a card expires during rebills, payments will fail until updated.

  • Sometimes CCBill’s Account Updater refreshes expiration dates automatically, but if not, the customer must update manually.

In short: “Expired Card” = The card is no longer valid; the customer needs to update their payment details.

34

CCBill

Suspected fraud

The CCBill error “Suspected Fraud” means the bank blocked the payment as potentially fraudulent. ❌🛡️

🔹 Why it happens: mismatched billing info, unusual/foreign charge, card reported lost/stolen, or bank restrictions.
🔹 What it means: the transaction is declined and retrying usually won’t work.
🔹 What the customer should do: contact their bank to clear the block or use another card/payment method.

In short: The bank flagged the payment as fraud, so it was declined.

35

CCBill

Card acceptor contact acquirer

The transaction was declined because the bank requires extra verification.

🔎 Why it happens:

  • Bank flagged the payment as unusual or high-risk

  • Extra authorization is needed

  • Bank wants the customer to confirm the charge

Next steps:

  • Customer should contact their bank to approve the payment, then retry

  • If urgent, they can use another card or payment method

36

CCBill

Restricted card

The card was declined because the bank placed restrictions on its use.

🔎 Why it happens:

  • Card blocked for online, international, or adult transactions

  • Card limited to domestic use only

  • Restrictions on certain cards (e.g., prepaid, gift cards)

Next steps:

  • Customer should contact their bank to confirm or lift restrictions

  • If not possible, use a different card or payment option

  • Merchants can confirm with CCBill that their category setup is correct

37

CCBill

Card acceptor call acquirer security

The bank declined the transaction because it flagged it as a potential security risk.

🔎 Why it happens:

  • Bank detected suspicious activity

  • Incorrect CVV or billing address

  • Fraud prevention rules triggered

Next steps:

  • Customer should contact their bank to approve the payment, then retry

  • If urgent, use another card or payment method

38

CCBill

Allowable PIN tries exceeded

The card was declined because the wrong PIN was entered too many times.

🔎 Why it happens:

  • Multiple incorrect PIN attempts

  • Bank temporarily blocked the card for security

Next steps:

  • Customer should contact their bank to reset or unblock the card

  • They may need to use another card to complete the purchase

🔹 For merchants: No action needed — this is entirely on the issuer’s side.

39

CCBill

No credit account

The card was declined because the account type doesn’t support credit transactions.

🔎 Why it happens:

  • Debit/ATM-only or restricted-use card used where a credit-enabled card is required

  • Account doesn’t allow online or recurring charges

Next steps:

  • Customer should use a different card that supports credit or online payments

  • If they believe it should work, they need to contact their bank to confirm restrictions

40

CCBill

Requested function not supported

The transaction was declined because the card or issuer doesn’t support this type of transaction.

🔎 Why it happens:

  • Card doesn’t allow recurring or certain online payments

  • Transaction type (e.g., refund, pre-authorization) not supported for that card

  • Issuer’s network doesn’t recognize the request

Next steps:

  • Customer should try a different card that supports online/recurring charges

  • If they believe the card should work, they need to contact their bank

  • Merchants should confirm the correct transaction type is being submitted to CCBill

42

CCBill

No universal account

The card was declined because the account type doesn’t support this kind of transaction.

🔎 Why it happens:

  • Restricted-use card (ATM-only, local debit, or prepaid)

  • Card not enabled for online or international use

  • Issuer blocked this type of transaction

Next steps:

  • Customer should try another card that supports online/credit transactions

  • If they believe the card should work, they need to contact their bank

  • For merchants: No action needed — this is issuer-side

44

CCBill

No investment account

The card was declined because the account type linked to it doesn’t support this kind of purchase.

🔎 Why it happens:

  • Restricted account (e.g., savings, investment, or non-transactional)

  • Account not valid for card purchases or online transactions

Next steps:

  • Customer should try another card that supports online payments

  • If they believe the card should work, they should contact their bank

  • For merchants: No action needed — this is issuer-side

45/50

CCBill

Reserved for ISO use

This decline code is a generic placeholder set by the ISO (International Standards Organization).

🔎 What it means:

  • The code itself has no standard meaning

  • The bank/network used it for a condition they haven’t disclosed

  • Often shows up when CCBill can’t map the bank’s reason to a common decline code

Next steps:

  • Customer should contact their bank for the exact reason

  • Suggest using a different card or payment method

  • For merchants: If many users see this, contact CCBill support

52

CCBill

No checking account

The transaction was declined because the card is not linked to a checking account, so it isn’t valid for this type of purchase.

🔎 Why it happens:

  • Card is tied to a savings, investment, or restricted-use account

  • Issuer doesn’t allow online or credit-type transactions on that account

Next steps:

  • Customer should try a different card linked to a checking or credit account

  • If they believe the card should work, they need to contact their bank

  • For merchants: No action needed — this is issuer-side

53

CCBill

No savings account

The transaction was declined because the card is tied to a savings account, which can’t be used for this type of purchase.

🔎 Why it happens:

  • Charge attempted on a savings-only account

  • Bank doesn’t allow online or recurring charges from savings accounts

  • Account type doesn’t support card transactions

Next steps:

  • Customer should use a card linked to a checking or credit account

  • If they believe the card should work, they need to contact their bank

  • For merchants: No action needed — this is issuer-side

55

CCBill

Incorrect personal identification number

The transaction was declined because the PIN entered didn’t match the one on file with the bank.

🔎 Why it happens:

  • Customer mistyped their PIN

  • Debit/ATM card requires PIN verification

  • Too many wrong attempts may temporarily block the card

Next steps:

  • Customer should re-enter the correct PIN

  • If it still fails, they need to contact their bank to reset or check the card status

  • Suggest using a different card if available

56

CCBill

No card record

The transaction was declined because the bank couldn’t find the card number in their system.

🔎 Why it happens:

  • Wrong card number entered

  • Card not yet activated

  • Card is invalid, expired, or no longer recognized by the bank

Next steps:

  • Customer should double-check and re-enter their card details

  • If it’s a new card, ensure it has been activated

  • If the issue continues, contact the bank or try another card

59

CCBill

Suspected fraud

The transaction was declined because the bank flagged it as possible fraud.

🔎 Why it happens:

  • Bank’s fraud system blocked the charge

  • Transaction looked unusual (cross-border, high-risk, large amount)

  • Card may have prior fraud alerts

Next steps:

  • Customer should contact their bank to confirm the payment is legitimate, then retry

  • If urgent, they can use a different card or payment method

  • For merchants: Watch for repeated fraud declines; if many users see this, check with CCBill

60

CCBill

Card acceptor contact acquirer

The transaction was declined because the card isn’t allowed for this type of purchase.

🔎 Why it happens:

  • Card restricted from online, international, or adult purchases

  • Issuer blocked certain transaction types (e.g., recurring, cross-border)

  • Security or compliance limits on the account

Next steps:

  • Customer should contact their bank to confirm the restriction

  • Suggest trying a different card or payment method

  • For merchants: No action needed unless many users report it — then check with CCBill

61

CCBill

Exceeds withdrawal amount limit

The transaction was declined because it exceeded the cardholder’s spending or withdrawal limit.

🔎 Why it happens:

  • Amount is higher than the card’s daily or per-transaction limit

  • Cardholder already reached their daily spending cap

  • Bank restricted high-value or international charges

Next steps:

  • Customer can try a smaller transaction (if possible)

  • Contact their bank to confirm or request a higher limit

  • If urgent, use another card or payment method

64

CCBill

Original amount incorrect

The transaction was declined because the refund, reversal, or adjustment amount didn’t match the original transaction.

🔎 Why it happens:

  • Mismatch between the original and follow-up amount

  • Attempted partial refund/adjustment when the issuer only allows full amounts

  • Incorrect data sent from the merchant system to CCBill

Next steps:

  • For merchants: Make sure the follow-up request exactly matches the original amount; check if partial refunds are supported

  • For customers: This is a processing issue — the merchant/CCBill needs to correct it

66

CCBill

Card acceptor call acquirer's security department

The transaction was declined because the bank flagged it as a security issue.

🔎 Why it happens:

  • Bank’s fraud system blocked the charge

  • Restrictions on certain merchants (adult, international, recurring)

  • Suspicious or incorrect transaction data

Next steps:

  • Customer should contact their bank to approve the charge, then retry

  • If urgent, they can use another card or payment method

  • For merchants: No action needed unless many users see this — then check with CCBill

67

CCBill

Hard capture (requires that card be picked up at ATM)

The transaction was declined because the bank flagged the card and requested it be retained if used in person.

🔎 Why it happens:

  • Card reported lost or stolen

  • Account closed by the bank

  • Fraud alert or security block placed on the card

Next steps:

  • Customer should contact their bank immediately to resolve the issue

  • They’ll need to use a different, valid card to complete the purchase

  • For merchants: No action required — this comes directly from the issuer

68

CCBill

Response received too late

The transaction was declined because the bank didn’t respond in time, and the request expired.

🔎 Why it happens:

  • Network or system delays at the bank

  • Temporary outage or slowdown

  • High traffic causing timeouts

Next steps:

  • Ask the customer to retry the payment

  • Suggest using a different card or payment method if it keeps failing

  • For merchants: If many customers see this, check with CCBill support about possible network issues

69/74

CCBill

Reserved for ISO use

This decline code is a generic placeholder under the ISO 8583 standard.

🔎 What it means:

  • It has no fixed, universal definition.

  • The issuer or network used it for an internal or non-standard reason.

  • In practice, it’s just a “non-specific” decline.

Next steps:

  • Ask the customer to contact their bank for the real reason.

  • Suggest trying a different card or payment method.

  • For merchants: If this happens often, reach out to CCBill support to clarify what issuers are returning.

75

CCBill

Allowable number of PIN tries exceeded

The card was declined because the wrong PIN was entered too many times.

🔎 Possible causes:

  • Several failed PIN attempts on a debit/ATM card.

  • The bank temporarily blocked the card for security.

Next steps:

  • The customer should contact their bank to reset or unblock the card.

  • They can use a different card to finish the purchase right away.

👉 Merchant note: No action required—this is entirely handled by the issuer.

90

CCBill

Cutoff is in process (switch ending a day's business and starting the next. Transaction can be sent again in a few minutes)

The transaction couldn’t be processed because the card issuer’s system was in daily update/maintenance mode.

🔎 Possible causes:

  • End-of-day batch processing by the bank.

  • Temporary downtime of the issuer’s authorization system.

  • Timing issue between CCBill and the bank.

Next steps:

  • Ask the customer to retry after a short wait.

  • If it still fails, suggest using a different card or payment method.

👉 Merchant note: No action needed—this is on the issuer’s side.

92

CCBill

Financial institution or intermediate network facility cannot be found for routing

The transaction couldn’t be completed because the card issuer’s system or network was unavailable.

🔎 Possible causes:

  • Temporary outage at the customer’s bank.

  • Communication issue between CCBill and the issuer.

  • Scheduled maintenance or unexpected downtime.

Next steps:

  • Ask the customer to retry later.

  • If urgent, suggest another card or payment method.

👉 Merchant note: No action needed unless many users report the same issue—then check with CCBill support.

94

CCBill

Duplicate transmission

The transaction was declined because it was flagged as a duplicate.

🔎 Possible causes:

  • Customer clicked “pay” multiple times.

  • A network glitch resent the request.

  • The system accidentally submitted it twice.

Next steps:

  • Check if the first transaction went through.

  • If it was approved, no need to retry.

  • If declined, the customer can try again.

👉 Merchant note: Review your setup to avoid sending duplicate requests.

95

CCBill

Reconcile error

The transaction failed because the processor found mismatched details during authorization.

🔎 Possible causes:

  • Data didn’t match between authorization and settlement.

  • Issuer or network flagged it as inconsistent.

  • Temporary processing glitch.

Next steps:

  • Ask the customer to try again.

  • If it keeps failing, suggest another card or payment method.

👉 Merchant note: Check your integration logs. If it repeats, contact CCBill support.

BE-102

CCBill

Pickup Card

The card was declined because it’s reported lost, stolen, or blocked by the bank.
If presented in person, the issuer would request it be confiscated.

🔎 Common causes

  • Reported lost or stolen

  • Suspected fraud

  • Account closed or blocked

Next steps

  • The customer must contact their bank.

  • They need to use a different, valid card or payment method.

  • Merchants should not retry the transaction with this card.

BE-103

CCBill

Do Not Honor

One of the most common card errors: a generic bank decline.

What it means
The issuing bank refused the transaction without giving a specific reason — basically: “Do not approve this payment.”

🔎 Common causes

  • Suspected fraud or unusual activity

  • Insufficient funds

  • Restrictions on online/recurring purchases

  • Temporary issue with the bank’s system

Next steps

  • Have the customer try again (a retry may work)

  • Suggest a different card or payment method

  • If it keeps failing, the customer must contact their bank

👉 As a merchant, there’s no technical fix — this decision is entirely up to the issuer.

BE-116

CCBill

Service Not Allowed

Means the issuing bank has blocked this type of transaction.

❌ What it means

- The card isn’t permitted for certain merchant categories (adult, subscription, or international services).

- The bank has disabled the card for online or recurring payments.

- Often happens with prepaid, debit, or regional cards that have restrictions.

🔎 Common causes

- Customer’s bank policy forbids this kind of purchase.

- The card is restricted to domestic only use, and your business is classified as international.

- The cardholder didn’t activate/enable e-commerce transactions.

✅ Next steps

- Suggest the customer use a different card (credit cards generally have fewer restrictions).

- Advise them to contact their bank and request online/recurring/merchant category access if available.

- If they have another payment option (PayPal, alternative billing), recommend that.

BE-146

CCBill

Blocked Country (CCBill)

The transaction was blocked because the cardholder’s country is not allowed by the issuer or CCBill’s compliance rules.

🔎 Common causes

  • The customer’s country is restricted for legal, regulatory, or compliance reasons.

  • CCBill or the issuing bank does not process payments from that location.

  • The merchant’s account/category does not permit transactions from certain regions.

Next steps

  • Inform the customer that payments from their country cannot be accepted.

  • Suggest an alternative payment method supported in their region (e.g., crypto, another processor).

👉 As a merchant, no action is required — this is a compliance restriction.

BE-132

CCBill

Card Blocked (CCBill)

The card has been blocked by the issuer.
This means the bank has explicitly declined the transaction and instructed that the card should not be used.

🔍 Possible Causes

  • Fraud prevention: The bank flagged the card for suspicious activity.

  • Account issues: The cardholder’s account is closed, suspended, or has unresolved problems.

  • Security measures: The card was reported lost or stolen, or blocked under bank protocols.

Recommended Actions

For the Merchant:

  • Do not retry: Avoid submitting the same card again.

  • Inform the customer: Let them know their bank blocked the card and recommend using a different payment method.

  • If widespread: Contact CCBill Merchant Support for clarification.

For the Customer:

  • Contact the issuing bank: Ask why the card was blocked and resolve the issue.

  • Try another method: Use a different card or payment option if urgent.

BE-112

CCBill

No Account

The card number is not recognized by the issuer.
The number provided does not correspond to an active account in the card issuer’s system.

🔍 Possible Causes

  • The card number was entered incorrectly.

  • The card is newly issued but not yet activated.

  • The card has been closed, expired, or canceled.

Recommended Actions

For the Merchant:

  • Do not retry: Don’t attempt the same card again.

  • Inform the customer: Let them know the card number isn’t recognized and advise them to try another payment method.

For the Customer:

  • Double-check details: Verify the card number, expiration date, and CVV are correct.

  • Contact the issuing bank: Confirm whether the card is active and usable.

  • Use another method: If unresolved, try a different card or payment option.

BE-900-999

CCBill

System error, authorization not successful

The payment couldn’t be completed due to a technical issue.

🔎 Causes

  • Temporary network or system outage.

  • Processing error between CCBill and the bank.

  • High traffic or timeout.

Next Steps

  • Ask the customer to retry after a short wait.

  • If it keeps failing, suggest another card or payment method.

  • As a merchant, contact CCBill if many users are affected.

BE-113

CCBill

Insufficient Funds

Insufficient Funds
The account doesn’t have enough balance to complete the payment.

Next Steps

  • Customer should add funds or use another card/payment method.

  • Merchant doesn’t need to take any action.

BE-114

CCBill

Expired card

Expired Card
The card is no longer valid because its expiration date has passed.

Fix

  • Customer must update their payment details with a new/valid card.

  • Merchant doesn’t need to act until new info is provided.

BE-119

CCBill

Activity Limit Exceeded

Transaction Limit Reached
The card/account has hit the maximum number of transactions allowed in a set time period.

🔎 Causes

  • Daily, weekly, or monthly transaction caps.

  • Spending limits exceeded.

  • Issuer restrictions on online/recurring payments.

Next Steps
For the Customer:

  • Wait until the limit resets and retry.

  • Use a different card or payment method.

  • Contact the bank to confirm or raise limits.

For the Merchant:

  • No action required — this is issuer-controlled.

BE-107

CCBill

Invalid Credit card

Invalid Card Number
The card number entered is not recognized by the issuer.

🔎 Causes

  • Typo or missing digits.

  • Card expired, canceled, or never activated.

  • Card type not supported.

Next Steps
For the Customer:

  • Recheck card number, expiration date, and CVV.

  • Make sure the card is active and valid.

  • Try another card if it still fails.

For the Merchant:

  • No fix needed — this is issuer-side.

  • Advise the customer to correct details or use a different card.

BE-105

CCBill

Invalid Transaction

Invalid Transaction Request
The issuer or processor rejected the request because it wasn’t valid.

🔎 Causes

  • Wrong or unsupported transaction type (sale, refund, recurring).

  • Invalid or incomplete data (amount, card details, format).

  • Card restricted or merchant setup issue.

Next Steps
For the Customer:

  • Check that card and billing info are correct.

  • Try a different card if it still fails.

For the Merchant:

  • Verify integration data and transaction type.

  • Confirm account settings support this transaction.

  • Contact CCBill if the problem persists.

BE-130

CCBill

Invalid Field Provided

Invalid or Incorrect Data
One or more fields in the payment request were entered incorrectly or formatted wrong.

🔎 Causes

  • Wrong card number, expiration date, or CVV.

  • Billing address/postal code doesn’t match bank records.

  • Invalid characters or formatting in the request.

  • Merchant integration/API error.

Next Steps
For the Customer:

  • Recheck all card and billing info.

  • Make sure the address matches what the bank has on file.

  • Try another card if it still fails.

For the Merchant:

  • Check logs to confirm fields are formatted properly.

  • Ensure API/form is sending valid data.

  • Contact CCBill if the issue keeps happening.

BE-101

CCBill

Invalid MID/TID

Invalid Merchant or Terminal ID
The transaction was sent with a wrong or inactive merchant account or terminal ID.

🔎 Causes

  • Integration errors or misconfigured payment settings.

  • Merchant account inactive or not recognized by CCBill.

Next Steps
For the Merchant:

  • Verify that the MID and TID in your integration or payment form are correct.

  • Ensure the account is active and supports the transaction type.

  • Contact CCBill Support if the issue continues.

For the Customer:

  • No action needed — this is a merchant-side issue.

F440

Segpay

SPVelocity

The card number isn’t recognized by the bank — it may be expired, canceled, inactive, or entered incorrectly.

🔎 Next Steps
For the Customer:

  • Verify the card number, expiration date, and CVV.

  • Try another card if it still fails.

For the Merchant:

  • No action required — this is issuer-side.

  • Advise the customer to check their card or use a different payment method.

F451

Segpay

SPNegDB

Invalid Card Expiration Date
The expiration date entered is incorrect or the card is expired.

🔎 Next Steps
For the Customer:

  • Check that the expiration month and year are correct.

  • Use a valid, active card if the current one is expired.

  • Try a different card if it still fails.

For the Merchant:

  • No action needed — this is issuer-side.

  • Advise the customer to verify their card details or use another payment method.

F452

Segpay

SPNegDB

Invalid Card Security Code (CVV/CVC)
The CVV/CVC entered doesn’t match what the bank has on file.

🔎 Next Steps
For the Customer:

  • Verify the 3- or 4-digit CVV on the card (back for most cards, front for Amex).

  • Re-enter carefully.

  • Try another card if it still fails.

For the Merchant:

  • No action needed — this is issuer-side.

  • Advise the customer to check their CVV or use a different card.

F453

Segpay

SPNegDB

Invalid Card Number / Card Not Supported
The card number is invalid, not recognized by the bank, or the card type isn’t supported.

🔎 Next Steps
For the Customer:

  • Check the card number, expiration date, and CVV.

  • Try another card if it still fails.

For the Merchant:

  • No action needed — this is issuer-side.

  • Advise the customer to verify their card or use a different payment method.

F455

Segpay

SPNegDB

Invalid / Unsupported Card Type
The card isn’t supported by Segpay or the merchant account. Some debit, prepaid, or regional cards may be restricted.

🔎 Next Steps
For the Customer:

  • Use a different card (preferably Visa, MasterCard, or Amex).

  • Contact the issuer to check if the card can be used for online or recurring payments.

For the Merchant:

  • No action needed — this is issuer/processor controlled.

  • Advise the customer to try another card or payment method.

F456

Segpay

SPNegDB

Card Restricted / Not Allowed for This Transaction
The card issuer blocked this card for the type of transaction being attempted. This can include online, recurring, adult, or geographically restricted payments.

🔎 Next Steps
For the Customer:

  • Use a different card that allows online or recurring transactions.

  • Contact the issuer to see if the card can be enabled for this purchase.

For the Merchant:

  • No action needed — this is issuer-controlled.

  • Advise the customer to use a supported card or another payment method.

F457

Segpay

Dupe

Card Restricted / Merchant Category Not Allowed
The card issuer blocked this card for purchases with certain merchant types, such as adult, online subscription, or high-risk merchants.

🔎 Next Steps
For the Customer:

  • Use a different card that allows this type of purchase.

  • Contact the issuer to see if the card can be enabled for this merchant category.

For the Merchant:

  • No action needed — this is issuer-controlled.

  • Advise the customer to try a supported card or another payment method.

F458

Segpay

SPNegDB

Card Restricted / Transaction or Merchant Type Not Allowed
The card issuer blocked this card for certain transaction types or merchant categories, such as adult content, online subscriptions, or high-risk merchants.

🔎 Next Steps
For the Customer:

  • Use a different card that allows online or recurring payments.

  • Contact the issuer to see if restrictions can be lifted.

For the Merchant:

  • No action needed — this is issuer-controlled.

  • Advise the customer to use a supported card or another payment method.

F460

Segpay

SPVelocity

Card Declined / Do Not Honor
The issuer refused the transaction without giving a specific reason.

🔎 Next Steps
For the Customer:

  • Try again or use a different card.

  • Contact their bank for more details.

For the Merchant:

  • No action needed — this is issuer-controlled.

  • Advise the customer to use another payment method.

F461

Segpay

SPVelocity

Card Declined / Insufficient Funds
The account doesn’t have enough balance to cover the payment.

🔎 Next Steps
For the Customer:

  • Check the account balance and try again.

  • Use a different card or payment method if needed.

For the Merchant:

  • No action needed — this is issuer-side.

  • Advise the customer to retry or use another payment method.

F462

Segpay

SPVelocity

Card Declined / Transaction Not Permitted
The issuer blocked this type of transaction due to restrictions on merchant category, geography, or card type.

🔎 Next Steps
For the Customer:

  • Use a different card that allows this purchase.

  • Contact the bank to see if restrictions can be lifted.

For the Merchant:

  • No action needed — this is issuer-controlled.

  • Advise the customer to try another card or payment method.

F463

Segpay

SPVelocity

Card Declined / Card Restricted
The issuer blocked the card for this type of transaction, often due to merchant category, online/recurring limits, or regional restrictions.

🔎 Next Steps
For the Customer:

  • Use a different card that allows this type of purchase.

  • Contact the bank to check restrictions.

For the Merchant:

  • No action needed — this is issuer-controlled.

  • Advise the customer to use another card or payment method.

F464

Segpay

SPVelocity

Card Declined / Card Not Allowed for This Merchant
The issuer blocked the card for use with this merchant, often due to merchant category, account restrictions, or unsupported card type.

🔎 Next Steps
For the Customer:

  • Use a different card that allows online or recurring transactions.

  • Contact their bank to see if restrictions can be lifted.

For the Merchant:

  • No action needed — this is issuer-controlled.

  • Advise the customer to use another card or payment method.

F465

Segpay

SPVelocity

Card Declined / Restricted Transaction
The issuer blocked the card for this type of transaction, often due to merchant category, online/recurring limits, or account restrictions.

🔎 Next Steps
For the Customer:

  • Use a different card that supports this transaction.

  • Contact their bank to check restrictions.

For the Merchant:

  • No action needed — this is issuer-controlled.

F470

Segpay

SPNegDB

Do Not Honor
The issuer declined the transaction without giving a reason, often due to suspected fraud, insufficient funds, or card restrictions.

🔎 Next Steps
For the Customer:

  • Try the transaction again or use a different card.

  • Contact their bank for more details.

For the Merchant:

  • No action needed — this is issuer-controlled.

  • Advise the customer to use another card or payment method.

F471

Segpay

SPNegDB

Card Declined / Insufficient Funds
The account doesn’t have enough balance to cover the payment. Daily or transaction limits may also apply.

🔎 Next Steps
For the Customer:

  • Check the account balance and try again.

  • Use a different card or payment method if needed.

For the Merchant:

  • No action needed — this is issuer-side.

  • Advise the customer to retry or use another payment method.

F481

Segpay

SPNegDB

Card Declined / Transaction Not Permitted
The issuer blocked this type of transaction, often due to merchant category, online/recurring limits, or card/account restrictions.

🔎 Next Steps
For the Customer:

  • Use a different card that allows this purchase.

  • Contact their bank to check restrictions.

For the Merchant:

  • No action needed — this is issuer-controlled.

  • Advise the customer to try another card or payment method.

F492

Segpay

MerchNegDB

Card Declined / Card Restricted
The issuer blocked the card for this type of transaction, often due to merchant category, online/recurring limits, or regional restrictions.

🔎 Next Steps
For the Customer:

  • Use a different card that supports this transaction.

  • Contact their bank to check restrictions.

For the Merchant:

  • No action needed — this is issuer-controlled.

  • Advise the customer to use another card or payment method.

F493

Segpay

SPNegDB

Card Declined / Transaction Not Allowed
The issuer blocked the card for this type of transaction, often due to merchant category, online/recurring limits, or card/account restrictions.

🔎 Next Steps
For the Customer:

  • Use a different card that allows this purchase.

  • Contact their bank to check restrictions.

For the Merchant:

  • No action needed — this is issuer-controlled.

  • Advise the customer to try another card or payment method.

F494

Segpay

SPNegDB

Card Declined / Card Restricted
The issuer blocked the card for this type of transaction, often due to merchant category, online/recurring limits, or regional restrictions.

🔎 Next Steps
For the Customer:

  • Use a different card that allows this transaction.

  • Contact the bank to check restrictions.

For the Merchant:

  • No action needed — this is issuer-controlled.

  • Advise the customer to try another card or payment method.

V3001

Segpay

SPVelocity

Card Declined / Card Restricted
The issuer blocked the card for this transaction type, often due to merchant category, online/recurring limits, or regional restrictions.

🔎 Next Steps
Customer:

  • Use a different card that allows this transaction.

  • Contact their bank to check restrictions.

Merchant:

  • No action needed — this is issuer-controlled.

  • Advise the customer to try another card or payment method.

V3002

Segpay

SPVelocity

AVS Not Supported / No Match
The card issuer can’t verify the billing address, or AVS isn’t supported. This is a fraud-prevention check, not necessarily a card issue.

🔎 Next Steps
Customer:

  • Make sure the billing address and postal code match exactly what the bank has on file.

  • For international cards, try a card that supports AVS.

Merchant:

  • No action needed — this is issuer-controlled.

  • Advise the customer to confirm their address or use a different card.

V3003

Segpay

SPVelocity

❌ Address Verification System (AVS) Mismatch – Postal Code / ZIP Incorrect

🔎 What it Means

The postal code or ZIP code entered does not match the one on file with the card issuer.

AVS is a fraud-prevention check; even a small difference can trigger this decline.

✅ Next Steps

For the Customer:

Verify that the billing postal code/ZIP code matches exactly what the bank has on file.

Correct any typos or missing digits.

Use a different card if the issue persists.

For the Merchant:

No technical action is required; this is issuer-side.

Advise the customer to confirm their billing postal code or try another card.

V3004

Segpay

SPVelocity

AVS Mismatch – Street Address Incorrect
The street address entered doesn’t match the one on file with the card issuer. AVS checks help prevent fraud.

🔎 Next Steps
Customer:

  • Make sure the billing street address matches exactly, including apartment/unit numbers.

  • Correct any typos or formatting issues.

  • Try a different card if it still fails.

Merchant:

  • No action needed — this is issuer-side.

  • Advise the customer to confirm their address or use another card.

V3005

Segpay

SPVelocity

AVS Mismatch – Street Address & Postal Code Incorrect
Both the street address and postal/ZIP code don’t match the card issuer’s records. AVS checks are used to prevent fraud.

🔎 Next Steps
Customer:

  • Ensure the billing street address and postal/ZIP code match exactly what the bank has on file.

  • Correct any typos or missing info.

  • Try a different card if needed.

Merchant:

  • No action needed — this is issuer-side.

  • Advise the customer to confirm their billing info or use another card.

V3006

Segpay

SPVelocity

AVS Not Verified / System Error
The card issuer couldn’t complete the AVS check. This doesn’t necessarily mean the card is invalid.

🔎 Next Steps
Customer:

  • Retry the transaction after a short wait.

  • Ensure the billing address and postal/ZIP code are entered correctly.

  • Try a different card if it still fails.

Merchant:

  • No action needed — this is issuer-side.

  • Advise the customer to retry or use another card.

V3007

Segpay

SPVelocity

❌ Address Verification System (AVS) Mismatch – Cardholder Name Does Not Match

🔎 What it Means

The cardholder name entered does not match the name on file with the card issuer.

AVS checks are used to prevent fraudulent transactions.

Even minor differences (e.g., initials, middle names, or spelling) can trigger this decline.

✅ Next Steps

For the Customer:

Verify that the billing name exactly matches what is on the card.

Correct any typos, initials, or formatting differences.

Use a different card if the issue persists.

For the Merchant:

No technical action is required; this is issuer-side.

Advise the customer to confirm their billing name or try another card.

V3008

Segpay

SPVelocity

AVS Mismatch – Name & Street Address Incorrect
The cardholder name and street address don’t match the bank’s records. AVS helps prevent fraud.

🔎 Next Steps
Customer:

  • Ensure the billing name and street address exactly match the bank’s records.

  • Correct any typos or formatting differences.

  • Try a different card if needed.

Merchant:

  • No action needed — this is issuer-side.

  • Advise the customer to confirm billing info or use another card.

V3009

Segpay

SPVelocity

AVS Mismatch – Name & Postal/ZIP Incorrect
The cardholder name and postal/ZIP code don’t match the bank’s records. AVS helps prevent fraud.

🔎 Next Steps
Customer:

  • Make sure the billing name and postal/ZIP code match the bank’s records exactly.

  • Correct any typos or formatting differences.

  • Try a different card if needed.

Merchant:

  • No action needed — this is issuer-side.

  • Advise the customer to confirm billing info or use another card.

V3010

Segpay

SPVelocity

AVS Mismatch – Name, Address, and Postal/ZIP Code Incorrect

🔎 What it Means
The billing name, street address, and postal/ZIP code entered don’t match the information on file with the card issuer. AVS checks help prevent fraudulent transactions.

Next Steps

For the Customer:

  • Make sure the billing name, address, and postal/ZIP code match exactly what the bank has on file.

  • Double-check for typos or formatting differences.

  • If the problem continues, try another card.

For the Merchant:

  • No technical fix is needed; this comes from the card issuer.

  • Advise the customer to verify their billing details or use a different card.

V3011

Segpay

SPVelocity

AVS Mismatch – Partial Match

🔎 What it Means
Some billing details (name, address, or postal/ZIP code) don’t fully match what the card issuer has on file. AVS checks help prevent fraud, and partial mismatches can cause declines.

Next Steps

For the Customer:

  • Ensure the billing name, address, and postal/ZIP code exactly match what the bank has on file.

  • Double-check for typos or formatting differences.

  • If the issue continues, try a different card.

For the Merchant:

  • No technical changes needed; this comes from the card issuer.

  • Ask the customer to confirm their billing details or use another card.

V3012

Segpay

SPVelocity

AVS Not Supported / Not Available

🔎 What it Means
The card issuer doesn’t support AVS, or the system couldn’t verify the billing address. This is common with international cards or temporary bank issues.

Next Steps

For the Customer:

  • Check that your billing address and ZIP/postal code are correct

  • Try again later

  • Use another card if it still doesn’t work

For the Merchant:

  • No action needed; this is issuer-side

  • Advise the customer to retry or use a different card

ERR301

Segpay

Invalid Card Number

🔎 What it Means
The card number isn’t recognized by the issuing bank. This may be due to a typo, an expired/canceled card, or an unsupported card type.


Next Steps

For the Customer:

  • Double-check the card number, expiration date, and CVV

  • Try another card if the issue continues

For the Merchant:

  • No action needed; this is issuer-side

  • Advise the customer to verify their card details or use a different card

ERR302

Segpay

Invalid Card Expiration Date

🔎 What it Means
The expiration date entered is incorrect or the card has expired.

Next Steps

For the Customer:

  • Double-check the expiration month and year

  • If the card is expired, use a valid card

  • Try another card if needed

For the Merchant:

  • No action required; this is issuer-side

  • Advise the customer to confirm their card details or use another card

ERR303

Segpay

Invalid Card Security Code (CVV/CVC)

🔎 What it Means
The CVV/CVC entered doesn’t match what the bank has on file. This may be due to a typo, using the wrong code, or too many failed attempts.

Next Steps

For the Customer:

  • Check the 3- or 4-digit CVV (back of card, or front for Amex)

  • Re-enter carefully

  • Use another card if the issue continues

For the Merchant:

  • No action needed; this is issuer-side

  • Advise the customer to confirm their CVV or try a different card

ERR304

Segpay

Insufficient Funds

🔎 What it Means
The cardholder’s account doesn’t have enough balance to complete the transaction, or the bank has set limits that block it.

Next Steps

For the Customer:

  • Check account balance and retry once funds are available

  • Use another card or payment method if needed

For the Merchant:

  • No action required; this is issuer-side

  • Advise the customer to retry or use a different payment method

ERR305

Segpay

Card Restricted / Transaction Not Allowed

🔎 What it Means
The bank has blocked this card for the attempted transaction. This may be due to merchant category restrictions (e.g., adult/high-risk), online or international limits, or account-level rules.

Next Steps

For the Customer:

  • Try a different card that supports this type of purchase

  • Contact your bank to ask about restrictions

For the Merchant:

  • No action required; this is issuer-controlled

  • Advise the customer to use another card or payment method

ERR306

Segpay

Card Expired

🔎 What it Means
The card is no longer valid because it has passed its expiration date.

Next Steps

For the Customer:

  • Use a valid, active card

  • Double-check the expiration month and year

For the Merchant:

  • No action required; this is issuer-side

  • Advise the customer to use a valid card

ERR307

Segpay

Card Restricted / Not Allowed for This Transaction

🔎 What it Means
The bank has blocked the card from being used for this type of purchase. This may be due to merchant category rules (e.g., adult/high-risk), online or international limits, or issuer-specific restrictions.

Next Steps

For the Customer:

  • Use another card that supports this type of transaction

  • Contact your bank to check on restrictions

For the Merchant:

  • No action needed; this is issuer-controlled

  • Advise the customer to try another card or payment method

ERR308

Segpay

Card Lost or Stolen

🔎 What it Means
The bank has blocked this card because it was reported lost or stolen. Transactions with it won’t be approved until resolved with the issuer.

Next Steps

For the Customer:

  • Contact your bank right away to resolve the issue

  • Use a different, valid card

For the Merchant:

  • No action required; this is issuer-side

  • Advise the customer to contact their bank or use another card

ERR309

Segpay

Card Restricted / Cardholder Not Authorized for This Transaction

🔎 What it Means
The bank has blocked the card from being used for this type of purchase. This may be due to merchant category restrictions (e.g., adult/high-risk), online or international limits, or cardholder-specific rules from the issuer.

Next Steps

For the Customer:

  • Try another card that supports this type of purchase

  • Contact your bank to ask about restrictions

For the Merchant:

  • No action required; this is issuer-controlled

  • Advise the customer to try a different card or payment method

ERR310

Segpay

Card Not Supported / Card Type Not Accepted

🔎 What it Means
The card isn’t supported by Segpay or the merchant. This may happen with certain card types (e.g., prepaid, debit) or with international cards blocked for cross-border use.

Next Steps

For the Customer:

  • Use another card that the merchant supports

  • Contact your bank to confirm if the card works for online or international payments

For the Merchant:

  • No action needed; this is issuer-side

  • Advise the customer to try a supported card or another payment method

3

Segpay

Invalid Merchant

🔎 What it Means
The issuing bank or Segpay system does not recognize the merchant ID or configuration. This is not related to the customer’s card details but to the merchant’s account setup.

What to Do

For the Merchant:

  • Check your Merchant ID (MID) in the Segpay gateway or integration settings

  • Confirm your merchant account is active and correctly configured for the card type/vertical

  • Contact Segpay support or your processor if the issue continues

For the Customer:

  • No action needed—this error is on the merchant side

4

Segpay

Pick Up Card / Do Not Honor

🔎 What it Means The card issuer has declined the transaction. “Pick Up Card” usually indicates a permanent decline, meaning the card cannot be used.

Common causes: Card reported as lost or stolen. Card closed or blocked by the issuer. Issuer refuses to authorize the transaction without giving a reason.

✅ Next Steps For the Customer: Use a different card. Contact the bank/issuer for clarification.

For the Merchant: No technical action is required; this is issuer-controlled. Advise the customer to use an alternative card.

7

Segpay

Pickup card, special conditions

🔎 What it Means
The bank has declined the transaction. This code often means the card was reported lost/stolen, closed, blocked, or the issuer refused the transaction without giving details.

Next Steps

For the Customer:

  • Use another card

  • Contact your bank for clarification

For the Merchant:

  • No action needed; this is issuer-controlled

  • Advise the customer to try a different card or payment method

12

Segpay

Invalid transaction

🔎 What it Means
The card issuer did not approve the transaction. This can be due to suspected fraud, restrictions on the card, or a general issuer decline without details.

Next Steps

For the Customer:

  • Try a different card

  • Contact your bank for more information

For the Merchant:

  • No action required; this is issuer-controlled

  • Advise the customer to use another card or payment method

15

Segpay

Invalid Card / No Such Issuer

🔎 What it Means
The card number isn’t recognized by the issuer. This can happen due to a typo, an expired or inactive card, or a card type not supported by the merchant/processor.

Next Steps

For the Customer:

  • Double-check the card number, expiration date, and CVV

  • Try another card if the issue continues

For the Merchant:

  • No action required; this is issuer-side

  • Advise the customer to verify their card or use another payment method

41

Segpay

Pickup card lost card

🔎 What it Means
The card has been reported as lost to the issuing bank. Any transactions with it will be declined until the cardholder resolves the issue with their bank.

Next Steps

For the Customer:

  • Contact the bank/issuer right away to resolve the lost card report

  • Use another valid card for the purchase

For the Merchant:

  • No technical action required; this is issuer-controlled

  • Advise the customer to reach out to their bank or try a different card

43

Segpay

Pickup card stolen card

🔎 What it Means
The card has been reported stolen to the issuing bank. Transactions with this card will be declined until the cardholder resolves the issue with their bank.

Next Steps

For the Customer:

  • Contact the bank/issuer immediately to resolve the stolen card report

  • Use another valid card for the transaction

For the Merchant:

  • No technical action required; this is issuer-controlled

  • Advise the customer to contact their bank or use a different card

57

Segpay

Transaction not permitted to cardholder

🔎 What it Means
The cardholder is not permitted to complete this type of transaction.

Common causes include:

  • Merchant category restrictions (e.g., adult content, high-risk merchants)

  • Issuer restrictions on online, recurring, or international payments

  • Cardholder-specific limitations imposed by the bank

Next Steps

For the Customer:

  • Use a different card that supports this type of transaction

  • Contact their bank/issuer for clarification

For the Merchant:

  • No technical action required; this is issuer-controlled

  • Advise the customer to try another card or payment method

62

Segpay

Restricted card

🔎 What it Means
The card has been restricted by the issuing bank and cannot be used for this transaction.

Common reasons:

  • Blocked for certain transaction types (e.g., online, international, high-risk merchants)

  • Cardholder-specific restrictions

  • Temporary holds or security measures imposed by the bank

Next Steps

For the Customer:

  • Use a different card

  • Contact their bank/issuer to ask about the restriction

For the Merchant:

  • No technical action required; this is issuer-controlled

  • Advise the customer to try another card or payment method

78

Segpay

Blocked Card / Issuer Restriction

🔎 What it Means
The card has been blocked by the issuing bank and cannot be used for this transaction.

Common reasons:

  • Restrictions on certain merchant categories (e.g., adult content, high-risk merchants)

  • Cardholder-specific limitations set by the bank

  • Security measures or temporary holds

Next Steps

For the Customer:

  • Use a different card

  • Contact their bank/issuer for clarification

For the Merchant:

  • No technical action required; this is issuer-controlled

  • Advise the customer to try another card or payment method

93

Segpay

Transaction cannot be completed

🔎 What it Means
The card issuer has declined the transaction because it violates cardholder or issuer rules.

Common reasons:

  • Cardholder is not permitted to make this type of transaction

  • Restrictions on high-risk merchants or categories

  • Bank-specific rules that block the transaction

Next Steps

For the Customer:

  • Try using a different card

  • Contact their bank/issuer for clarification

For the Merchant:

  • No technical action is required; this is issuer-controlled

  • Advise the customer to try another card or payment method

R0

Segpay

Transaction Declined – No Reason Given

🔎 What it Means
The card issuer has declined the transaction without specifying a reason.

Common causes:

  • Possible fraud concerns

  • Card restrictions or limits set by the issuer

  • Temporary or unexplained bank issues

Next Steps

For the Customer:

  • Try using a different card

  • Contact their bank/issuer for clarification

For the Merchant:

  • No technical action is required; this is issuer-controlled

  • Advise the customer to use another card or payment method

R1

Segpay

Revocation of authorization order

🔎 What it Means

The card issuer requires additional verification before approving the transaction.

Common causes:

Suspected fraudulent activity.

Transaction exceeds a limit or threshold set by the bank.

Bank wants to manually review the transaction.

✅ Next Steps

For the Customer:

Contact their bank/issuer to authorize or verify the transaction.

Try using a different card if the bank cannot approve immediately.

For the Merchant:

No technical action is required; this is issuer-controlled.

Advise the customer to contact their bank or try another card.

R3

Segpay

Revocation of all authorization

🔎 What it Means
The cardholder or bank has canceled all recurring payment authorizations. This card can’t be used for future recurring charges.

Next Steps

For the Customer:

  • Contact your bank if you didn’t request the cancellation.

  • Use another card to continue billing.

For the Merchant:

  • No action needed; this is issuer-controlled.

  • Let the customer know their recurring authorization was revoked and request another card.

19

Segpay

Re-Enter Transaction

🔎 What it Means
A temporary issue or processing error prevented the transaction.

Next Steps

For the Customer:

  • Retry the transaction.

  • Check card details are correct.

  • Use another card if it keeps failing.

For the Merchant:

  • Safe to retry; this is usually a soft decline.

  • Contact Segpay if the problem continues.

51

Segpay

Insufficient Funds

🔎 What it Means
The cardholder doesn’t have enough funds or credit to complete the transaction.

Next Steps

For the Customer:

  • Check account balance.

  • Retry when funds are available.

  • Use another card if needed.

For the Merchant:

  • This is a soft decline; safe to retry.

  • Ask the customer to use another card if it keeps failing.

59

Segpay

Suspected Fraud

🔎 What it Means
The card issuer flagged the transaction as possible fraud.

Next Steps

For the Customer:

  • Contact your bank to confirm the transaction.

  • Use another card if needed.

For the Merchant:

  • Hard decline — don’t retry.

  • Advise the customer to call their bank or use another payment method.

61

Segpay

Exceeds Withdrawal/Transaction Limit

🔎 What it Means
The transaction exceeds the cardholder’s spending or withdrawal limit.

Next Steps

For the Customer:

  • Use a smaller amount or another card.

  • Contact your bank to check or raise the limit.

For the Merchant:

  • You may retry with a different card.

  • Advise the customer to try another card or payment method.

65

Segpay

Exceeds Spending Limit

🔎 What it Means
The cardholder’s transaction was declined because it went over their available balance or set spending limit.

Next Steps
Customer: Check balance or credit limit, wait for reset, or use another card.
Merchant: No action needed—advise the customer to try a different payment method.

75

Segpay

PIN Tries Exceeded / Card Locked

🔎 What it Means
The card was declined because the wrong PIN was entered too many times or the bank locked the card.

Next Steps
Customer: Contact the bank to unlock the card or reset the PIN, or use another card.
Merchant: No action needed—advise the customer to reach out to their bank or try a different card.

86

Segpay

Cannot Verify PIN / Authorization Failed

🔎 What it Means
The card issuer couldn’t verify the PIN or the authorization failed.

Common causes:

  • Wrong PIN entered.

  • Temporary issuer system issues.

  • Card or transaction type restrictions.

Next Steps
Customer: Double-check the PIN and try again. If it continues, contact the bank or use another card.
Merchant: No action needed—advise the customer to retry or use a different payment method.

91

Segpay

Issuer or Network Unavailable

🔎 What it Means
The bank or payment network couldn’t be reached to process the transaction.

Common causes:

  • Network or communication issues

  • Bank or processor systems offline

Next Steps
Customer: Wait a few minutes and try again, or use another card.
Merchant: No action needed—advise the customer to retry or use a different payment method.

96

Segpay

Issuer or Switch Inoperative / Unable to Process

🔎 What it Means
The card issuer or payment network couldn’t be reached to authorize the transaction.

Common causes:

  • Temporary network or communication issues

  • Bank or processor systems offline

Next Steps
Customer: Wait a few minutes and try again, or use another card if the issue continues.
Merchant: No action required—advise the customer to retry or use a different payment method.

N3

Segpay

Cash Service Not Allowed

🔎 What it Means
The card issuer does not permit cash-related transactions with this card.

Common causes:

  • Attempting a cash advance or cash-equivalent purchase

  • Restrictions on certain card types (e.g., debit, prepaid)

Next Steps
Customer: Use the card only for standard purchases, or try another card for cash services.
Merchant: No action needed—advise the customer to use a different card or adjust the transaction type.

N4

Segpay

Restricted Card / Merchant Not Allowed

🔎 What it Means
The bank has restricted this card from being used with this merchant or type of transaction.

Common causes:

  • Merchant category restrictions (e.g., adult or high-risk)

  • Limits on international or online purchases

  • Bank-specific restrictions on the cardholder’s account

Next Steps
Customer: Try another card that supports this type of purchase or contact the bank for details.
Merchant: No action needed—advise the customer to use a different payment method.

14

Segpay

Restricted Card / Merchant Not Allowed

🔎 What it Means
The card issuer has blocked this card from being used with this merchant or type of transaction.

Common causes:

  • Merchant category restrictions (e.g., adult or high-risk)

  • International or online transaction limits

  • Bank-specific restrictions on the cardholder’s account

Next Steps
Customer: Use another card that supports this type of purchase, or contact the bank for clarification.
Merchant: No action required—advise the customer to try a different payment method.

54

Segpay

Expired Card

🔎 What it Means
The card is no longer valid because its expiration date has passed.

Next Steps
Customer: Use a valid, active card and double-check the expiration date.
Merchant: No action needed—advise the customer to provide a valid card.

55

Segpay

Incorrect PIN

🔎 What it Means
The entered PIN was incorrect, so the issuer declined the transaction.

Common causes:

  • Typing error

  • Forgotten PIN

  • Card temporarily blocked after multiple wrong attempts

Next Steps
Customer: Re-enter the correct PIN, or contact the bank to reset it. Use another card if needed.
Merchant: No action required—advise the customer to retry with the correct PIN or a different card.

82

Segpay

CVV Verification Failed

🔎 What it Means
The transaction was declined because the card’s security value (CVV, CAM, dCVV, or iCVV) did not match what the issuer has on file.

Common causes:

  • Wrong CVV entered

  • Security code mismatch due to issuer verification systems

Next Steps
Customer: Re-enter the correct CVV exactly as shown on the card. If the problem continues, contact your bank or try another card.
Merchant: No action needed—this is issuer-controlled. Advise the customer to recheck the CVV or use a different payment method.

N7

Segpay

Invalid CVV

🔎 What it Means
The transaction was declined because the CVV (security code) was entered incorrectly or did not match the issuer’s records.

Common causes:

  • Incorrect or mistyped CVV

  • Cardholder misread the digits

  • Security mismatch with the issuer

Next Steps
Customer: Re-enter the CVV exactly as shown on the card. If it still fails, contact your bank or try another card.
Merchant: No action required—this is issuer-controlled. Advise the customer to check the CVV or use a different payment method.

14

Segpay

Invalid Card Number

🔎 What it Means
The card number entered is invalid or not recognized.

Common causes:

  • Mistyped card number

  • Wrong details entered

  • Expired or inactive card

Next Steps
Customer: Recheck the card number and try again, or use another card.
Merchant: No action needed—advise the customer to verify details or use a different payment method.

54

Segpay

Expired Card

🔎 What it Means
The transaction was declined because the card has passed its expiration date.

Common causes:

  • Card expired and no longer valid

  • Wrong expiration date entered

Next Steps
Customer: Use a valid card and check the expiration date carefully. Contact the bank for a replacement if needed.
Merchant: No action required—advise the customer to use a valid, unexpired card.

3

Segpay

Invalid Merchant

🔎 What it Means
The transaction was declined because the merchant ID is invalid or not recognized by the card issuer.

Common causes:

  • Invalid or inactive merchant account

  • Processing error with the payment gateway

Next Steps
Customer: Try again later or use a different payment method.
Merchant: Contact CCBill support to verify your merchant account status.

13

Segpay

Invalid Amount

🔎 What it Means
The transaction was declined because the payment amount was invalid.

Common causes:

  • Entered amount is zero or not allowed

  • Amount exceeds the card or merchant limits

Next Steps
Customer: Recheck the transaction amount and try again, or use another payment method.
Merchant: Verify the charge amount and ensure it meets processor and card issuer requirements.

57

Segpay

Transaction Not Allowed

🔎 What it Means
The transaction was declined because the card cannot be used for this type of purchase.

Common causes:

  • Card restricted from online, international, or high-risk transactions

  • Bank-imposed merchant category restrictions

Next Steps
Customer: Contact your bank to check restrictions, or use another card that supports this type of purchase.
Merchant: No action required—advise the customer to reach out to their bank or try a different payment method.

61

Segpay

Exceeds Withdrawal/Spending Limit

🔎 What it Means
The transaction was declined because the cardholder exceeded their spending or withdrawal limit.

Common causes:

  • Daily, weekly, or monthly limits set by the bank

  • Transaction amount is higher than the available balance or credit

Next Steps
Customer: Check your balance or credit limit, wait until the limit resets, or use another card.
Merchant: No action required—advise the customer to try again later or use a different payment method.

62

Segpay

Restricted Card / Invalid Transaction

🔎 What it Means
The card issuer blocked the transaction because this type of purchase isn’t allowed with the card.

Common causes:

  • Bank restrictions on certain merchant categories (e.g., adult or high-risk sites)

  • Card not enabled for international or online use

  • Cardholder-specific limits set by the issuer

Next Steps
Customer: Try another card or contact your bank to enable online/merchant transactions.
Merchant: No action required—this is issuer-controlled. Advise the customer to retry with a different card or payment method.

65

Segpay

Exceeds Withdrawal / Activity Limit

🔎 What it Means
The transaction was declined because the cardholder has reached their daily or transaction limit set by the bank.

Common causes:

  • Daily spending or withdrawal cap exceeded

  • Too many transactions attempted in a short time

  • Bank security limits on certain purchase amounts

Next Steps
Customer: Wait and try again later, or contact your bank to raise the limit. Use a different card if needed.
Merchant: No action required—this is issuer-controlled. Advise the customer to retry later or use another payment method.

41

Segpay

Lost Card, Pickup Requested

🔎 What it Means
The transaction was declined because the card has been reported lost and is blocked by the issuer.

Common causes:

  • Cardholder reported the card as lost or stolen

  • Bank flagged the card for security reasons

Next Steps
Customer: Contact your bank for a replacement card. Use another valid card for the transaction.
Merchant: No technical action required—this is issuer-controlled. Advise the customer to use a different card.

43

Segpay

Stolen Card, Pickup Requested

🔎 What it Means
The transaction was declined because the card has been reported stolen and is blocked by the issuer.

Common causes:

  • Cardholder reported the card stolen

  • Issuer flagged the card for suspected fraud

Next Steps
Customer: Contact your bank immediately and request a replacement card. Use another valid card for payments.
Merchant: No technical action required—this is issuer-controlled. Advise the customer to use a different card.

55

Segpay

Incorrect PIN

🔎 What it Means
The transaction was declined because the PIN entered was incorrect.

Common causes:

  • Wrong PIN typed in

  • Cardholder forgot their PIN

  • Too many failed attempts may temporarily block the card

Next Steps
Customer: Double-check and re-enter the correct PIN. If the issue continues, contact your bank to reset the PIN or use another card.
Merchant: No action required—this is issuer-controlled. Advise the customer to retry with the correct PIN or a different card.

63

Segpay

Security Violation / CVV Error

🔎 What it Means
The transaction was declined because of a CVV (security code) verification failure or another security mismatch.

Common causes:

  • Incorrect CVV entered

  • Security code doesn’t match the issuer’s records

  • Card flagged for a security violation

Next Steps
Customer: Re-enter the CVV exactly as shown on your card. If it still fails, contact your bank or try another card.
Merchant: No technical action required—this is issuer-controlled. Advise the customer to verify the CVV or use a different card.

1

Segpay

Refer to Issuer

🔎 What it Means
The transaction was declined by the card issuer, but no specific reason was provided. The customer must contact their bank for details.

Common causes:

  • General decline with no explanation

  • Possible account restrictions, flags, or issues requiring issuer review

Next Steps
Customer: Contact your bank/issuer for more information or try another card.
Merchant: No technical action required—this is issuer-controlled. Advise the customer to reach out to their bank or use a different card.

2

Segpay

Refer to Issuer (Special Condition)

🔎 What it Means
The card issuer declined the transaction and requires the cardholder to contact their bank for more information.

Common causes:

  • Issuer-specific restrictions or flags

  • Possible fraud prevention or account issue

Next Steps
Customer: Contact your bank/issuer for details or try another card.
Merchant: No technical action required—this is issuer-controlled. Advise the customer to reach out to their bank.

3

Segpay

Invalid Merchant

🔎 What it Means
The transaction was declined because the merchant is not recognized or not permitted by the card issuer.

Common causes:

  • Merchant not set up properly with the issuer

  • Card issuer blocks transactions with this merchant category

Next Steps
Customer: Try another card or contact your bank for clarification.
Merchant: Contact your processor if this occurs frequently, but typically no action is needed—this is issuer-controlled.

4

Segpay

Pick Up Card (No Fraud)

🔎 What it Means
The card issuer has declined the transaction and is requesting the card be retained by the merchant. This usually means the card is no longer valid for use.

Common causes:

  • Expired, canceled, or restricted card

  • Issuer requested card retrieval for administrative reasons

Next Steps
Customer: Contact your bank/issuer for a replacement card. Use another valid card for the transaction.
Merchant: No technical action required—this is issuer-controlled. Do not attempt further charges on this card.

21

Segpay

No Action Taken / Unable to Complete

🔎 What it Means
The card issuer could not process the transaction and did not complete authorization.

Common causes:

  • Temporary system or network issue

  • Issuer declined without giving a specific reason

Next Steps
Customer: Wait a few minutes and try again, or contact your bank if the problem continues. Using another card may also help.
Merchant: No technical action required—this is issuer-controlled. Advise the customer to retry or use another payment method.

22

Segpay

Suspected Malfunction

🔎 What it Means
The issuer declined the transaction because of a system or processing error—not an issue with the card itself.

Common causes:

  • Temporary malfunction with the card network or issuer’s system

  • Communication or authorization error

Next Steps
Customer: Retry the transaction after a short time. If the issue continues, contact your bank or try another card.
Merchant: No technical action required—this is issuer-controlled. Advise the customer to retry or use a different card.

2

Segpay

Cardholder only wishes to stop one specific payment in the recurring payment relationship.

🔎 What it Means
The customer asked to cancel one payment in their subscription, but not the whole plan. Since recurring payments are set up as ongoing, Segpay can’t block just one payment.

Next Steps
Customer: Contact your bank to confirm. If you want to pause or cancel, use the merchant’s subscription management options.
Merchant: Don’t retry the payment until clarified. Confirm with the customer if they want to skip one charge or fully cancel the subscription.

3

Segpay

Cardholder has requested to stop all recurring payment transactions for a specific merchant.

🔎 What it Means
The customer asked their bank to stop all recurring payments for this subscription. Any future charges will be declined.

Next Steps
Customer: No action needed if you want the subscription canceled. Contact the merchant if you’d like to restart it or explore other options.
Merchant: Don’t try to charge this card again. Update your records to mark the subscription as canceled.

21

Segpay

All recurring payments have been cancelled for the card number requested.

🔎 What it Means
The bank or customer has stopped all recurring payments on this card. Any future subscription charges will be declined.

Next Steps
Customer: Nothing to do if you want payments canceled. To restart, update your card details or re-subscribe with the merchant.
Merchant: Don’t attempt new charges. Update your records to mark the subscription as canceled.

Segpay

Segpay

Segpay

Segpay

Did this answer your question?