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
  • Import file format:
  • To import card data:
  • Required fields:
  • Optional fields:

Was this helpful?

  1. Explore Hyperswitch
  2. Payment Operations
  3. Data migration

Import data to Hyperswitch

We help you with smooth migration from your current payment processor, ensuring uninterrupted business operations.

Performing the import data process:

  1. Merchant initiates a request to our team for Data import.

  2. We will share our PCI Attestation of Compliance (AoC) certificate to Merchant.

  3. Merchant requests a data export (for both customer records and associated payment data) from their current payment processor, by providing Hyperswitch’s PCI AoC certificate.

  4. We will provide our public PGP key for Merchant’s current payment processor to encrypt their export data.

  5. An encrypted CSV file containing all the export data needs to be sent through SFTP by Merchant’s current payment processor.

  6. We will import the data.

  7. Post migration of data, we will send an updated customer-payment method reference IDs to Merchant.

Import file format:

The CSV file for import should be formatted in accordance with the following requirements:

  • The first line contains the names of the fields.

  • Each subsequent line should contain the fields for a single record.

  • Delimit rows by a single newline character \n (not \r\n).

  • Delimit columns by ,

  • Leave empty fields entirely empty (no character in between delimiters). You must not denote a missing field with NULL, N/A, or any other value.

  • Fields can’t contain comma, newline characters (\r or \n or ,) within a field.

    • Example of what to avoid: 1st Ave\nApt 1

  • All rows must have the same number of columns.

  • Field names and values are case-sensitive.

  • Multi-line fields are not allowed.

  • Save the file in UTF-8 format (to support non-western characters).

  • Encrypt the file using the public PGP key provided by Hyperswitch.

To import card data:

Required fields:

Field

Description

card_number

Primary Account Number (PAN) of the customer card

card_expiry_month

Card expiry month

card_expiry_year

Card expiry year

payment_instrument_id

Unique reference ID of payment method saved (PSP token)

Note: This is required for mapping to Hyperswitch payment_method_id.

original_network_transaction_id

Original Transaction ID of the first transaction where the customer signed up for recurring payments. For eg. Visa - Visa Transaction ID, Mastercard - Mastercard Trace ID. Note: This is only required for connector agnostic MIT

Optional fields:

Note: Billing details are mandatorily required if AVS (Address verification Service) check is enabled.

Field

Description

name

Name of the customer

email

Email id of the customer

payment_method

Payment method used by customer (Eg: card - for cards import)

payment_method_type

Payment method type used by the customer (eg: credit / debit)

card_scheme

Card network (Eg: Visa, Mastercard, American Express)

phone

Customer mobile number

phone_country_code

Country code of Customer mobile number

billing_address_first_name

Customer First Name for billing address

billing_address_last_name

Customer Last Name for billing address

billing_email

Billing email id of the customer

billing_address_line1

Street Name/Address Line 1 of the billing address

billing_address_line2

Locality Name/Address Line 2 of the billing address

billing_address_city

City of the billing address

billing_address_state

State of the billing address

billing_address_zip

Postal code of the billing address

billing_address_country

Country of the billing address

Last updated 5 months ago

Was this helpful?

To import other payment methods like SEPA, ACH, Paypal, Klarna, kindly reach out to

hyperswitch@juspay.in