LogoLogo
Explore with DeepWikiJoin Slack CommunityContact Us
  • About Hyperswitch
    • Exploration Guide
    • Overview
    • Payments Suite
    • Payments Modules
      • Cost Observability
      • Revenue Recovery
      • Vault
        • Server to Server Vault tokenization
        • Vault SDK Integration
        • Hyperswitch Vault: Pass Through Proxy Payments
      • 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
    • 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
  • Overview
  • Open Banking Use-Cases
  • Steps to configure Account Verification for bank debits
  • Steps to configure Payment Initiation (via Plaid)
  • Payment flow for AIS based Bank debits:
  • Payment flow for PIS based Open banking payments:
  • FAQ

Was this helpful?

  1. Explore Hyperswitch
  2. Payment Orchestration
  3. Accept Payments
  4. Setup Payment Methods
  5. Banks

Open Banking

Account Verification and Payment Initiation Services using open banking providers

Overview

Open banking enables the sharing of financial data between banks and third-party providers via APIs. It serves as a framework for services like bank-to-bank transfers and account verification, allowing customers to transfer funds to merchants directly from their bank accounts.

Open Banking Use-Cases

Account Information Service

Account Information Services (AIS) in open banking allow authorized third-party providers to access and retrieve financial data from a user's bank account, with the customer's consent. This information can include transaction history, account balances, and spending patterns.

Regional Usage:

  • U.S.: AIS is mostly employed for one-time account verification, especially in direct debit payments.

  • UK/EU: AIS services are more widely adopted for a variety of use cases, like financial management, due to the robust open banking frameworks under PSD2.

Payment Initiation Service

Payment Initiation Services (PIS) in open banking allow authorized third-party providers to initiate payments directly from a customer's bank account, with their consent, without the need for traditional intermediaries like credit or debit card networks. PIS provides an alternative to conventional payment methods, making bank-to-bank transfers more seamless and efficient.

Regional Usage:

  • UK/EU: PIS is mostly dominant across Europe. Adoption in other regions, such as the U.S., is slower due to less-developed open banking frameworks.

Steps to configure Account Verification for bank debits

  1. On the Hyperswitch dashboard, head to Connectors Tab

  2. Head on to the PM Authentication Tab and select your Open Banking AIS connector

  3. Add your credentials and you should be good to go.

  4. Head on to Payment Processor and configure a Payment Processor, on select payment methods like Bank debits, you'll be asked to select a PM authentication connector to link with the payment Processor

  5. Select a existing PM auth connector (that you have already configured) and proceed with the rest of the steps.

Steps to configure Payment Initiation (via Plaid)

  1. On the Hyperswitch dashboard, head to Connectors Tab

  2. Head on to the Payment Processor Tab and select Plaid.

  3. Enter your client_id and secret and select relevant payment methods.

  4. Merchant's Bank account data needs to be provided in order to initiate transfer of funds to the merchant account. Under the dropdown Open Banking Recipient Data, One of the underlying options should be selected - - bank scheme, in which merchant's recipient account details needs to be provided (either sepa or bacs) - Connector Recipient Id, in case the merchant already has a recipient id created with the connector

  5. For Payment Initiation services, the payment method selected should be Open banking with payment method type as Open Banking PIS

  6. Configure the rest and you should be good to go.

Payment flow for AIS based Bank debits:

  1. Customers select a Bank debit method on your checkout page

  2. They are prompted to save the payment method with hyperswitch and your configured PM auth (open banking AIS) processor.

  3. Customer is then asked to select their bank account in Processor SDK for saving it with the PM auth processor.

  4. Hyperswitch connects with the PM auth processor to get the necessary information about their bank accounts and saves it.

  5. The customer can now select their saved bank account at hyperswitch to make payment.

Payment flow for PIS based Open banking payments:

  1. Customers select a Open banking PIS method on hyperswitch checkout.

  2. Customer is then asked to select their bank account in Processor SDK for authorizing the payment.

  3. Once the customer authorizes the payment via Processor SDK, hyperswitch does a sync call with the Processor to update the status of the payment and displays the same to the customer.

FAQ

  1. Are there any other Open banking processors apart from Plaid? - Yes, Processors like TrueLayer and Tink provide the same services as Plaid. However, Hyperswitch currently only supports an integration with Plaid. If there are other providers that you want to use please raise a Github Issue.

  2. Any extra configuration required for Android or IOS platform? - If using Plaid, the android package name (for android) and redirect uri (Universal Link for your application) (for IOS) needs to be passed from the merchant SDK while invoking the Hyperswitch SDK.

  3. In which all geographies can I use open banking?

    1. Account Verification is currently available to verify bank accounts for direct debits via ACH, SEPA and BACS

    2. Payment Initiation is currently available for the UK and EU markets

Last updated 8 months ago

Was this helpful?