What Does Code 43: Stolen Card, Pick Up Mean?
The credit card transaction decline code 43, “Stolen card, pick up,” indicates that the payment card used in the transaction has been reported as stolen. The issuer of the card is requesting that the merchant retain the card if possible. This is a security measure to prevent further unauthorized use and to assist in recovering the stolen card. If you encounter this code, it’s advised to contact the card issuer and follow their instructions, which usually involve not completing the transaction and keeping the card if it is physically present.
Key Takeaways
- Code: 43
- Standard meaning: Stolen card, pick up; fraud account
- Plain-English meaning: The card has been reported stolen or flagged as a stolen-card fraud account
- Likely source: Issuer stolen-card status, hot-card file, card-network response, processor mapping, or fraud-account flag
- Best customer-facing action: Keep the message neutral and request another approved payment method only if policy allows
- Best merchant action: Stop the transaction, avoid retries, protect staff, document the event, and do not fulfill card-not-present orders
Code 43 is the payment system’s red flag for a card reported stolen. It is serious, but the merchant’s job is not to play detective or escalate the situation.
The right response is calm and controlled: stop the sale, protect staff, avoid accusations, document the event, and follow processor instructions.
What Code 43 Means in Plain English
When a cardholder reports a card stolen, the issuer blocks that account from new use. If someone tries to use that card after it has been flagged, the authorization system can return Decline Code 43: Stolen Card, Pick Up.
The phrase “pick up” comes from card-present acceptance. It means the issuer may want the merchant to retain the physical card. That instruction should never override employee safety, store policy, processor rules, or common sense.
For ecommerce, subscription, MOTO, and virtual-terminal orders, there is no card to pick up. The merchant should decline the transaction, hold or cancel fulfillment, and preserve the details for fraud review.
Common Reasons Code 43 Happens
Code 43 is narrower and more serious than many decline codes. It usually means the card has already been reported stolen or flagged as a fraud account.
- Cardholder reported the card as stolen
- Issuer flagged the account as a stolen-card fraud account
- Card number appears on a hot-card or restricted-card file
- A stolen card is attempted at an in-person terminal
- A stolen card number is used in an ecommerce or MOTO transaction
- Stored card data belongs to a card that has since been reported stolen
- Subscription rebill attempts a card after the issuer has blocked it
- Fraud screening and issuer data conflict with the order details
- The card was used after cardholder or issuer fraud reporting
- Processor returns Code 43 as a hold-call or pick-up-card response
Code 43 is related to Code 41, but not identical. Code 41 usually means the card was reported lost. Code 43 means the card was reported stolen, which generally carries stronger fraud concern.
What the Merchant Should Do
Handle Code 43 as a safety-first fraud-account stop.
- Stop the transaction immediately. Do not retry, override, or continue the sale on that card.
- Protect staff and customers. Never physically confront a person or create a risky situation over a card.
- Retain the card only if safe and required by policy. Follow processor, terminal, store, and local procedures.
- Keep the customer message brief. Say the issuer declined the transaction and another payment method is needed only if your policy allows.
- For ecommerce or MOTO, do not fulfill the order. Hold or cancel the order and review fraud signals before any shipment or service access.
- Document the event. Record date, time, amount, channel, order ID, card brand, BIN range, response code, and staff notes.
What Not To Do
Code 43 is serious, but the wrong reaction can make the situation worse.
- Do not retry the card.
- Do not force or voice-authorize the transaction without processor direction.
- Do not accuse the customer in person.
- Do not put staff at risk trying to seize a card.
- Do not ship or provide services on an online order after Code 43.
- Do not ignore repeated Code 43 events from one checkout, campaign, BIN range, or customer profile.
The merchant does not need to solve the crime. The merchant needs to stop the payment, follow policy, and protect the business.
When Merchants Should Look Deeper
One Code 43 may be a single stolen-card attempt. Repeated Code 43 events deserve fraud and checkout review.
- Ecommerce orders with mismatched billing and shipping details
- High-ticket products or fast-shipping orders
- MOTO or manually keyed transactions
- Subscription rebills using old stored credentials
- Orders from new customers with unusual email, device, or IP signals
- Multiple attempts from the same customer, address, IP, or device
- Specific BIN ranges, issuers, countries, or card brands
- Promotions that attract fraud testing or carding attempts
- Retail locations or staff workflows with repeated pick-up-card responses
- Gateway, fraud-filter, or velocity-rule gaps
If Code 43 clusters around the same product, traffic source, country, device profile, or checkout flow, the issue may be fraud exposure rather than normal decline noise.
How Durango Merchant Services Can Help
Durango Merchant Services helps merchants interpret decline codes as risk, revenue, and operations signals.
For high-risk, ecommerce, MOTO, subscription, travel, nutraceutical, large-ticket, and cross-border merchants, Code 43 can affect fraud exposure, chargeback risk, fulfillment rules, staff training, and processor confidence.
The fix may involve better fraud screening, stronger velocity controls, clearer fulfillment holds, safer staff procedures, improved token and stored-card management, or a processor and gateway better suited to your business model.
If Code 43 or other fraud-account declines keep showing up in your reports, contact Durango Merchant Services. We can help you review the pattern, protect legitimate sales, and reduce avoidable fraud exposure.
FAQs For Decline Code 43
It means the card has been reported stolen or flagged as a stolen-card fraud account. The issuer declined the transaction and may instruct the merchant to pick up or retain the card if it is safe and allowed by policy.
No. Code 43 is a hard decline. Do not retry, override, or force the transaction through unless your processor gives a specific approved instruction.
Only follow processor, terminal, store, and local policy, and only if it is safe. Staff safety comes first. Do not confront a customer or create a dangerous situation over a card.
Cancel or hold the order, do not fulfill based on that failed payment, document the transaction, and review the order for fraud signals before taking any further action.