Card-present (CP)

Card-present transactions are the in-person side of card acceptance: a chip card dipped into a terminal, a contactless tap, a phone using Apple Pay or Google Pay at a reader. Because the card is read electronically and the cardholder is physically there, the networks treat these transactions as lower-risk than card-not-present, and that difference shows up in both cost and liability.

How it works, and what it costs

EMV chip and contactless transactions generate a dynamic cryptogram per transaction, so captured data cannot be replayed the way stolen card numbers can. That security earns lower interchange: a consumer credit card dipped at a retailer might qualify around 1.5–1.8% plus $0.10, where the same card keyed into a website often costs 0.4–0.8 percentage points more. Liability follows the technology too: since the US EMV shift, counterfeit-card fraud at a merchant that supports chip acceptance is generally the issuer’s problem, while a merchant still swiping magnetic stripes eats it.

Modern card-present stacks also involve real engineering: terminal management, point-to-point encryption so card data never touches the merchant’s systems, tokenization for linking in-person customers to stored profiles, and offline handling when connectivity drops.

Why it matters

For software platforms serving physical-world verticals (field services, healthcare, restaurants, retail), card-present support is often the difference between owning the full payment relationship and ceding it to a countertop terminal from another provider. The evaluation questions: which terminals are supported, how do in-person and online transactions unify in reporting, and does a semi-integrated model keep your software out of PCI scope?

QorPay handles card-present acceptance through QorConnect and Qor@theEdge, processed on the same QorCommerce platform as card-not-present and ACH volume.