Card not present (CNP)

Credit-card transactions where the card is not physically presented (e-commerce, phone, mail order).

Definition

Card not present (CNP) transactions are credit-card transactions completed online, by phone, or by mail without physical card swipe. Higher fraud risk; higher processing fees; chargeback liability on merchant.

Context

Most Delaware LLC e-commerce and SaaS transactions are CNP. Stripe and PayPal optimize for CNP.

Example

A Delaware LLC Shopify store processes 100% CNP transactions. Stripe charges standard 2.9% plus $0.30 per transaction.

Common pitfalls

Chargeback liability rests with merchant.
Implement fraud-prevention tools (Stripe Radar, fraud screening).

What card not present really describes for a Delaware LLC

Card not present, usually shortened to CNP, is a payment industry category that describes any transaction where the customer's physical card never touches a terminal or reader controlled by your business. The card number, expiry date, and security code travel as data rather than as a swipe, dip, or tap. For a non-resident founder running a Delaware LLC, this is almost certainly the only kind of card transaction the business will ever process, because the company exists primarily as an online entity selling to customers who could be anywhere on the planet. There is no storefront counter, no point of sale device, and no employee handing back a receipt. Everything happens through a checkout page, an invoice link, a subscription billing system, or an API call.

Understanding the category matters because the payments world treats CNP and card present transactions very differently in terms of pricing, fraud exposure, and who absorbs losses when something goes wrong. The glossary definition already notes that CNP carries higher fraud risk, higher processing fees, and merchant chargeback liability. Those three consequences flow directly from the fact that nobody verified a real human holding a real card. When you build a Delaware LLC that takes payment online through Stripe, PayPal, or a similar processor, you are stepping into the CNP world by default, and the way you design checkout, store customer data, and respond to disputes will shape how much of that risk actually lands on your company.

It helps to think of CNP not as a single product but as a status that attaches to a transaction. The same Visa or Mastercard credential can be card present at a coffee shop and card not present an hour later on your website. The rules, fees, and liabilities shift based on that status, and your job as a founder is to recognize that an online-first Delaware LLC operates almost entirely in the higher-risk half of that split.

Why CNP is the default for a foreign-owned single-member LLC

A single-member LLC owned by someone living outside the United States is usually built to sell software, digital products, services, or physical goods over the internet. The owner may never set foot in Delaware or anywhere in the country. There is no reason to own a physical card terminal, and most payment hardware is impractical to operate from abroad anyway. As a result, the company's entire revenue stream tends to arrive through card not present channels: a Shopify checkout, a Stripe payment link, a subscription managed inside a SaaS billing tool, or a marketplace that settles funds to your account. This is simply the shape of the modern remote business, and it is the shape the glossary entry assumes when it says most Delaware LLC e-commerce and SaaS transactions are CNP.

Because the founder is a non-resident, the banking and processing setup also leans on services that are comfortable with remote, document-based onboarding. Mercury, Wise, Relay, Lili, and Payoneer are commonly used to hold and move the money that card processors pay out. These accounts receive the net settlement after a processor like Stripe takes its cut and after any reserves or holds. The CNP nature of the business influences how those payouts behave, because processors watch CNP merchants more closely for fraud and disputes and may adjust payout timing or hold reserves when risk signals appear.

None of this requires the founder to be physically present anywhere. That is the appeal and also the reason CNP discipline matters. The same features that let you run a US company from another continent, remote onboarding, card-on-file billing, instant digital delivery, are the features that make every sale a card not present sale with the elevated scrutiny that comes with it.

How CNP fees compare to card present and why the gap exists

Processing fees for CNP transactions are generally higher than for card present transactions because the card networks price risk into their interchange categories. When a card is swiped or tapped in person, the network has strong evidence that the legitimate cardholder authorized the purchase, so the fraud risk is lower and the interchange rate tends to be lower too. When the same card is keyed into a website, that evidence is missing, so the transaction often qualifies for a more expensive interchange category. Processors pass this difference along, which is why an online-first Delaware LLC typically pays a blended rate at the higher end of the published range.

