Buy Now Pay Later

Quick answer / Definition

Buy Now Pay Later (BNPL) is a checkout payment option that lets customers defer payment or pay in installments for an online purchase. It describes a family of services provided by third-party pay-over-time vendors (or internal merchant plans) that are presented at product pages and during checkout to reduce friction and increase purchase intent.

• What it is: A payment solution that breaks one payment into multiple scheduled payments.
• What it describes: A payment method and its adoption on orders, influencing conversion and average order value.
• Where it is used: Product pages, cart, and checkout on ecommerce sites, marketplaces, and mobile apps.
• Why it matters: BNPL can improve conversion, lift AOV, and change payment processing costs and customer behavior.

Why Buy Now Pay Later matters

For ecommerce founders and DTC brands, BNPL matters because it changes the economics of acquisition and checkout behavior. The direct business impacts include:

• Revenue & conversion: BNPL frequently increases conversion rate and average order value by reducing upfront price friction.
• Customer acquisition cost (CAC): Higher conversion can lower CAC per buyer for the same ad spend; however BNPL fees may offset part of that gain.
• Profitability: BNPL adds merchant fees and operational complexity; measure net margin after BNPL fees, returns, and chargebacks.
• Customer experience: Clear messaging around eligibility, fees, and returns affects satisfaction and returns behavior.
• Marketing performance: BNPL can enable larger-ticket promotions, different creatives, and segmented offers targeted to high-intent buyers.
• Operational efficiency: Reconciliation, refunds, and fraud handling change when third-party providers underwrite repayments.

What is Buy Now Pay Later?

BNPL is a collection of payment products that let customers make a purchase now and pay later, typically via:

• Short-term, interest-free installments (e.g., 3 equal payments over 6 weeks).
• Longer-term installment plans with interest (e.g., 6 or 12 months at a specified APR).
• Deferred-pay options (pay in full after 30 days).

What BNPL includes:

• Point-of-sale integration (widget, button, or hosted page).
• Credit decisioning by the BNPL provider for each transaction.
• Merchant settlement: the vendor typically pays the merchant upfront (minus fees) and collects repayments from the customer.

What BNPL excludes:

• Traditional credit card lending products and unsecured personal loans under the consumer's bank account.
• Layaway programs that require prepayment before shipping.

When businesses use BNPL: to reduce cart abandonment on higher-ticket items, test new audiences, and lift AOV on product collections where affordability is a barrier.

What a high or low BNPL adoption rate indicates:

• High adoption: product price or customer segment is sensitive to upfront cost; may increase average order value and new customer trials.
• Low adoption: customers prefer existing payment methods, eligibility restrictions from provider, or poor in-page messaging/UX.

Important terminology:

• Adoption rate: share of orders using BNPL.
• AOV lift: percent change in average order value for orders using BNPL versus those that don't.
• Merchant fee / take rate: percentage of transaction the BNPL provider charges the merchant.
• Underwriting/eligibility: the vendor's credit decision rules which affect approval rate.

Formula / Calculation

BNPL itself is not a single metric, but you should track measurable KPIs. Common formulas:

BNPL adoption rate = (Orders using BNPL / Total orders) × 100

Explanation: Orders using BNPL = number of completed transactions where BNPL was the selected payment method. Total orders = all completed transactions in the same time window.

Example:

1. Monthly orders = 1,800
2. Orders using BNPL = 540
3. Adoption rate = (540 / 1,800) × 100 = 30%

AOV lift for BNPL = ((AOV_BNPL - AOV_nonBNPL) / AOV_nonBNPL) × 100

Explanation: Compare average order values for BNPL vs other payment methods.

Example:

1. AOV_nonBNPL = $80
2. AOV_BNPL = $88
3. AOV lift = ((88 - 80) / 80) × 100 = 10%

Incremental revenue from BNPL = (New total revenue with BNPL) - (Baseline revenue without BNPL)

Example calculation is in the Example section below. If a metric cannot be calculated directly, measure it with analytics events, server-side order flags, or payment provider webhooks.

How BNPL works (practical flow)

