How to Accept International SaaS Payments Without a Merchant of Record

How to Accept International SaaS Payments Without a Merchant of Record

To accept international SaaS payments without a third-party Merchant of Record, your Indian business needs a supported payment-collection flow, a subscription lifecycle and a process for its own seller obligations. Razorpay Subscriptions supports recurring card payments in supported international currencies for eligible accounts, with subscription settlements made in INR under the India Subscriptions FAQs. Your business remains responsible for the customer contract and applicable tax and reporting work.

That distinction is where most founders get stuck. Overseas customers are ready to subscribe, the pricing page is in USD, and the open question is whether accepting their cards also solves billing automation, export documentation and destination-country tax. It does not. Payment acceptance, subscription automation and legal responsibility as the seller are three separate jobs, and only the first two sit with a payment provider. This guide separates those responsibilities, then walks through the setup, testing and reconciliation work an Indian SaaS team has to do before going live.

Key Takeaways

  • Direct selling lets your SaaS business collect through a payment gateway while keeping full responsibility as the seller of record.
  • Razorpay Subscriptions supports international-currency card subscriptions for eligible, activated accounts.
  • Monthly and yearly plan frequencies are documented configuration options in the Create Plan API.
  • The customer’s billing currency and your settlement currency are separate questions; the documented subscription flow settles in INR.
  • Confirm activation, supported recurring methods, intended currencies and commercial terms before you design a checkout.
  • Build tax, invoicing, export-record, failed-payment and customer-service processes alongside the integration, not after launch.

Can an Indian SaaS Company Sell Globally Without a Third-Party Merchant of Record?

Yes. An eligible Indian SaaS business can collect overseas card subscriptions directly through Razorpay while retaining its customer relationship and its seller obligations. Razorpay is a practical option when its supported payment methods, currencies, and billing workflow fit the business, and when the team can operate its own tax, finance, and customer processes.

A third-party Merchant of Record works differently: that provider contractually becomes the seller for covered transactions and takes on the associated responsibilities. Selling directly means no external party assumes that role. You are not selling without a legally accountable seller; you are the legally accountable seller.

Choose the Architecture From Your Billing Requirements

Razorpay documents both international-card subscriptions and INR subscription methods, which makes it a practical option to evaluate for overseas subscriptions as well as for a mixed India-and-global customer base. Decide whether you need another payment route from a tested requirement, not from an assumed percentage of international traffic.

The requirements worth testing are concrete: do your intended currencies work on your account, do the recurring card methods your customers use get authorised, do monthly and annual intervals map cleanly to your entitlements, and can Finance reconcile an INR settlement back to a USD invoice. For the broader category comparison, see the guide on choosing between a gateway and a third-party MoR.

What Does Razorpay Handle, and What Remains Your Responsibility?

Razorpay provides the supported collection and subscription tools, payment events and relevant payment records. Your SaaS business operates the customer contract, service access, tax decisions, filings and customer policies. A gateway’s payment processing and its export-payment statements do not transfer the responsibilities of the seller.

Task Razorpay’s documented role What your SaaS business must do
International card collection Process the supported card flow after activation Confirm account eligibility, recurring methods and intended currencies
Monthly and annual billing Plans, Subscriptions and customer authorisation Set prices, billing periods, renewal terms and the access period purchased
Subscription changes Supported update and proration behaviour Design upgrades and downgrades within card-method and subscription-state restrictions
Failed renewals Documented retry flow and subscription webhook events Set grace periods, customer messages and entitlement rules; handle unresolved failures
Foreign-currency subscription receipts Supported card presentment; subscription settlement in INR Reconcile the charge, conversion, deductions and bank receipt
Export payment evidence Dashboard FIRS process with purpose-code checks Retain documents and match them to invoices, receipts and settlement records
Tax and statutory reporting Payment records that can support your finance workflow Determine applicable tax treatment, registrations and filings with advisers
Refunds, disputes and customer service Payment tools and transaction records within the product’s scope Set customer policies, respond to the customer and supply required evidence

What Payment Evidence Can Support Your Finance Workflow?

