Merchants play a critical role in preventing fraud and disputes. Fraudulent transactions can result in Disputes, loss of goods/services, operational overhead, reputational damage, and potential restrictions on payment processing if dispute/fraud levels exceed acceptable thresholds. 

1. How Payment Fraud Impacts Merchants 

• Dispute initiated by cardholders (transaction reversal) 

• Loss of goods or services already delivered (especially for physical shipments and instant digital delivery) 

• Dispute and processing fees charged by the acquiring partner 

• Higher risk classification and enhanced monitoring (which may impact authorization rates and settlement timelines) 

• Potential suspension of payment processing if fraud/dispute ratios are excessive or if prohibited activity is detected 

2. Fraud Types That May Impact Merchants (E-commerce) 

A. Stolen Card Fraud 

Fraudsters use stolen card credentials obtained from phishing, malware, data breaches, or illegal marketplaces to place unauthorized orders. 

Merchant impact: disputes, lost inventory/services, and dispute fees. 

Common warning signs: 

• High-value orders from new customers with limited history 

• Mismatch between billing country and shipping/delivery location 

• Multiple attempts with different cards before success 

• Unusual combination of items (e.g., high resale goods) or unusually large quantities 

B. Card Testing / Bot Attacks 

Fraudsters (often using bots) attempt many low-value transactions to validate stolen cards and identify those that work. 

Merchant impact: high decline volumes, gateway stress, elevated fraud risk, and potential account monitoring. 

Common warning signs: 

• Sudden spike in failed authorizations, especially low-value attempts 

• Many different cards used from the same device/IP or within short time windows 

• Repeated attempts with similar amounts and short intervals 

C. Account Takeover (ATO) 

Fraudsters gain access to customer accounts (credential stuffing, leaked passwords) and place orders using stored cards. 

Merchant impact: chargebacks and loss of goods, especially with expedited delivery. 

Common warning signs: 

• Login from new device/location followed by immediate purchase 

• Change of delivery address or phone number shortly before purchase 

• Multiple attempts or unusually high-value basket from an existing account 

D. Friendly Fraud / Dispute Fraud 

A customer disputes a legitimate transaction (e.g., claims ‘unauthorized’, ‘not received’, or ‘not as described’) after receiving goods/services. 

Merchant impact: revenue reversal, dispute fees, and increased dispute ratios. 

Common warning signs: 

• Customer contacts support with inconsistent claims or delays dispute until after delivery 

• High dispute rates for a specific product, promotion, or traffic source 

• Digital goods delivered instantly with limited evidence of consumption/usage logs 

E. Transaction Laundering / Misrepresentation 

A merchant processes payments for goods/services not disclosed during onboarding (including prohibited or restricted products). 

Merchant impact: immediate suspension/termination of processing, settlement holds, scheme compliance actions, and regulatory risk. 

3. What Merchants Should Do When Fraud Is Suspected 

1. Pause fulfillment (shipment/delivery) for the suspicious order until you complete additional verification. 
2. Check customer contact details and order consistency (email/phone plausibility, address format, and repeat behavior). 
3. Review order history and attempt patterns (multiple declines, repeated retries, multiple cards). 
4. For digital goods/services, delay instant fulfillment for high-risk orders and keep delivery/usage logs. 
5. Report promptly to PayCaps with relevant order and transaction details (see Section 7). 

4. Fraud Prevention Best Practices (Merchant Controls) 

4.1 Website & Account Security 

• Use HTTPS and maintain up-to-date website security patches. 

• Require strong passwords and consider multi-factor authentication for customer accounts (where applicable). 

• Limit excessive login attempts and implement bot protections (rate limiting / CAPTCHA) on login and checkout. 

4.2 Operational Controls 

• Apply manual review for high-value orders or unusual baskets (especially new customers). 

• Delay shipment for high-risk orders and use trackable delivery methods requiring signature where possible. 

• Ensure your refund, cancellation, and delivery timelines are clearly displayed on your website. 

• Do not accept card details via email, chat, or phone. All payments must occur through the PayCaps secure payment flow. 

5. Real E-commerce Fraud Scenarios Merchants Commonly Face 

Use the scenarios below as practical red flags. One indicator alone may not confirm fraud, but multiple indicators together should trigger additional review and/or reporting to PayCaps. 