The glossary example uses Stripe's standard pricing of 2.9% plus $0.30 per successful transaction for a Shopify store running 100% CNP. That figure is a useful anchor because it reflects a flat, predictable rate that bundles the underlying interchange, network assessments, and the processor's margin into one number. Flat-rate pricing is attractive for small remote businesses precisely because it removes the need to understand dozens of interchange tiers. The tradeoff is that you pay the same rate whether a given card would have qualified for a cheap or expensive category, so high-volume merchants sometimes outgrow flat pricing and negotiate interchange-plus arrangements later.

For a founder modeling unit economics, the practical takeaway is that the percentage fee and the fixed per-transaction fee both bite hardest on small-ticket sales. A $4 digital download loses a meaningful share to the $0.30 fixed component, while a $400 invoice barely notices it. CNP pricing therefore rewards bundling, raising average order value, and reducing the count of tiny transactions where the fixed fee dominates the math.

Chargeback liability and what it means in practice

The single most important consequence of operating CNP is that chargeback liability rests with the merchant, exactly as the glossary pitfalls warn. A chargeback happens when a cardholder disputes a charge with their issuing bank rather than asking your business for a refund. In a card present world, when the customer dipped a chip card, the issuer generally absorbs fraud losses because the merchant followed the secure procedure. In CNP, that protection largely disappears, and the merchant becomes the party who eats the loss when a dispute is decided against them. For a Delaware LLC owned remotely, this means the company carries financial responsibility for fraud it may have had no realistic way to detect.

When a chargeback is filed, the processor pulls the disputed amount back out of your balance, often adds a dispute fee, and gives you a window to submit evidence. You respond with proof such as delivery confirmation, IP and device data, customer communications, and your terms of service. The issuer then decides. If you lose, the funds and the fee are gone. If you win, the funds return but the fee usually does not. A pattern of chargebacks above network thresholds can push a merchant into monitoring programs that carry additional fines and, in serious cases, loss of processing access entirely.

This is why founders treat chargeback management as an operational function rather than an afterthought. Clear billing descriptors so customers recognize the charge, responsive support so people ask you for a refund before calling their bank, and good record keeping all reduce both the rate of disputes and the rate at which you lose them. Because the LLC, not the founder personally, is the merchant of record, these losses hit the company's books, which is one more reason to keep clean separation between business and personal finances.

Fraud risk and the prevention tools that matter

Higher fraud risk is the third pillar of the CNP category, and it is inseparable from the chargeback problem because most fraud surfaces later as a dispute. When a card number is entered online, a criminal using stolen credentials looks identical to a legitimate buyer until the real cardholder notices the charge. The glossary entry points specifically to fraud-prevention tools such as Stripe Radar and general fraud screening as the recommended response. These systems score each transaction against signals like the card's history, the device fingerprint, the billing and shipping mismatch, velocity of attempts, and known patterns of abuse, then block or flag the riskiest ones before they settle.

For a non-resident founder, fraud screening carries an extra wrinkle: your legitimate customers are often international too, and naive geographic rules can block real sales. A buyer in one country paying with a card issued in another, shipping to a third, looks suspicious to crude filters but may be completely genuine in a global digital business. Good tooling lets you tune sensitivity so you catch fraud without rejecting honest cross-border orders. The goal is a balance where the cost of fraud and chargebacks stays below the revenue you would lose by being too strict.

Layered defenses help. Address verification, card security code checks, 3D Secure authentication that shifts some liability back to the issuer, and machine-learning scoring each catch a different slice of risk. None is complete on its own. A practical Delaware LLC setup leans on the processor's built-in screening first, then adds friction such as step-up authentication only where the risk score justifies it, so the typical customer enjoys a smooth checkout while the suspicious one meets resistance.

A worked example: a SaaS subscription business

Imagine a non-resident founder forms a Delaware LLC to sell a project management app for $29 per month. Every customer enters their card on a signup page, and the card is stored on file so the subscription renews automatically each month. From the first signup onward, every charge is card not present. The initial signup is CNP because the customer typed the number into a form, and every renewal is CNP because the processor charges a stored credential without anyone present at all. This recurring, card-on-file model is the purest form of CNP, and it is exactly the kind of business the glossary context describes when it mentions SaaS.