Razorpay’s documented FIRS process gives your finance team downloadable evidence of foreign receipts. Complete the relevant purpose-code process in the Dashboard and match the statement to your billing and settlement records. The FIRS automated process documentation describes FIRS as evidence of funds received from a foreign country, recognised in scenarios such as GST refunds and beneficiary-bank compliance requirements. Razorpay also describes automated digital FIRS as a direct download from the merchant dashboard.

Your team still determines the export treatment and completes the required reporting.

Keep the instruments distinct:

  • FIRS is a statement generated through your payment flow.

  • Bank-issued certificates come directly from your Authorised Dealer (AD) bank.

  • eBRC is self-certified by the exporter on the DGFT portal using bank-transmitted inward remittance messages (a streamlined process introduced under Trade Notice 33/2023-24 dated 10 November 2023).

Three documents, three issuers, three triggers.

DID YOU KNOW: The FIRS Dashboard distinguishes bank-provided certificates from Razorpay-generated statements. Preserve that distinction so Finance never substitutes one for the other during an audit.

How Do International Subscription Currencies and INR Settlement Work?

Razorpay’s India Subscriptions FAQs state that card subscriptions support international currencies and that subscription settlements are always made in INR, while UPI recurring payments are INR-only and generally limited to Rs 15,000, though the limit has been enhanced to Rs 1,00,000 for specific categories like mutual funds, insurance premiums and credit card bill payments. Confirm the exact recurring-card and currency configuration enabled on your account before showing a price to overseas customers.

Separate the Customer’s Billing Currency From Your Settlement Currency

The flow runs in one direction: the customer agrees to a subscription priced in a supported currency, the authorised card is charged each cycle, a payment record is created, and the receipt settles into your Indian account in INR. “USD pricing” does not mean the subscription flow settles in USD.

Razorpay has launched a separate Multi-Currency EEFC Account for exporters supporting USD, EUR, GBP, AED and SGD, and an explainer covering EEFC settlement for international card payments. That is a distinct product with its own settlement checks. Confirm whether it applies to your subscription flow before assuming it does.

Assess Domestic and International Cards Separately

Razorpay’s Subscriptions FAQs state that the RBI card-mandate guidelines discussed there apply to domestic cards, not international cards. Domestic mandate limits should therefore not be used on their own to rule out international-currency card subscriptions.

That said, RBI issued the Digital Payments E-mandate Framework, 2026 on 21 April 2026, and a summary notes it applies to participants processing recurring domestic and cross-border transactions through cards, PPIs and UPI. Review applicability with your compliance adviser. For more on the flow itself, see the guide to international subscriptions for Indian businesses.

How Do You Set Up Monthly and Annual International SaaS Billing With Razorpay?

Create a monthly or yearly Plan, create the customer’s Subscription against it, collect the required authorisation, and connect verified payment events to your application’s access rules. Razorpay supplies the recurring-payment workflow. Your application controls what the customer can use and what happens when billing changes or a renewal fails.

Create Separate Monthly and Yearly Plans

Illustrative SaaS plan Price Billing frequency Implementation point
Starter Monthly USD 49 Monthly, interval 1 Create a monthly Plan in an account-supported currency
Starter Annual USD 490 Yearly, interval 1 Create a separate yearly Plan and define the annual service period
Trial before Monthly Same selected paid Plan Future subscription start date Collect the required authorisation upfront and disclose when paid billing begins

These prices are illustrative software prices for your own product. They are not Razorpay charges or an available offer.

A Plan describes the amount, currency and frequency. A Subscription applies that arrangement to a specific customer. The Create a Plan API documents period values of daily, weekly, monthly, quarterly and yearly, combined with an interval value, so a standard monthly plan is period: monthly with interval: 1. Plans are immutable under the documented FAQ, so create a new Plan rather than editing an existing one. The Create a Subscription API requires you to bound the arrangement with either total_count or end_at, and not both.

Handle Trials, Upgrades and Proration Within the Supported Flow

Trials are implemented as a future start date rather than a separate trial object: you pass a future start_at value and billing begins automatically on that date. Disclose the exact trial end date, the converting amount and how to cancel before conversion.