1. A first-time customer places a very high-value order and requests urgent same-day delivery.
2. Multiple payment declines occur, followed by a successful payment using a different card.
3. Several small payments (low-value) areattemptedfrom many different cards within minutes (card testing). 
4. The customer provides a free email domain and an unreachablephone number, butinsists on quick shipping. 
5. Billing country differs from the customer’s stated location; shipping is to a third-party address.
6. Largequantitypurchase of high-resale items (electronics, giftable items) with minimal browsing history. 
7. Customer asks to change shipping address after payment approval.
8. Customer requests that the package be delivered without signature or to a courier/forwarder location.
9. Repeat orders from different customer accounts but same device/IP and same delivery address.
10. Customer refuses to provide basic order verification details (e.g., correct delivery address confirmation).
11. Customer disputesimmediatelyafter delivery confirmation, claiming ‘not received’. 
12. Customer claims ‘unauthorized’ but shipment was delivered to an address used previously by the same account.
13. Digital goods are delivered instantly; shortly after, the customer raises ‘fraud’ or ‘service not received’.
14. Customer places multiple orders across different merchants using similar amounts and patterns (cross-merchant testing).
15. Multiple failed OTP/3DS attempts occur and then a successful attempt from a different device.
16. The customer’s name does not match the deliveryrecipientname, and the recipient cannot be verified. 
17. Multiple refunds are requestedtoa different card/account than the original payment method. 
18. Abnormally high refund rate for a specific product line or marketing campaign.
19. Merchantwebsite is updated to add new products/services not approved during onboarding (risk of misrepresentation). 
20. A spike in disputes occurs after a change in pricing, promotions, fulfillment, or delivery performance.

6. Chargeback Prevention Guidance  

Most disputes are preventable through clear customer communication, strong evidence, and disciplined operational controls. The guidance below focuses on the most common dispute reasons. 

6.1 Before the Transaction: Reduce Disputes at Source 

• Show a clear descriptor on checkout and receipts (merchant name and support contact). 

• Display total amount, currency, taxes/fees, delivery timelines, and refund/cancellation terms before payment. 

• Send an order confirmation email/SMS with order summary and support channels. 

• Use clear product descriptions and accurate images to avoid ‘not as described’ disputes. 

• For subscriptions/recurring services: clearly show renewal terms, billing frequency, and cancellation steps. 

6.2 Fulfillment & Delivery: Evidence That Wins Disputes 

• Use trackable shipping with delivery confirmation (and signature for high-value items where feasible). 

• Retain proof of delivery (carrier tracking, delivery timestamp, signature, and delivery address). 

• For digital goods/services: retain access logs, download logs, account usage logs, and delivery timestamps. 

• Keep customer communications (emails/chats) and support tickets tied to the order reference. 

6.3 Refunds & Customer Support: Prevent Escalation to Chargebacks 

• Make refunds easy and timely when valid—many chargebacks occur when customers cannot reach support. 

• Provide clear timelines for refund processing and communicate status updates. 

• If you cannot fulfill an order on time, proactively offer alternatives (replacement, partial refund, cancellation). 

• Avoid partial shipments without notifying the customer; customers may dispute for ‘partial/incorrect fulfillment’. 

6.4 Dispute Readiness: What to Retain for Representment 

Maintain the following records for each order (especially high-value orders): 

• Order ID, transaction reference, date/time, amount, and currency 

• Customer name, email, phone, and delivery address 

• Order confirmation and delivery confirmation (tracking/signature) 

• Proof of service delivery or digital fulfillment logs (if applicable) 

• Refund/cancellation policy acceptance evidence (e.g., checkbox logs) 

• Customer communications and support resolution notes 

7. Reporting Suspicious Transactions to PayCaps 

If you identify suspicious activity, report it promptly to PayCaps Merchant Support to allow review and appropriate action. 

Include the following details in your report: 

• Merchant Name and Merchant ID (MID) 

• Order reference number and transaction reference number 

• Transaction amount, currency, date and time 

• Customer email/phone (if available) and delivery destination (if applicable) 

• Reason for suspicion (which indicators/scenarios apply) 

• Any supporting evidence (screenshots, logs, communication transcripts) 

8. Important Security Reminder 

Merchants must never request, capture, store, or share sensitive cardholder information outside the secure PayCaps payment flow. 

• Full card number (PAN) 

• Card PIN 

• CVV/CVC 

• One-Time Password (OTP) or bank authentication credentials 

9. Contact PayCaps 

PayCaps Technology LLC
Merchant Support Team
Email: support@paycaps.com