LogoLogo
Explore with DeepWikiJoin Slack CommunityContact Us
  • About Hyperswitch
    • Introduction
    • Payments Suite
    • Payments Modules
      • Cost Observability
      • Revenue Recovery
      • Vault
        • Server to Server Vault tokenization
        • Vault SDK Integration
      • Intelligent Routing
      • Reconciliation
        • Getting Started with Recon
      • Alternate Payment Method Widgets
        • Hyperwidget Integration Guide
    • Roadmap - Q2 2025
      • Previous Roadmap - Q1 2025
      • Previous Roadmap - Q4 2024
      • Previous Roadmap - Q3 2024
      • Previous Roadmap - Q2 2024
      • Previous roadmap - Q1 2024
      • Previous roadmap - Q4 2023
  • Use-Cases
    • For SaaS Businesses
    • For B2B SaaS Businesses
    • For E-Commerce Businesses
    • For Marketplace/Platforms
  • Explore Hyperswitch
    • Payment Orchestration
      • Accept Payments
        • Connectors
          • Activate Connector on Hyperswitch
          • Try a Payment
          • Available Connectors
            • ACI
            • Adyen
            • Airwallex
            • Authorizedotnet
            • Bambora
            • Bank of America
            • Billwerk
            • Bluesnap
            • Braintree
            • Checkout
            • Coinbase
            • Cybersource
              • Apple Pay
              • Google Pay
            • dLocal
            • Fiserv
            • GlobalPayments
            • GoCardless
            • Klarna
            • Mollie
            • MultiSafepay
            • Nuvei
            • OpenNode
            • Paypal
            • PayU
            • Prophetpay
            • Rapyd
            • Shift4
            • Stripe
            • TrustPay
            • Volt
            • Worldline
            • Worldpay
            • Zen
            • Netcetera
              • Authenticating Payments via Netcetera Through HyperSwitch SDK
        • Setup Payment Methods
          • Cards
          • Wallets
            • Apple Pay
              • Web Domain
              • iOS Application
            • Google Pay
            • PayPal
          • Pay Later
          • Banks
            • Bank Debits
            • Bank Redirects
            • Bank Transfers
            • Open Banking
          • Crypto
          • Test Credentials
        • Payment Links
          • Configurations
          • Create Payment Links
          • Secure Payment Links
          • Setup Custom Domain
        • Save a Payment Method
        • Manual Capture
        • Incremental Authorization
        • Tokenization & Card Vault
          • Network Tokenisation
        • Supported Payment Workflows
        • Co-badged Cards
        • Webhooks
      • Process Payouts
        • Getting Started with Payouts
        • Using Saved Payment Methods
        • Smart Router for Payouts
        • Smart Retries in Payout
        • Payout Links
      • Smart Routing
        • Rule Based Routing
        • Volume Based Routing
        • Default Fallback Routing
      • Smart Retries
        • 3DS Step-up Retries
      • 3DS / Strong Customer Authentication
        • Setting up 3DS Decision Manager
        • Native 3DS Authentication
        • External Authentication for 3DS
      • Fraud & Risk Management
        • Activating FRM in Hyperswitch
        • Fraud Blocklist
      • Subscriptions
        • PG Agnostic Card Forwarding
        • Zero Amount Authorization
      • Split Payments
        • Stripe Split Payments
        • Adyen Split Payments
        • Xendit Split Payments
    • Checkout Experience
      • Customizable and Native Integrations
        • Web
          • Node And React
          • Customization
          • Error Codes
          • Node and HTML
          • Vanilla JS and REST API Integration
        • Android
          • Kotlin with Node Backend
          • Customization
          • Features
        • iOS
          • Swift with Node Backend
          • Customization
          • Features
        • React Native
          • React Native with Node Backend
          • Card Widget
          • Customization
        • Flutter
          • Flutter with Node Backend
          • Customization
        • Headless SDK
        • Server Setup
      • Click To Pay
        • Visa Click to Pay: V1 to V2 Migration
      • Payment Methods Management
    • Payment Operations
      • Managing Accounts and Profiles
        • ⚙️Control Centre Account setup
        • Hyperswitch Account Structure
      • Manage Your Team
      • Analytics & operations
        • Exporting payments data
      • Disputes / Chargebacks
      • Surcharge
        • Surcharge Setup guide
      • Multi-Tenancy
      • Data migration
        • Import data to Hyperswitch
        • Export data from Hyperswitch
    • Security and Compliance
      • PCI Compliance
      • Data Security
      • GDPR compliance
      • Identity and Access Management
    • E-commerce Platform Plugins by Hyperswitch
      • 🔌WooCommerce Plugin
        • Setup
        • Roadmap
        • Compatibility
        • FAQs
      • Saleor App
        • Setup
      • Automatic Tax calculation for Express Checkout wallets
  • Hyperswitch open source
    • Overview
      • Run Hyperswitch Locally Using Docker
        • Run Additional Services
      • Development Environment Setup
        • Backend
          • Configure and Run the Application
          • Try out APIs
        • SDK (Frontend)
        • Control Center
    • Deploy on AWS
      • Deploy on AWS using CloudFormation
      • Component-wise Deployment
        • Deploy app server
        • Deploy Control Center
        • Deploy web client
          • Production ready deployment
          • Integrate web client on your web app
          • Playground deployment for prototyping (optional)
        • Deploy Card Vault
          • Production ready deployment on AWS
          • Cloud setup guide
    • Deploy on Kubernetes
      • Deploy on GCP Using Helm Charts
      • Deploy on Azure Using Helm Charts
    • Exploration Guide
    • Account setup
      • Using Hyperswitch Control Center
      • Test a payment
      • Using postman
    • Troubleshooting
  • Testing Payments
  • Check list for Production
    • Going live
      • For SaaS Setup
      • For On-Prem Setup
        • Monitoring
        • PCI compliance
          • Get started
          • Completing the SAQ
        • Data Security
        • Updates
  • Learn more
    • API Reference
    • Connectors Supported
    • SDK Reference
      • React
      • JS
      • Custom Events
    • Hyperswitch architecture
      • Router
      • Storage
      • A Payments Switch with virtually zero overhead
    • Payment flows
    • Blog
  • Community Guidelines