1. Product/Cart display

   What happens: BNPL options and messaging are shown on product pages and cart (e.g., 'Pay in 4 interest-free payments').

   What the business measures: impressions, click-throughs to BNPL widget, and add-to-cart uplift when BNPL messaging is present.

   Why it matters: Early visibility signals affordability and alters intent before checkout.

2. Checkout selection & eligibility

   What happens: At checkout the customer selects BNPL; the provider runs quick underwriting and returns approval or decline.

   What the business measures: approval rate, decline reasons, and drop-off during this step.

   Why it matters: Approval friction can create a failure point—track declines to optimize messaging.

3. Order settlement

   What happens: The BNPL provider settles the merchant (often paying the merchant upfront minus fees) and collects payments from the consumer.

   What the business measures: settlement timing, effective payout (gross minus fees), and reconciliation accuracy.

   Why it matters: Cashflow and margin calculations depend on net settlement and timing.

4. Fulfillment & returns

   What happens: Merchant fulfills the order; returns/refunds are handled per provider rules which may affect customer repayments.

   What the business measures: return rate for BNPL orders, refund processing time, and reconciliation of returned amounts.

   Why it matters: Returns can complicate reconciliation and customer refunds, impacting net revenue and disputes.

5. Post-purchase lifecycle

   What happens: Provider manages repayment schedule and collections; merchant monitors chargebacks, disputes, and customer service tickets.

   What the business measures: chargebacks, dispute rate, customer support volume by payment type.

   Why it matters: Increases in disputes or support costs can erode the benefits of higher conversion.

Key components / Factors that influence BNPL performance

• Traffic source: Paid search vs organic vs email audiences respond differently; paid channels may convert better when BNPL is visible in ad creative.
• Device: Mobile checkout flows need compact BNPL widgets; eligibility modals must be fast to avoid mobile abandonment.
• Customer intent: High-intent shoppers for big-ticket items are more likely to choose BNPL than bargain-hunters.
• Product/category: Electronics, furniture, and premium apparel often show higher BNPL adoption than low-margin consumables.
• Pricing & thresholds: BNPL messaging for items above a threshold (e.g., $100) can drive uptake without cluttering low-ticket pages.
• Shipping & returns policy: Customer-friendly returns reduce friction; ambiguous policies increase disputes on BNPL orders.
• Checkout UX: Placement of BNPL choice, clear terms, and smooth approval flow directly affect conversion.
• Payment provider fees & settlement: Fee rate and payout timing affect margin and cashflow forecasting.
• Seasonality & promotions: BNPL uptake can spike during holidays or sales—monitor fees and fulfillment capacity.
• Analytics & tracking: Accurate event tagging, order flags, and reconciliation are required to measure real impact.

Example: realistic ecommerce scenario with calculations

Starting situation

• Monthly sessions: 100,000
• Baseline conversion rate (CR): 1.5% → baseline orders = 1,500
• Baseline AOV: $80 → baseline revenue = 1,500 × $80 = $120,000

Introduce BNPL and assumptions

• After adding BNPL, overall CR increases to 1.8% (20% relative uplift) → orders = 1,800
• BNPL orders show a 10% AOV lift: AOV_BNPL = $88; assume non-BNPL orders remain $80
• BNPL adoption rate = 30% of orders → BNPL orders = 1,800 × 0.30 = 540
• BNPL merchant fee = 3.5% charged on BNPL sales only

Calculation

• Total revenue after BNPL = (BNPL orders × AOV_BNPL) + (non-BNPL orders × AOV_nonBNPL)
• BNPL revenue portion = 540 × $88 = $47,520
• Non-BNPL orders = 1,800 − 540 = 1,260; non-BNPL revenue = 1,260 × $80 = $100,800
• Gross revenue = $47,520 + $100,800 = $148,320
• BNPL fees = $47,520 × 0.035 = $1,663.20
• Net revenue after BNPL fees = $148,320 − $1,663.20 = $146,656.80

Business impact

• Gross revenue uplift vs baseline = $148,320 − $120,000 = $28,320 (23.6% increase)
• Net revenue lift after BNPL fees = $146,656.80 − $120,000 = $26,656.80 (22.2% increase)
• Cost to acquire additional 300 orders depends on ad spend; if cost per click and conversion remain, improved CR lowers effective CAC.