For changes mid-lifecycle, the India FAQ is explicit that you can only update a Subscription authorised using cards, not one authorised via UPI or eMandate. The update a Subscription API documents plan_id, quantity, remaining_count, start_at, schedule_change_at and customer_notify, with schedule_change_at set to “now” applying the change immediately. Two restrictions bite in practice: an update fails if the subscription is still in the created state, and a plan change that downgrades the amount on an offer-linked subscription is only allowed at the end of the current billing cycle. Complex usage metering and service entitlements remain part of your application’s design.

Verify Authorisation and Plan for Failed Renewals

Initial authorisation, server-side verification and subsequent renewals are three distinct stages. The first transaction goes through 2FA via OTP or 3D Secure; later charges are made automatically without 2FA. Verify checkout response signatures on your server and use subscription events to update access. Never grant paid access because a browser returned a success screen.

Razorpay’s payment retries documentation describes a T+3 cycle with three retries, once a day for three days excluding the charge date, after which the subscription moves to halted. Your application still needs a grace-period policy, a customer recovery journey and clear access rules. Test initial authorisation and renewal separately for your intended markets; no gateway can guarantee every issuer decision.

PRO-TIP: Keep your internal customer ID, Plan ID, Subscription ID and payment IDs connected in your own database. That mapping makes a failed renewal investigation far easier six months later.

What Should You Confirm Before Building the Integration?

Start with an active, KYC-verified Razorpay account and a working website. Request international-card activation and confirm the intended recurring-card flow, supported currencies, and commercial terms. This turns a general “check eligibility” caution into a concrete launch task with a named owner.

Assign Owners to the Activation and Website Checklist

Work through these items before any engineering begins:

  • Legal business details and settlement bank account
  • A live product and a public pricing page
  • Terms of service, privacy policy, refund and cancellation policies
  • Intended countries and billing currencies
  • Recurring-card approval confirmed for your account and business category
  • Customer communication templates and a published support contact

The exact documents depend on Razorpay’s onboarding request and your business category. The documented Import/Export code reference is tied to sales of tangible products, so do not assume an IEC is mandatory for every SaaS exporter. Follow the current international card activation instructions, and note that approval timing is account-specific. You can also review the International Payments product page for scope.

Confirm the Full Cost, Not Just the Card Rate

Ask for international-card processing charges, FX and conversion terms, any subscription-product charges, taxes on provider fees, refund and dispute charges, settlement terms and any reserves. Then add the costs you retain: finance operations, tax advisory, reconciliation labour and engineering maintenance.

Review your account’s current quote against Razorpay pricing rather than assuming a domestic promotional rate applies to international subscriptions. Razorpay’s international payment costs breakdown sets out the method: processing fee, FX conversion, any minimum or flat charge, plus GST on fees.

PRO-TIP: Get the intended recurring-card and currency setup confirmed in writing before the team commits to a checkout design.

How to Implement Direct International SaaS Collections in Eight Steps

Implement direct international SaaS collections by confirming the merchant setup, configuring billing plans, collecting authorisation, verifying events, handling failures and reconciling receipts. Each step needs an owner and a testable result.

Step 1: Define Your Customer Markets and Billing Model

List your merchant location, target customer countries, whether the audience is B2B or B2C, billing currencies, plan structure, trial rules and expected payment methods. A hypothetical example: a Bengaluru analytics SaaS selling to US and EU B2B teams at USD 49 monthly or USD 490 annually, with a 14-day trial.

Owner: Founder and Product.
Expected output: A one-page payment requirements sheet signed off by Finance.

Step 2: Complete Onboarding and Confirm Recurring-Card Activation

Follow Razorpay’s current international activation instructions through the Dashboard under Account and Settings, then International payments. Confirm explicitly that the intended recurring flow, currencies and business category are enabled, not just that international payments are live.

Owner: Finance and Operations.
Expected output: Account approval plus an internally retained capability and commercial confirmation.

Step 3: Create the Monthly and Annual Plans

Create separate Plans with the intended amount, currency and frequency using the Create a Plan API. Define taxes, trial disclosures and the service period in your own billing system. Keep test-mode configuration strictly separate from production.

Owner: Engineering and Product.
Expected output: A reviewed Plan catalogue and a mapping from each Plan to the entitlement it purchases.

Step 4: Create the Subscription and Collect Customer Authorisation

Create the Subscription against the selected Plan, bounded by total_count or end_at. On the checkout screen, show the amount, interval, trial end date where relevant, renewal terms and the cancellation route.

Owner: Engineering.
Expected output: A test Subscription linked to the correct customer and Plan. Never collect or store raw card details in your own systems.

Step 5: Verify Payments and Connect Events to Service Access

Verify checkout response signatures on the server. Process authenticated subscription webhook events securely, and handle repeated or delayed deliveries idempotently.

Subscription state Recommended application action
Authenticated Do not grant paid access until the relevant payment is verified
Active Enable the service period tied to the verified payment
Charged Extend access once, using idempotent event processing
Pending Start your grace-period and customer recovery workflow
Halted Apply your access policy; do not assume old invoices keep retrying
Cancelled End future renewals and apply your access end-date policy

Owner: Engineering.
Expected output: An event-to-entitlement map and test logs for successful and unsuccessful billing states.

Step 6: Build Recovery, Cancellation and Plan-Change Journeys

The subscription states documentation notes that in the halted state, invoices continue to be generated per the billing cycle but no auto-charge is attempted. Once a subscription returns to active, previous charges are not re-attempted and only future cycles are charged. Design your recovery policy around that.

Owner: Product, Engineering and Support.
Expected output: Tested failure, recovery, cancellation, refund and supported-update paths.

Step 7: Reconcile Charges, Settlements and Export-Payment Records

Match each customer invoice and service period to its Subscription and payment IDs, deductions, INR settlement and bank receipt. Obtain the relevant FIRS records through the documented Dashboard process and confirm the applicable purpose code with your AD bank.

Owner: Finance.
Expected output: A sample reconciled ledger and an export-payment evidence folder. A FIRS statement does not itself file a tax return.

Step 8: Run an Approved Pilot and Review the Results

Use test mode for integration checks, including the “Charge this now” simulation to trigger events without waiting for a due date. Then run a separately approved live pilot. Inspect first authorisations and renewals by intended market and method.

Owner: Engineering, Product and Finance.
Expected output: A launch review documenting observed results and a decision to proceed or revise. See the Payment Gateway and Razorpay Subscriptions product pages for scope.

How Should You Manage Tax, Invoices and Export Records When Selling Directly?

Your SaaS business needs its own process for customer invoicing, applicable indirect taxes and export reporting. A payment gateway helps collect and document the money. The correct tax treatment depends on the transaction, the customer and the jurisdiction.

Check Indian Export-of-Service Treatment

An overseas customer or a foreign-issued card does not by itself establish export-of-service treatment. The conditions are cumulative and set out in Section 2(6) of the IGST Act, with zero-rating under Section 16. Work through the applicable route with Finance, including whether you export under LUT or bond without paying IGST, or pay IGST and claim a refund.

Separate Destination Taxes From Indian Export Treatment

Destination-country VAT or sales tax is an entirely separate review. For the EU, the non-Union One Stop Shop lets a non-EU supplier register in one member state and file a single return covering B2C sales. Start from the European Commission’s VAT guidance for businesses and the One Stop Shop portal, then confirm country rules with an adviser. In the US, taxability varies by state: California SB 122, signed on 29 June 2026, extends sales and use tax to SaaS from 1 January 2027.

Keep a Payment-to-Invoice Evidence Trail

Retain the contract or order, customer location evidence where required, the invoice, payment and Subscription references, deductions, the INR bank receipt, FIRS records and refund documentation.

What Changed for Software and Service Export Reporting in 2026?

The Foreign Exchange Management (Export and Import of Goods and Services) Regulations, 2026 introduced a consolidated Export Declaration Form covering goods, services and software, replacing the SOFTEX form, with the monthly EDF regime operative from 1 October 2026. RBI then amended it on 2 November 2026, so that an EDF is deemed submitted for resident individual service exporters and where the inward remittance does not exceed Rs 10 lakh. Confirm your position with Finance.

DID YOU KNOW: Billing in a foreign currency and qualifying for export treatment answer different questions. Keep payment configuration and tax eligibility as separate checks.

What Should You Test Before Expanding International SaaS Collections?

Test What to verify Evidence to retain
Initial authorisation Correct customer, Plan, amount, currency and consent Test payment and Subscription records
Monthly and annual billing Correct interval and purchased service period Plan catalogue and entitlement result
Trial conversion Agreed future start date and cancellation before charging Timeline and customer communications
Renewal success Verified charge updates the correct access period once Payment event and application log
Renewal failure Pending, retry and halted handling matches the documented flow Failure events and recovery journey
Supported plan change State and method permit the update; proration matches the operation Before and after billing records
Cancellation and refund Customer instruction and access or refund policy work together Cancellation and refund records
INR reconciliation Charge, conversion, fees, settlement and bank receipt reconcile Finance ledger and bank statement
Export evidence Relevant statement can be retrieved and matched FIRS record linked to the invoice

Measure Authorisation and Renewal Performance Separately

Track your own merchant-level metrics: attempted and successful initial authorisations, renewal attempts and successes, recovery after failure, cancellation complaints and reconciliation exceptions. Segment by intended country, currency and card method where your sample size permits.

Do not convert initial authorisation performance into a renewal success claim; they are different populations. Cross-border authorisation behaviour varies by issuer and market, which is why you measure your own baseline during the pilot rather than importing someone else’s number.

Test Failed Payments and Halted-State Entitlements

Run a deliberate failure in test mode and watch what your application does. The two behaviours teams get wrong are that invoices keep generating in the halted state without an auto-charge, and that recovery does not retroactively collect missed cycles.

Know When Direct Selling Needs More Operational Support

If your team cannot manage destination-tax registrations and filings, complex usage metering, multilingual billing support or a high volume of disputes, additional tooling, external advisers or a third-party MoR may fit your requirements better. That is a legitimate selection boundary, not a failure.

For enterprise customers who require invoice-led bank transfers, review the separate international bank-transfer product and verify its scope. A receiving account is not evidence of automatic monthly card debits.

PRO-TIP: Reconcile one complete customer lifecycle, including a failed payment and a cancellation, before scaling your subscriber count. Also confirm every documentation page you rely on is showing India content.

Frequently Asked Questions

Can an Indian SaaS Business Use Razorpay Without a Third-Party Merchant of Record?

Yes. An eligible business can use Razorpay’s supported international-card subscription flow while selling directly to overseas customers. The business keeps the customer contract, pricing, refund policy and applicable tax responsibilities. Choose Razorpay when its supported recurring methods, currencies and settlement flow match your requirements.

Can I Bill Overseas SaaS Customers Monthly or Annually?

Razorpay documents monthly and yearly Plan frequencies alongside daily, weekly and quarterly options. Create separate Plans, create each customer’s Subscription against the chosen Plan, and collect the required authorisation. This is automatic recurring billing, not sending a fresh one-time payment link every month.

Can I Charge in USD and Receive the Subscription Settlement in INR?

Yes. Under the documented flow, supported international-currency card subscriptions settle in INR. Confirm your intended currency and recurring-card activation for your specific merchant account before launching. A separate multi-currency EEFC settlement option exists; confirm whether it applies to your subscription flow.

Does Razorpay Handle Global SaaS Sales Tax and Export Filing for Me?

No. Razorpay provides payment tools and payment records that support your finance workflow, including the documented FIRS process. It does not issue a FIRC or eBRC automatically for every transaction. Your business and its advisers determine export treatment, destination-country tax obligations and the required filings.

What Happens if an International Subscription Payment Fails?

The subscription moves to pending, webhook events notify your application, and Razorpay retries according to the documented T+3 cycle before moving the subscription to halted. You must define customer communication, grace periods, access restrictions and a recovery route. Not every failed charge is recovered.

Do I Still Need to File SOFTEX for SaaS Export Invoices?

The 2026 EXIM regulations replaced SOFTEX with a consolidated Export Declaration Form from 1 October 2026, and a November 2026 amendment deems the EDF submitted for service remittances up to Rs 10 lakh. Confirm your specific filing position with Finance and your AD bank.

Marvil Fernandes

Marvil Fernandes is a content marketing professional at Razorpay, specialising in research-driven content across payments, banking infrastructure, and financial technology. As an Associate in the content marketing team, he focuses on simplifying complex fintech topics for businesses, from payment flows and cross-border transactions to emerging trends in digital commerce and AI in payments.