Powered by GitBook

Compliance

  • Vulnerability Disclosure
  • PCI DSS 4.0
  • ISO 27001:2022

Community

  • Slack
  • Discord
  • GitHub Discussion
On this page
  • Payment Analytics
  • Understanding the payment conversion funnel
  • Terminology
  • FAQs
  • Payment Operations
  • Customer Experience Team
  • Finance Team
  • Business Operations and Growth
  • How could Hyperswitch simplify Payment Operations?

Was this helpful?

  1. Explore Hyperswitch
  2. Payment Operations

Analytics & operations

Single dashboard for all your payment operations needs!

Last updated 3 months ago

Was this helpful?

Payment Analytics

Typical payment conversion funnel of a user through Hyperswitch involves five stages as shown below.

Understanding the payment conversion funnel

Lets take a scenario where you website had initiated 100,000 payments with Hyperswitch.

Payments created

100,000

User dropout at before checkout page is displayed

(10,000)

User dropout at checkout page

(10,000)

User inputs payment information and clicks pay button (payment confirmed by user)

80,000

Payment confirmation rate

80% = (80,000 / 100,000)

User fails 3DS verification

(2,000)

User dropout at 3DS verification page

(3,000)

Payment declined due to fraud

(1,000)

Payment authorized, but pending to be captured by merchant

(4,000)

Successful payments

70,000

Payment success rate

Total successful payments processed out of all user confirmed payments

*includes user dropouts at 3DS verification page, bank transfer login page, pages powered by digital wallets (Paypal, Googlepay, Applepay etc.,)

87.5% = (70,000 / 80,000)

Overall conversion rate

Total successful payments processed out of total payments created.

*includes user dropouts at shopping cart and checkout page.

70% = (70,000 / 100,000)

Terminology

Overall conversion rate

Total successful payments processed out of total payments created.

This includes user dropouts at shopping cart and checkout page.

Payment success rate

Total successful payments processed out of all user confirmed payments.

This includes user dropouts at 3DS verification page, bank transfer login page, pages powered by digital wallets (Paypal, Googlepay, Applepay etc.,).

