---
title: "Payment Friction"
url: "https://mahouse.world/glossary/payment-friction"
type: "glossary term"
topic: "Payments"
author: "Ihor Vlasov"
reviewed: "2026-09-20"
published: "2026-08-06"
---

# Payment Friction

Payment friction is any step in a payment that costs the customer effort, time or attention — entering card details, creating an account, a redirect to a bank page, a one-time code, a failed attempt and a retry — and each step measurably reduces completion. Removing friction raises conversion by points that compound into revenue; adding it where risk requires is the control regulation and fraud demand. The design skill is putting friction where it prevents loss and nowhere else.

**Also known as:** Checkout friction, Transaction friction, Friction in payments, Frictionless payments

## Key facts

- **Used at:** e-commerce checkout, in-app payments, subscription sign-up, account funding, transfers, loan drawdown, and any flow where a customer must act to move money
- **Binding:** PSD2's strong customer authentication requires two-factor authentication on electronic payments, with exemptions (low value, low risk by transaction risk analysis, recurring, trusted beneficiaries) that the industry uses to keep most transactions frictionless; consumer-protection rules require some friction (confirmation of terms, cooling-off); fraud-prevention duties under the UK's authorised-push-payment reimbursement rules make a confirmation step on transfers a defence
- **Typical costs of friction:** cart abandonment of 70% on average across e-commerce, with payment-step causes (forced account creation, long forms, lack of preferred method, security concerns) accounting for a large share; SCA challenges lose 10–25% of challenged transactions; a redirect loses several points; a decline without a retry path loses the sale
- **Typical removals:** network tokens and saved credentials; wallets (Apple Pay, Google Pay, PayPal); guest checkout; address autofill; frictionless 3-D Secure 2 flows using risk data; SCA exemptions where the fraud rate permits; smart retries and decline messaging; local payment methods where cards are not preferred
- **Parties:** merchants and their conversion teams, payment providers and orchestrators who supply the tools, issuers whose authentication decisions determine friction, the schemes, the regulators who set the floor, and the fraud teams who need some friction to remain

## How payment friction works in practice

A merchant's checkout asks the customer to create an account, enter a card number, expiry and CVV, type a billing address, and complete a 3-D Secure challenge on every transaction. Each step loses buyers: 25% leave at account creation, 8% at card entry, 5% at the address, 12% at the challenge. A redesign: guest checkout, Apple Pay and Google Pay buttons above the form, saved cards as network tokens with address on file, and a 3-D Secure 2 integration that sends the issuer device, history and basket data so 85% of transactions are authenticated without a challenge under the acquirer's transaction-risk-analysis exemption. Conversion at the payment step rises from 62% to 81%. Fraud does not rise, because the exemption applies only to low-risk transactions and the challenges concentrate on the rest.

Friction is also a control, and the same design discipline puts it where it belongs. A transfer of €20,000 to a new payee gets a confirmation screen, a name check against the account and a warning about impersonation scams, because the loss it prevents dwarfs the seconds it costs. A card payment at a new merchant from a new device gets a challenge. A loan drawdown gets the affordability check the rules require. The fraud team's models decide, transaction by transaction, which side of the line each one falls on; the product team designs the frictionless path for the majority and the friction for the minority so that both are clear. For a fintech, payment friction is a conversion budget spent on risk; for a buyer, a target's authorisation and conversion rates against its fraud rates show how well it spends it.

## Example

A subscription service loses 11% of new sign-ups at the payment step and sees 3% of its payment attempts fail on 3-D Secure challenges. Analysis: the service challenges every transaction because its acquirer had not enabled exemptions; its card form has no wallet option; declined cards are told "payment failed" with no reason. Changes: transaction-risk-analysis exemptions enabled (the service's fraud rate of 0.08% qualifies it for the €250 threshold), wallets added, decline codes mapped to messages ("insufficient funds — try another card"; "your bank declined — call them or try another"), and a retry with a different card offered in the flow. Sign-up loss at payment falls to 4%; challenge failures to 0.6%; fraud rate unchanged at 0.08%. On €60 million of annual new-subscription revenue the change is worth €4 million a year, at an engineering cost of six weeks.

## Common mistakes

- Challenging every transaction because exemptions were never enabled.
- Forced account creation before payment.
- No wallets on a mobile checkout.
- Declines with no reason and no retry path.
- Removing the friction that fraud and regulation require, then discovering why it was there.

## Related terms

- [Cart Abandonment](https://mahouse.world/glossary/cart-abandonment.md)
- [Strong Customer Authentication](https://mahouse.world/glossary/strong-customer-authentication.md)
- [SCA Exemption](https://mahouse.world/glossary/sca-exemption.md)
- [Frictionless Flow](https://mahouse.world/glossary/frictionless-flow.md)
- [Guest Checkout](https://mahouse.world/glossary/guest-checkout.md)
- [One-Click Checkout](https://mahouse.world/glossary/one-click-checkout.md)

— Ihor Vlasov, M&A FinTech Expert. Last reviewed 2026-09-20. https://mahouse.world/authors/ihor-vlasov