Cardflo vs PayPal

Ja, og dette er et almindeligt mønster. PayPal forbliver som en tegnebog-knap, mens kortbaserede og kortfri transaktioner afregnes via Cardflos indløsere til interchange-plus-priser.

Tre ting: gennemsigtig interchange-plus-prisfastsættelse, der skalerer med volumen, indløser-redundans, så en enkelt processorfejl ikke stopper kortindtægter, og adgang til specialiserede indløsere for vertikaler, som PayPal ikke tilbyder.

Cardflo er optimeret til $5M GMV og op. Nedenfor det er PayPals alt-i-en-pakke ofte svær at slå operationelt, selvom den overordnede sats er højere.

PayPal Braintree typically prices around 2.9% + 30c blended. On $10M annual card volume with a 60/40 credit/debit split and an average ticket of $45, Cardflo's interchange-plus model with multi-acquirer routing usually lands 40 to 70 bps lower on effective rate, before the approval-rate uplift on renewal cohorts.

Card-on-file portfolios migrate via PCI-compliant vault-to-vault token export (Braintree-issued network tokens transfer directly, raw PANs pass through Cardflo's Level 1 vault). Typical timelines are 4 to 8 weeks including parallel-run validation on renewal cohorts before full cutover.

Cardflo raises card-scheme disputes through the standard Visa VROL and Mastercom flows with automated evidence submission from your order and shipping data. PayPal-branded disputes still route through PayPal's own resolution centre when the buyer paid via a PayPal wallet, and Cardflo reconciles both surfaces in one dashboard.

Every merchant gets a named payments manager plus a shared Slack or Teams channel with the acquiring, risk and engineering pods. SLAs on P1 incidents are 15 minutes to first response and 4 hours to root-cause update, materially tighter than PayPal's ticket-based enterprise support.

In most markets PayPal is a wallet and payment method, not a full card acquirer for merchants. Where PayPal offers card processing (through Braintree or PayPal Complete Payments) it operates as a single-acquirer processor. Cardflo is the acquirer / ISO layer, and PayPal sits inside Cardflo's checkout as one payment method rather than replacing the card acquiring rail.

The PayPal button converts well for its user base but leaves cost and control on the table: no interchange-plus visibility, no card-on-file portability, and dispute outcomes governed by PayPal's Buyer Protection rather than the scheme's chargeback rules. Running cards through Cardflo and offering PayPal as one method captures the conversion lift without giving up the underlying merchant relationship.

PayPal Buyer Protection operates parallel to scheme chargebacks and has its own evidence rules, timelines and outcomes. A single order can trigger both a PayPal case and a card chargeback if the buyer funded via a linked card. Cardflo consolidates both into one dispute queue with issuer / PayPal deadlines surfaced and evidence attached from order data, so ops teams do not miss the shorter PayPal windows.