Payment success rate does not include payments which are authorized by but not captured, because non-captured payments will be be settled to your merchant account by your payment processor.

Processed amount

Sum of amount of all payments with status = succeeded.

Please note that there could be payments which could be authorized but not captured. Such payments are not included in the processed amount, because non-captured payments will be be settled to your merchant account by your payment processor.

Average ticket size

The total amount for which payments were created divided by the total number of payments created.

Successful payments

Total number of payments with status as succeeded.

FAQs

Why is the conversion rate on my Payment processor dashboard higher that what I observe on Hyperswitch dashboard?

There are two aspects which you need to be aware of:

  • Once you start using the Hyperswitch, the role of the payment processor is involved only in the last leg of the payment processing (i.e) after the user enters payment information

  • Most payment processors report only the authorization rate excluding user dropouts on the checkout page and failed 3DS verifications.

Hyperswitch measures conversion rate including user dropouts, so that you get full visibility on your user dropouts and take appropriate measures to reduce user dropouts.

Please refer here for detailed understanding how popular payment processors track payment lifecycle and measure conversion rates.

What should I do to improve my conversion rate?

The analytics section on the Hyperswitch dashboard offers you the tools to derive insights on patterns of payment failures. Here are some frequently faced problems and actionables.

Most frequent problems faced by merchants

Actionables

Majority of my users are dropping off at the checkout page

  • Offer a wide range of payment methods preferred by your target audience

  • Eliminate any inconsistency in the total amount displayed to user across the product catalog page, shopping cart, checkout page

  • Ensure that the proceed to pay button is clearly visible to the user within minimal clutter on the UX.

I am facing lower conversion rates through my primary payment processor

  • Enable an alternative payment processor via Hyperswitch and use Smart Routing to optimize conversion rate

  • Reachout to Hyperswitch support to enable Smart Retries

I am facing low conversion rates for USD payments compared to EUR payments

  • Try enabling an alternative payment processor via Hyperswitch and use Smart Routing to route EUR payments (typically local payment processor offer higher conversion rates which you could benefit from)

I am facing zero conversion rate for a particular payment method/ currency

  • Check with your payment processor whether the payment method/ currency has been enabled for your merchant account

I need help and suggestions to improve conversion rate

  • Please drop a note to biz@hyperswitch.io with your query.

Payment Operations

"Payment Operations" refers to the operational time and effort spent by businesses beyond the payment processing step to manage the entire lifecycle of payments. It is cross-functional responsibility and shared across various teams of your business which is responsible for Customer Experience, Finance and Business Growth.

And, as you begin to process payments through multiple payment processors, the complexity increases multifold, thereby increasing fixed costs and siphoning out mind share from focussing on the core business.

Below are some of the day-to-day use cases of payments operations across teams which could potentially extract significant bandwidth from focusing on your core business growth.

Customer Experience Team

  • Issuing refunds to customers

  • Proactive monitoring of failed refunds and delayed refunds

  • Customer queries on double debits

  • Customer queries on incomplete/ delayed payments

Finance Team

  • Reconciliation of Payment Processed versus Amount Settled to Bank

  • Timely submission of evidence for chargeback claims from customers

  • Reducing the cost of fraud through monitoring

  • Optimizing payment processing cost with Smart Routing

  • Reporting across multiple business units / product lines

  • Triggering bulk refunds

Business Operations and Growth

  • Tracking, analyzing, and enhancing payment authorization rate

  • Expanding to new markets and accepting new payment methods

  • Product Returns versus Refunds issued to customers

  • Reporting across multiple business units/ product lines

Inadequate attention to payment operations might negatively impact your Net Promoter Score and impact the growth of your business.

How could Hyperswitch simplify Payment Operations?

Hyperswitch Control Center is a single interface that all your teams will be required to use for all Payment Operations use cases. This provides more power to your team for managing payments seamlessly.

In addition to the above, it also includes rich features to make operations more automated for your teams, such as

  • Real-time analytics

  • Checkout analytics

  • Automated Reports

  • Alerts automation

  • Managing user roles and access

Stripe - Conversion analysis
Adyen - Reporting and payment lifecycle
Paypal - Reports