At the $29 price point with Stripe's standard 2.9% plus $0.30, the founder loses roughly $1.14 per successful monthly charge, leaving about $27.86 before other costs. Over a year of a retained customer that is around $13.68 in processing fees on $348 of revenue. The founder bakes this into pricing rather than treating it as a surprise. Failed renewals add another layer, because expired or declined cards trigger retries and dunning emails, and some of those recoveries succeed while others churn. Each retry is still CNP and still carries the same fee structure when it eventually clears.

The chargeback dimension shows up when a subscriber forgets they signed up and disputes a renewal instead of canceling. The founder's defense is a recognizable billing descriptor, an easy in-app cancel button, and a record of the customer's usage. Because liability rests with the merchant, every avoidable dispute is a small loss, so reducing them is a direct contributor to the LLC's margin. This is CNP economics in miniature: predictable fees, recurring revenue, and a constant low-grade tax of fraud and dispute management.

A worked example: a physical goods Shopify store

Now consider a Delaware LLC running a Shopify store that ships physical products. The glossary example pins this exactly: 100% CNP transactions at Stripe's standard rate. Here the CNP risk profile is different from SaaS because physical fulfillment introduces shipping, tracking, and the possibility of item-not-received disputes alongside ordinary fraud. A fraudster who places an order with a stolen card wants the goods delivered somewhere, so address mismatch signals and rush-shipping requests become important fraud indicators that a digital-only business would never see.

Suppose the store sells a $120 product. At 2.9% plus $0.30, the processing cost is about $3.78, leaving roughly $116.22 before the cost of goods and shipping. The founder's real exposure, though, is the friendly fraud chargeback where a genuine customer receives the item and then disputes the charge anyway. The merchant's defense is delivery confirmation with signature on higher-value orders, accurate product descriptions to prevent not-as-described claims, and prompt communication. Because the merchant bears liability in CNP, tracking numbers and signed proof of delivery are not bureaucratic extras but the evidence that decides disputes.

Inventory makes the stakes higher than in SaaS. When a software subscription is disputed, the founder loses the revenue but nothing physical. When a shipped order is charged back fraudulently, the founder loses the revenue, the product, and the shipping cost together. That triple loss is why physical-goods CNP merchants invest more heavily in pre-shipment fraud screening, sometimes holding suspicious orders for manual review before anything leaves the warehouse, accepting a little delay in exchange for avoiding a total loss.

How CNP connects to forming the Delaware LLC

Before any card not present revenue can flow, the company has to exist as a legal entity that processors and banks will recognize. For a Delaware LLC, that starts with filing the Certificate of Formation, which carries a $110 state filing fee. This document creates the LLC and gives the founder a registered legal person that can open accounts, sign processor agreements, and act as the merchant of record on every CNP transaction. Without it, there is no entity to underwrite, and payment processors have no company to approve. The formation step is therefore the foundation on which the entire CNP payment stack is built.

Processors underwrite the business when it applies, reviewing what the company sells, its expected volume, and its risk profile. Because CNP is inherently higher risk, this underwriting matters more than it would for an in-person shop. A clean formation, a clear description of the business model, and a legitimate website all help the application succeed. The LLC structure also provides the liability separation that makes the founder comfortable carrying merchant chargeback exposure, since the company, not the individual, stands behind the transactions.

Founders should also note the ongoing obligation that keeps the entity in good standing: Delaware charges a flat $300 annual franchise tax for an LLC, due each June 1. Keeping that current ensures the company remains a valid legal person able to maintain its processor and banking relationships. A lapsed entity can jeopardize the very accounts that make CNP revenue possible, so the small annual tax is part of protecting the payment infrastructure, not a separate concern.

How CNP connects to banking and getting paid