Interpretation: In this realistic example BNPL increased orders and AOV enough that net revenue after fees still rose substantially. Monitor returns and disputes, which would reduce net benefit.

Benchmark / What is a good BNPL metric?

There is no universal 'good' value for BNPL adoption or lift—benchmarks vary widely by category, price point, geography, and target customer. Instead:

• Use your historical store baseline as the primary benchmark.
• Compare segmented adoption (mobile vs desktop, paid vs organic traffic, new vs returning customers).
• If testing BNPL, target statistically significant changes in conversion and AOV before rolling out sitewide.

Note: public industry averages exist in analyst reports and vendor whitepapers, but they reflect specific samples and should not replace your own segmented tests.

How to improve or optimize Buy Now Pay Later performance

Prioritized strategies by likely impact:

1. Optimize placement and messaging

   What to change: Show BNPL pricing examples on product pages, shopping ads, and cart. Use real-dollar installment messaging (e.g., 'as low as $22/mo').

   Why it works: Concrete numbers reduce mental math friction and improve perceived affordability.

   How to implement: Add vendor widget, ensure server-side rendered copy for SEO, and test different formats with A/B tests.

   Monitor: product page CTR to BNPL flow, cart conversion, approval drop-off.

2. Test thresholds and eligibility messaging

   What to change: Show BNPL only above a price threshold where it lifts AOV, or personalize display by returning customer.

   Why it works: Avoids cluttering low-ticket items and focuses BNPL where it yields ROI.

   How to implement: Use server-side logic or GTM to hide/show BNPL by price or user cohort; run experiments.

   Monitor: adoption rate, AOV by cohort, and incremental conversion.

3. Reduce checkout friction

   What to change: Pre-check eligibility or streamline the BNPL approval step so it does not force a full page load or long form.

   Why it works: Lowering friction reduces drop-off during credit checks.

   How to implement: Use provider SDKs that offer popup or inline flows and measure drop-off by step.

   Monitor: decline rate, checkout abandonment at BNPL step.

4. Negotiate fees and settlement terms

   What to change: If you have volume, negotiate take rate, flat fees, and settlement timing.

   Why it works: Lower fees improve net margin and make BNPL more profitable.

   How to implement: Consolidate volume to preferred providers or bundle services (fraud, reporting) to improve leverage.

   Monitor: effective fee as percent of BNPL GMV and payout timing.

5. Instrument analytics properly

   What to change: Tag BNPL impressions, clicks, approvals, and settle events in analytics and server logs.

   Why it works: Accurate data enables cohort analysis and determines true incrementality.

   How to implement: Use order-level flags, server-side events, and reconcile with provider webhooks.

   Monitor: consistency between analytics and payments reconciliation.

Best practices

• Expose BNPL early: Show installment pricing on product pages and PPC ad copy where allowed.
• Be transparent: Clearly communicate fees, repayment schedule, and returns policy specific to BNPL orders.
• Segment reporting: Track BNPL metrics by device, traffic source, SKU, and new vs returning customers.
• Reconcile daily: Match provider settlements to platform orders to catch discrepancies quickly.
• Test incrementally: Use A/B tests with sufficient sample sizes to measure true lift in conversion and AOV.
• Monitor fraud & disputes: Track disputes and return rates for BNPL orders to avoid margin erosion.
• Negotiate with data: If you can show volume and improved retention, negotiate lower fees or marketing support.
• Consider UX for mobile: Make BNPL selection a one-tap option on mobile checkout flows.
• Train support teams: Ensure CS reps understand BNPL provider rules for refunds and customer questions.

Common mistakes to avoid

• Not tracking BNPL separately

  Why it happens: Teams rely on generic order events without tagging payment method.

  Why harmful: You cannot measure adoption, fees, or returns split by payment method.

  Correct approach: Add a payment-method dimension to orders and reconcile with provider reports.

• Ignoring net margin impact

  Why it happens: Focus on gross revenue uplift without subtracting BNPL fees, chargebacks, and returns.

  Why harmful: Can mislead management into thinking BNPL is profitable when net margin shrank.

  Correct approach: Calculate net revenue and margin by payment type.

