Card-Not-Present (CNP) refers to a payment transaction where the physical credit or debit card is not presented to the merchant at the time of the transaction. This is the standard model for e-commerce, mail-order, and telephone-order (MOTO) businesses. In the deterministic world of payment risk, CNP transactions are considered significantly higher risk than Card-Present (CP) transactions because they are more susceptible to unauthorized usage and stolen card data.
Because the merchant cannot physically verify the card or the cardholder's identity, platforms like Stripe require additional data points to mitigate risk, such as CVC Check, AVS, and 3D Secure (3DS). High volumes of CNP transactions without these security layers often lead to a High Dispute Rate and subsequent Payout Holds and Rolling Reserves. Merchants must maintain high Risk Confidence by providing clear Website Trust and Disclosures.
Why this term matters for Stripe account risk
Card-Not-Present (CNP) is not only a vocabulary item. It is a live risk signal that influences how Stripe evaluates dispute exposure, payout predictability, and verification confidence for your account. When this signal appears together with abnormal refund velocity, delivery uncertainty, or weak policy disclosures, account controls can become stricter. Treat Card-Not-Present (CNP) as an operational metric that should be monitored, documented, and explained with evidence.
Diagnostic signals to review weekly
- Track trend direction, not just a single snapshot. A persistent rise is more important than one isolated spike.
- Compare this signal with fulfillment timing, support response speed, and billing clarity to identify root causes.
- Document the exact trigger conditions so your team can reproduce, audit, and resolve the issue consistently.
- Escalate early when this term appears alongside dispute-heavy reason codes or repeated verification requests.
Practical actions to improve confidence
- Define an internal threshold and owner for this signal so actions are not delayed.
- Link this signal to a checklist in your operations workflow (checkout, fulfillment, support, and evidence retention).
- Update website disclosures and receipts so customer expectations match real delivery and billing behavior.
- Keep a short incident log with timeline, root cause, and remediation to support future platform reviews.
Further reading
- Problem: Identity Verification Failed
- Problem: Representative Authorization Failed
- Guide: Policy Pages Template: What to Include
- Hub: Payout Holds and Rolling Reserves
- Glossary Index: All glossary terms
Where This Appears
Card-Not-Present (CNP) commonly appears in the following Stripe risk scenarios: