Accepting International Payments From India: Stripe, Razorpay, Wise — Complete 2026 Guide

Deep-Dive International Payment & Compliance FAQs

1. Dynamic Currency Conversion (DCC) vs. Multi-Currency Pricing (MCP): How to configure Stripe and Razorpay to prevent excessive cross-border markup and conversion failures?

Dynamic Currency Conversion (DCC) and Multi-Currency Pricing (MCP) are often conflated by online merchants, but they represent fundamentally different technical approaches with massive implications for your user experience, conversion rates, and gross margins. When an international customer visits your Indian e-commerce store, booking engine, or SaaS checkout page, how you present prices determines who controls the foreign exchange (FX) markup. Under DCC, your website presents prices in Indian Rupees (INR), but the payment gateway or the card network (such as Visa or Mastercard) dynamically converts that price to the customer's home currency (e.g., USD, EUR, or GBP) at the point of sale. While this allows the customer to see what they will pay in their local currency, the conversion is executed using a retail exchange rate set by the card-issuing bank or the acquiring bank. This rate typically carries a hidden markup ranging from 3% to 8% above the actual interbank mid-market rate. For the customer, this results in an unexpectedly expensive transaction, which frequently triggers card-issuer fraud alerts or causes the customer to abandon their cart due to price shock at the final step.

In contrast, Multi-Currency Pricing (MCP) allows you, the merchant, to define and display native prices directly in foreign currencies. When a customer in New York views your product, they see exactly $100.00, and their card is charged exactly $100.00. The currency conversion happens on the backend during settlement, where your payment gateway converts the USD to INR before depositing it into your Indian bank account. In Stripe, MCP is natively supported via their multi-currency presentment feature. You can create multiple Price objects in Stripe's API for a single product, specifying exact amounts in USD, EUR, and GBP. Stripe's backend automatically routes these transactions using local acquiring networks, minimizing card declines and limiting foreign exchange fees to a transparent, flat conversion rate (typically around 2% for Indian merchants, plus standard GST). Razorpay also supports international payments in over 100 currencies, but you must manually request multi-currency settlement enablement within your account settings, and you must design your frontend to pass the correct currency code to the Razorpay Checkout utility. Implementing MCP instead of relying on default DCC is the single most effective way to eliminate friction for global buyers and secure higher checkout conversion rates.

To implement a robust MCP setup, follow these technical best practices: First, employ server-side IP geolocation (or client-side detection) to dynamically identify the user's location and load the corresponding currency price from your database rather than relying on automatic browser translation tools. Second, when constructing the checkout session payload in Stripe or Razorpay, ensure that the currency code is set to the customer's native currency (e.g., USD or GBP) and that the amount is formatted according to the zero-decimal or multi-decimal requirements of that specific currency. Third, continuously review your settlement statements. Look for foreign transaction markup reports and analyze transaction drop-offs by currency. This will help you adjust your localized base pricing to absorb gateway conversion fees while remaining highly competitive in target international markets.

2. Navigating RBI's Purpose Codes & e-FIRC requirements: How do Indian service exporters auto-generate and reconcile foreign transaction receipts with Stripe and Wise?

For any Indian business or freelancer exporting services, digital products, or physical goods, compliance with the Reserve Bank of India (RBI) is a mandatory requirement that cannot be overlooked. Under the Foreign Exchange Management Act (FEMA), every single dollar, euro, or pound entering India from overseas must be declared to an Authorized Dealer (AD) bank and mapped to a specific RBI Purpose Code. These codes are alphanumeric identifiers that classify the exact nature of the transaction. For instance, a software developer or SaaS startup must use purpose code P0802 (Software implementation services) or P0803 (Information services including data processing and database services). A digital creator selling templates or e-books should use P1007 (Digital downloads), while a premium boutique hotel or inbound tour operator in Ladakh must use P1102 (Travel for leisure or tourism). If your incoming funds are not assigned the correct purpose code, your domestic bank cannot complete the settlement process, resulting in suspended payouts, manual compliance queries, or potential legal penalties for violating foreign exchange regulations.

In addition to purpose codes, you must obtain a Foreign Inward Remittance Certificate (FIRC) or an electronic FIRC (e-FIRC). An e-FIRC is the primary official document that proves foreign currency was received in India and converted into INR. This document is indispensable for tax compliance, particularly if you want to claim GST exemption under the "Export of Services" provision. Under Indian GST law, export of services is treated as a "zero-rated supply," allowing you to avoid charging 18% GST to global clients, provided you file a Letter of Undertaking (LUT) beforehand and can produce an e-FIRC as proof of foreign currency receipt within nine months. Traditional banks charge heavy fees and require weeks of manual paperwork to issue an FIRC, but modern platforms like Wise and Stripe have automated this process to save time and reduce administrative costs.

When you accept international bank transfers via Wise Business, Wise acts as an Authorized Dealer Category II entity (or partners with AD Category I banks like Yes Bank or HDFC). For every foreign transfer received, Wise automatically requests the purpose code from you and matches it to the transaction. Within your Wise dashboard, you can download a fully compliant, digitally signed e-FIRC for each payment. For e-commerce and subscription sales processed via Stripe India, Stripe operates under the Online Payment Gateway Service Provider (OPGSP) guidelines. Stripe aggregates your international transactions and transfers them to your Indian bank account in daily batches. Along with these payouts, Stripe generates a consolidated "Payment Advice" or digital FIRC download. To make sure this runs without any issues, you must log into your Stripe and Wise settings and upload your Importer-Exporter Code (IEC) and your Goods and Services Tax Identification Number (GSTIN). Once these details are saved, the platforms will auto-populate your digital certificates, ensuring your accountant has a clear audit trail to reconcile export invoices, keep your books clean, and satisfy GST inspectors during annual audits.

3. Liberalised Remittance Scheme (LRS) and TCS Compliance: What are the distinct tax reporting and reporting mandates for outward remittances via Wise or Flywire versus inward business collections?

There is a widespread misconception among Indian business owners that the Liberalised Remittance Scheme (LRS) and the associated Tax Collected at Source (TCS) rules apply to all cross-border transactions. This misunderstanding often leads to unnecessary worry about tax withholding on business revenue. To clarify: the LRS is a regulatory framework created by the RBI that allows individual resident Indians to outward remit up to USD 250,000 per financial year for specific, non-commercial purposes. These purposes include overseas travel, higher education, medical expenses, purchasing foreign real estate, or investing in international stock markets. Under recent finance bills, any outward remittance under LRS that exceeds INR 7 Lakhs in a financial year is subject to TCS. Depending on the category, TCS rates can be as high as 20%. Because TCS is a tax collection framework, it is designed for individuals sending personal funds *out* of India. It does *not* apply to inward payments (money coming *into* India) for business sales, nor does it apply to legitimate corporate entities executing outward transactions for standard commercial purposes.

If your business uses Stripe or Razorpay to accept payments from international customers, you are receiving an inward remittance, which is completely outside the scope of LRS and TCS. Your primary tax obligation for these inward payments is to ensure compliance with the GST laws. By uploading a valid Letter of Undertaking (LUT) on the GST portal at the start of each fiscal year, you can treat your international sales as zero-rated exports, meaning you do not have to pay or charge GST on these invoices. However, you must maintain clean records linking each inward remittance to an active export invoice, backed by the corresponding e-FIRC. Failure to do so could result in the tax department retroactively demanding 18% GST on your foreign earnings, along with interest and penalties.

Conversely, if your Indian business needs to make outward payments to foreign vendors—such as paying for Amazon Web Services (AWS), purchasing software licenses, or paying international freelance developers via Wise or Flywire—this is classified as a commercial import of services rather than an LRS transaction. In this scenario, TCS does not apply because you are a corporate entity executing a business expense. However, you must comply with Indian Income Tax laws regarding withholding tax (Tax Deducted at Source or TDS). Before initiating an outward wire transfer, you are required to file Form 15CA online, and if the transaction exceeds certain thresholds, you must obtain a signed Form 15CB from a Chartered Accountant certifying that the appropriate TDS has been calculated and paid. Additionally, you will be liable to pay GST under the Reverse Charge Mechanism (RCM) on the imported services, which you can later claim back as Input Tax Credit (ITC). Keeping these rules in mind ensures that your business stays compliant on both incoming and outgoing international transactions.

4. Setting up Fallback High-Value Wire-Transfer Pathways: How do you configure Wise Business and Flywire to accept large B2B invoices above gateway limits?

