Payment Verdict
Risk Topics

Card-Present (CP)

A payment transaction where the card and the cardholder are physically present at the time of purchase.

Updated March 1, 2026•3 min read

Card-Present (CP) refers to a payment transaction where the physical credit or debit card is swiped, dipped (EMV), or tapped (NFC) at a physical point-of-sale (POS) terminal. In the deterministic world of payment risk, CP transactions have significantly lower fraud rates compared to Card-Not-Present (CNP) transactions because the physical presence of the card and the use of chip technology (EMV) provide strong authentication.

For merchants primarily operating online, most transactions are CNP. However, if a merchant uses Stripe Terminal for in-person sales, those transactions are categorized as CP. Platforms like Stripe monitor the ratio of CP to CNP transactions as part of a merchant's overall risk profile. A sudden shift from CP to CNP without a corresponding business model change can be a signal of Unusual Transaction Patterns and may trigger a Payout on Hold.

Why this term matters for Stripe account risk

Card-Present (CP) 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-Present (CP) 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

  1. Define an internal threshold and owner for this signal so actions are not delayed.
  2. Link this signal to a checklist in your operations workflow (checkout, fulfillment, support, and evidence retention).
  3. Update website disclosures and receipts so customer expectations match real delivery and billing behavior.
  4. Keep a short incident log with timeline, root cause, and remediation to support future platform reviews.

Further reading

Where This Appears

Card-Present (CP) commonly appears in the following Stripe risk scenarios:

Related glossary terms

Card-Not-Present (CNP)

A payment transaction where the card and the cardholder are not physically present at the time of purchase.

AVS (Address Verification Service)

A security tool used to verify that the billing address provided by a customer matches the address on file with their card issuer.

CVC Check

A security verification that checks if the Card Verification Code provided during a transaction matches the code on file with the bank.

3D Secure (3DS)

An additional security layer for online credit and debit card transactions that provides explicit customer authentication.

Chargeback

A chargeback is a cardholder-initiated reversal via the issuing bank, often treated as a high-severity risk signal by payment platforms.

Move from definitions to diagnosis

Once the term makes sense, use the problem library and operational guides to see how it creates real Stripe account pressure.