• Poor UX around eligibility

  Why it happens: Sites show BNPL but do not explain approval criteria, causing declines and abandonment.

  Why harmful: High decline-related drop-off and customer dissatisfaction.

  Correct approach: Provide clear messaging about eligibility and next steps after a decline.

• Not A/B testing

  Why it happens: Teams assume BNPL will automatically improve metrics and flip it on sitewide.

  Why harmful: Missed learning on which products, segments, and placements drive real lift.

  Correct approach: Run controlled experiments and measure incremental revenue.

• Inadequate returns and reconciliation processes

  Why it happens: Operations teams are unprepared for BNPL-specific refund flows.

  Why harmful: Delays and errors in refunds damage customer trust and complicate accounting.

  Correct approach: Document provider refund flows and automate reconciliation where possible.

Buy Now Pay Later vs related concepts

BNPL vs Credit Card

• BNPL: Short-term installment or deferred-payment product, often with quick approval and lower visible interest.
• Credit Card: Revolving credit line with variable interest and broader consumer protections; payments are handled by card networks.
• Key difference: BNPL usually shows installment amounts and is underwritten per transaction; credit cards offer ongoing credit and rewards tied to a card account.

BNPL vs Layaway

• BNPL: Customer receives goods immediately and pays over time; merchant may be paid upfront by provider.
• Layaway: Customer pays over time and receives goods only after final payment.
• Key difference: BNPL delivers product immediately; layaway delays delivery until paid in full.

BNPL vs Personal Installment Loan

• BNPL: Typically purchase-specific, quick approvals, often integrated at checkout with shorter terms.
• Personal loan: Broader use, longer underwriting and terms, often higher documentation and credit checks.
• Key difference: BNPL is purchase-centric and usually faster; personal loans are standalone credit products for various uses.

When should you track Buy Now Pay Later?

• Who should track it: Ecommerce founders, finance teams, growth marketers, and product managers launching or evaluating BNPL.
• Stage of business: Track from the moment you launch a BNPL option; larger merchants should track multiple providers and cohorts.
• Review frequency: Weekly for approvals, fees, and settlement checks; monthly for revenue and margin analysis; quarterly for negotiating provider terms.
• Segments to analyze: Traffic source, device, SKU/category, new vs returning, geography, and marketing campaign.
• Other metrics to view alongside BNPL: conversion rate, AOV, return rate, chargebacks, net margin, and CAC.

Related ecommerce metrics

• Conversion rate: BNPL affects whether visitors become buyers at checkout.
• Average order value (AOV): BNPL often increases AOV as customers buy more or pricier items.
• Cart abandonment rate: BNPL messaging can reduce abandonment during payment steps.
• Customer acquisition cost (CAC): Higher conversion reduces CAC per customer for the same ad spend.
• Lifetime value (LTV): BNPL may influence repeat purchase behavior and retention.
• Return rate: BNPL orders may have different return behavior; track separately.
• Chargeback / dispute rate: Essential for assessing post-purchase risk and costs.
• Payment failure rate: Approval and settlement failures affect revenue recognition and operations.

FAQs

1. How is BNPL measured?

   Measure BNPL adoption rate (orders using BNPL / total orders), AOV for BNPL orders, approval and decline rates, and net revenue after BNPL fees and returns.

2. Is BNPL always profitable?

   Not necessarily. BNPL can increase revenue but also adds fees and operational costs. Profitability depends on fee rate, change in return/chargeback rates, and incremental volume.

3. Why might BNPL not improve conversion?

   Common reasons include low visibility of the option, high decline rates, poor mobile experience, or customer segments that prefer other payment types.

4. How do I test BNPL impact?

   Run an A/B test that exposes half your traffic to BNPL and half to the baseline, and measure incremental changes in conversion, AOV, and net revenue after fees.

5. What fees should I expect?

   Fees vary by provider and contract—commonly a percentage of the transaction plus potential flat fees. Negotiate based on volume and bundled services.

6. How should returns be handled for BNPL orders?

   Follow provider rules: many providers adjust customer repayment schedules and issue merchant refunds upon confirmation. Automate reconciliation to ensure accurate refunds and accounting.

7. Which BNPL provider is best?

   There is no one-size-fits-all. Evaluate providers on fees, approval/decline behavior, settlement timing, and integrations with your stack, and benchmark with a pilot.