Card not present revenue does not appear in your bank account directly from the customer. It travels through the processor first, which collects the gross charge, deducts its fee, manages any reserve, and then sends a net payout to a business bank account on a schedule. For non-resident founders, that receiving account is commonly held at Mercury, Wise, Relay, Lili, or Payoneer, since these platforms onboard remote owners through document review rather than requiring a US visit. The CNP nature of the income shapes how these payouts behave, because processors watch dispute and fraud rates and may delay payouts or hold reserves when a CNP merchant looks risky.

Opening one of these accounts generally requires the formed LLC and its federal tax identification number, so the formation and EIN steps come first and the banking follows. Once the account is live, it becomes the destination for processor settlements and the source of refunds when you proactively refund a customer to avoid a chargeback. Keeping the account funded matters, because when a dispute is lost, the processor reclaims money from your balance, and an empty balance can push the account negative or trigger holds. A healthy buffer absorbs the normal churn of CNP disputes without disrupting operations.

It is worth distinguishing the processor from the bank. Stripe, PayPal, and similar services are the payment processors that handle the CNP transaction and assume the merchant relationship with the card networks. Mercury, Wise, Relay, Lili, and Payoneer are where the resulting funds land and from which the business spends. A non-resident founder usually runs both layers in parallel, and a clean handoff between them is what turns a card not present sale into spendable money in the company's name.

How CNP connects to EIN, tax forms, and reporting

Payment processors and banks ask for the LLC's Employer Identification Number during onboarding, so the EIN is a gatekeeper to accepting card not present payments at all. A foreign-owned single-member LLC obtains its EIN by filing Form SS-4 with the IRS, and there is no charge for it. When filed by a responsible party without a US Social Security number, the process commonly runs about 8 to 10 business days by fax or mail rather than the instant online issuance available to those with a SSN. Founders typically complete this early, because almost every processor and bank application will request the number before approving CNP processing.

The income that CNP transactions generate also feeds into the company's annual federal filing obligations. A single-member LLC owned by a non-resident and treated as a disregarded entity generally has to file Form 5472 together with a pro forma Form 1120 to report reportable transactions between the LLC and its foreign owner. This is an information return rather than an income tax return for the disregarded entity, but it is taken seriously: the penalty associated with failing to file Form 5472 is $25,000. The card not present revenue, the capital the owner contributes, and money the owner withdraws can all create reportable transactions that this filing captures.

Founders should keep clean records of every CNP payout, fee, refund, and chargeback so that these filings reflect reality and so the company's books reconcile with processor and bank statements. This is general information and not tax advice, and the specifics of how a given founder reports income depend on their personal situation and any treaty positions, so professional guidance is sensible. The point here is simply that the EIN and the annual filings are the tax-side bookends around the CNP revenue the business earns.

Related terms and where CNP sits among them

Card not present is closely tied to several neighboring concepts that a founder will encounter while setting up payments. The most directly related, and the one the glossary entry links to, is Stripe payments, because Stripe is the processor most often used to accept CNP transactions for a remote Delaware LLC. Stripe and similar processors are engineered around CNP first, with their checkout flows, stored card vaults, and fraud tools all designed for the online, no-card-present world. Understanding CNP is really understanding the environment those processors operate in.

Other adjacent terms include the merchant of record, which is the legal entity that accepts the payment and bears liability, and which for your business is the Delaware LLC itself. Interchange describes the underlying network fees that make CNP more expensive than card present. The chargeback is the dispute mechanism that shifts loss to the merchant. The payment gateway and the payment processor describe the technical and financial plumbing that carries the card data and settles the funds. Reserves and rolling holds describe how processors protect themselves against the future dispute risk that a CNP merchant represents.

Knowing how these terms interlock helps a founder read processor agreements with clear eyes. When a Stripe or PayPal agreement talks about reserves, liability, and dispute fees, it is describing the consequences of operating in the CNP category. The vocabulary is dense, but it all traces back to the same root fact: nobody physically presented a card, so the system distributes the resulting risk through fees, holds, and merchant liability.

Edge cases that surprise new founders

Several CNP edge cases catch founders off guard. The first is the recurring card-on-file charge, where the customer is not present at all for renewals. These are CNP by definition and can be disputed long after the original signup, which is why descriptors and easy cancellation matter so much for subscription businesses. The second is the manually keyed phone or invoice payment, where a founder types a customer's card number into a virtual terminal. This is fully CNP and carries the same elevated fees and liability as a website checkout, even though it feels more personal than an automated flow.