While payment processors like Stripe and Razorpay are perfect for processing credit card payments for e-commerce checkouts, small digital downloads, and monthly SaaS subscriptions, they are highly inefficient for high-value B2B transactions. If your digital agency, consulting firm, or tourism business in India issues an invoice for $15,000, routing that payment through a standard gateway card transaction is a major financial mistake. Standard gateways charge an international processing fee of 3% to 4%, which means you lose $450 to $600 of your profit margins on a single payment. Additionally, international credit cards are subject to strict daily spending limits and advanced fraud prevention algorithms. When a client tries to pay a high-value invoice online, the card-issuing bank will often decline the transaction, leading to frustrating payment failures and checkout delays. To avoid these issues, Indian businesses should set up fallback wire-transfer pathways using platforms like Wise Business and Flywire.

Wise Business solves this problem by providing virtual local bank accounts (also known as local receiving details) in major global currencies, including USD, EUR, GBP, AUD, CAD, and SGD. When billing a foreign client, you can include these local account details directly on your invoice. A client based in the United States can pay you via a standard domestic ACH transfer or a local wire, while a European client can send a local SEPA bank transfer. These local payments are usually free or cost just a few cents for the sender. Once the foreign currency arrives in your Wise account, Wise converts it to INR using the real mid-market exchange rate and a highly transparent, low fee (often under 0.5%). The funds are then deposited directly into your Indian business bank account, typically within a few hours. This approach saves you hundreds of dollars in gateway fees and ensures your clients do not have to worry about card declines or wire transfer fees.

For specialized industries like travel booking, educational institutions, or healthcare services, Flywire is another excellent solution. Flywire is designed to handle high-value, cross-border payments with ease, allowing customers to pay in their local currency using familiar, local payment options while ensuring the funds are securely delivered to your bank in India. By implementing a hybrid billing setup, you can use Stripe or Razorpay to collect small, immediate security deposits (e.g., $500 to secure a booking or start a project) and provide Wise or Flywire details for all subsequent progress payments and high-value invoices. This strategic workflow optimizes checkout conversion rates, keeps your clients happy, and protects your business from high transaction fees.

5. Handling the Stripe India "Invitation-Only" and Merchant Onboarding Bottleneck: What are the exact compliance documents and workarounds for new Indian entities?

In recent years, the regulatory environment for digital payments in India has changed dramatically. The Reserve Bank of India (RBI) introduced strict guidelines for payment aggregators and payment gateways (PA/PG guidelines) to enhance security and prevent financial fraud. These changes led to a prolonged pause in new merchant onboarding for international payment aggregators, including Stripe India. As a result, Stripe transitioned its Indian operations to an "invitation-only" onboarding system. This has created a significant hurdle for new startups, agency owners, and e-commerce merchants in India who want to accept international credit cards. Understanding the compliance standards and the workarounds for this bottleneck is essential for any business wanting to launch services globally.

To successfully request an invitation and pass the verification checks, your business must have impeccable corporate and regulatory documentation ready for review. Stripe's compliance team and its Indian banking partners will require: First, a registered business structure (such as a Private Limited Company or a Limited Liability Partnership), as sole proprietorships face much higher scrutiny and frequent rejection. Second, an active Importer-Exporter Code (IEC) issued by the Directorate General of Foreign Trade (DGFT), which is legally required to export services or goods from India. Third, a valid Goods and Services Tax Identification Number (GSTIN) matching your registered company name. Fourth, a dedicated business bank account matching the exact entity name on your registration. Finally, you must have a fully functional website containing comprehensive Terms of Service, a transparent Refund and Cancellation Policy, an explicit Privacy Policy, and clear customer support contact details (which must route to a professional email address like bkbtechies@gmail.com). If any of these pages are missing or contain placeholders, your onboarding request will be immediately declined.

If your Stripe India invitation is delayed and you need to accept global payments immediately, there are a few practical workarounds. The first option is to enable international payments on Razorpay. As a domestic market leader with an Authorized Payment Aggregator license, Razorpay often onboard Indian merchants more quickly, provided you submit the necessary business registration, GSTIN, and IEC details. A second option is to register an offshore company (such as a US LLC or a UK LTD) using services like Stripe Atlas, Firstbase, or similar platforms. By establishing a US entity, you can open a US bank account (via Mercury or Wise) and register for a standard US-based Stripe account. While this approach bypasses the Indian onboarding bottleneck, you must consult a qualified tax advisor to ensure your company structure remains compliant with Indian tax laws and FEMA rules regarding foreign corporate holdings.