Scope. This guide covers accepting cards via PayPal only (no wallets) for EU-registered projects selling to US payers. You’ll learn what the setup is, what PayPal and partners check, which industries it fits, and how to squeeze more approvals with smart retry logic US issuers and hygiene. So, you will learn about PayPal card processing USA.
What the setup actually is (cards-only with PayPal)
PayPal’s Advanced Credit and Debit Card Checkout (part of the modern PayPal/“Expanded/Advanced” Checkout stack) lets you accept major cards without forcing buyers to log into PayPal—“guest checkout” is supported where available. You can embed card fields on your site (hosted fields) and keep your branding while PayPal processes the card. The product includes 3-D Secure support and a fraud toolkit.
Card brands in the US
PayPal advertises acceptance of Visa, Mastercard, American Express, Discover (and others where applicable). Availability depends on your account and region.
Practical note: Amex/Discover coverage can vary by product and market; ensure it’s enabled in your merchant profile to maximize Discover acceptance online US and Amex reach.
When a US payment gateway for European company makes sense (and when it doesn’t)
- If your US share is moderate and you want fast time-to-market with one integration, PayPal’s cards-only path is a quick win.
- If most of your payers are US and cross-border declines stay high, a US-domestic acquirer/MID may unlock better local recognition and Improve US authorization rate—but that’s outside a pure PayPal cards-only scope and typically requires US entity/bank account. Use A/B tests before you change stack.
What you need to get approved (and what PayPal/partners check)
- PayPal Business account with Advanced Credit and Debit Card features enabled in your developer app (Dashboard → Features → Accept payments). This is provisioned subject to business evaluation/approval.
- KYC/KYB package: legal entity data, owners/beneficials, URLs, product use-cases, pricing, refund/fulfilment terms, support contacts.
- Compliant website/checkout: clear descriptor/brand name, consistent merchant location, refund/fulfilment policies, and a reachable support channel.
- Acceptable Use: confirm your model isn’t on the prohibited/restricted list (e.g., certain adult, gambling, weapons, prescription drugs) or requiring pre-approval. High-risk categories often aren’t eligible.
- Fraud & authentication: plan for 3-D Secure where appropriate and turn on Fraud Protection (Advanced) rules once live.
- Integration path:
- Direct integration via PayPal JS SDK + hosted card fields.
- Through a PayPal-certified checkout/subscription partner (hosted checkout page, subscription logic, dunning).
WiseAlt has already shortlisted the most suitable PayPal-certified checkout/subscription partners for this scenario and will guide your onboarding end-to-end (commercials, technical integration, and fraud settings).
Do you need a partner-hosted checkout page for PayPal card processing USA?
Pros: fastest go-live, prebuilt subscriptions/vaulting, built-in dunning, and PCI surface reduction. Cons: less control over UX and some fraud/flows. For SaaS/subscriptions, a partner solution can be ideal; for custom UX, go direct and add only the modules you need. (Either way, you still pass PayPal’s underwriting for advanced card payments.)
Industries where this works well (and where it doesn’t)
Works best: SaaS, education/coaching, digital services, many retail/marketplace use-cases—i.e., low- to medium-risk models. Combine with fraud prevention high-risk controls if your profile edges upward.
Commonly limited/not allowed: many high-risk e-commerce solutions that fall into PayPal’s Acceptable Use Policy (certain gambling/iGaming, high-risk nutraceuticals, some crypto instruments, adult content, etc.). Always review the current AUP before you plan the build.
How to Improve US authorization rate with a PayPal cards-only setup
- Data hygiene: keep merchant location, descriptor, policies, and support consistent—issuers use that context to score risk.
- 3-D Secure and AVS/CVV: enable step-up only when helpful; don’t force friction on every checkout.
- Tokens & account updater equivalents: use vaulting and update flows to reduce passive churn. (Availability varies by integration.)
- Retry strategy: implement retry logic US issuers for soft declines (e.g., temporary issues/insufficient funds); cap attempts and wait between them.
- BIN routing USA (expectations): granular BIN routing USA is not something you control inside PayPal the same way as with a direct acquirer; measure results and, if needed, test a parallel US-domestic route outside PayPal to compare approvals.
- Discover acceptance online US: verify Discover/Amex are truly enabled in your profile to gain extra US coverage.
Tip: if you ever expand beyond “cards only,” a separate flow such as Pay by Bank (Plaid) (ACH via a processor that integrates Plaid account-linking) can offload card-specific declines—but that is outside this PayPal cards-only article’s scope. (Plaid is an account-connection layer that verifies bank accounts and can power ACH with user consent.)
Risk & compliance touches you shouldn’t skip
- AUP alignment (including items that need pre-approval).
- Seller Protection eligibility (where applicable) and documentation discipline for fulfilment—helps with chargebacks and disputes.
- Fraud Protection Advanced tuning: rules, allow/deny lists, risk signals; consider 3-D Secure for risky cohorts.
- Testing before go-live: sandbox flows and edge-cases (PayPal/Braintree publish test cards and responses).
Quick implementation checklist for PayPal card processing USA
- PayPal Advanced/Expanded Checkout (cards, 3-D Secure) and Fraud Protection Advanced.
- PayPal Payment Methods (card brands in the US).
- Guest checkout (pay by card without PayPal account).
- Acceptable Use Policy / Supported activities & pre-approvals.
- Braintree/PayPal test cards (pre-go-live).