A third edge case is the partial refund interacting with a chargeback. If you refund part of an order and the customer still disputes the full amount, you can end up out more than the original sale unless you act quickly and document the refund. A fourth is currency and cross-border settlement, where a non-resident founder sells in one currency and settles in another through Wise or Payoneer, adding conversion costs on top of the standard CNP processing fee. These layers can quietly erode margin if they are not modeled in advance.

A fifth edge case involves marketplaces and platforms that act as the merchant of record on your behalf. When you sell through certain app stores or marketplaces, the platform takes on the CNP liability and remits funds to you net of its cut, which changes who handles disputes and fraud. Knowing whether you or the platform is the merchant of record on a given channel tells you who actually owns the CNP risk, and that answer varies from one sales channel to the next within the same business.

Common misunderstandings about card not present

A frequent misunderstanding is that using a reputable processor like Stripe or PayPal eliminates chargeback risk. It does not. These processors provide tools to fight and prevent disputes, but the underlying liability in a CNP transaction still rests with the merchant, which is your Delaware LLC. The processor is not insuring you against fraud losses by default. Believing otherwise leads founders to skip fraud screening and dispute documentation until a wave of chargebacks teaches the lesson the hard way. The glossary pitfalls state this plainly, and it is the misconception worth correcting first.

Another misconception is that CNP fees are negotiable from day one. For a new, low-volume remote business, flat-rate pricing such as 2.9% plus $0.30 is usually the practical reality, and meaningful negotiation tends to come only with substantial volume and a track record of low disputes. Founders sometimes also assume that being card not present makes them somehow informal or exempt from rules. In fact CNP merchants face more scrutiny, not less, because the absence of a physical card is precisely what raises the risk the rules are designed to manage.

A final misunderstanding conflates the payment category with the company's legal and tax obligations. Accepting CNP payments does not change the need to keep the Delaware entity in good standing with its $300 franchise tax due June 1, to hold a valid EIN, or to file Form 5472 with its pro forma 1120 where required. The payment side and the compliance side run in parallel. CNP describes how money comes in, while formation, banking, and tax filings describe how the company stays legitimate enough to keep accepting it. Treating them as one blurred thing is a recipe for missed obligations on both fronts.

Practical posture: running a healthy CNP operation in 2026

Pulling the threads together, a non-resident founder running a Delaware LLC in 2026 should treat card not present as the normal operating environment rather than an exception. That means designing checkout and billing assuming every sale is CNP, pricing products so the 2.9% plus $0.30 style fee and the occasional dispute are already absorbed, and turning on the processor's fraud screening such as Stripe Radar from the start rather than after the first loss. The aim is a setup where the predictable cost of CNP is a planned line item and the unpredictable cost of fraud is held to a manageable level through tooling and good support.

On the compliance side, the same founder keeps the foundation solid: the Certificate of Formation filed for $110, the EIN secured through Form SS-4 over roughly 8 to 10 business days, the $300 franchise tax paid each June 1, and Form 5472 with its pro forma 1120 filed where required given the $25,000 penalty for getting it wrong. Worth noting separately, beneficial ownership information reporting under the Corporate Transparency Act was made exempt for US-formed entities like a Delaware LLC by the FinCEN Interim Final Rule of March 26, 2025, which removes one filing many founders had previously expected. These pieces keep the entity legitimate enough to maintain the processor and bank relationships that CNP revenue depends on.

The throughline is that card not present is where the money is made and where the risk lives, and that the formation, banking, and tax steps are what keep the doors open so that money can keep flowing. A founder who respects both halves, the payment economics and the legal upkeep, runs a CNP operation that is durable rather than fragile. This is general information and not legal or tax advice, so a founder with specific circumstances should confirm the details with a qualified professional before acting.

Related terms

Stripe Payments

Related glossary terms & guides

Form your LLC WhatsApp

WhatsApp Form your LLC