International Cards and Wallets: A Payment Gateway Guide for Indian SaaS

International Cards and Wallets: A Payment Gateway Guide for Indian SaaS

An Indian SaaS business has overseas buyers ready to subscribe, but the checkout brief simply says “cards and wallets.” That one line leaves product, engineering and finance holding three different assumptions about launch day. A Google Pay logo may refer to domestic UPI rather than international card checkout. A successful first payment says nothing about whether next month’s renewal will clear.

So the real decision question is this: can my Indian SaaS business offer international cards, Apple Pay and Google Pay through one gateway, and what must I check before launch?

An international payment gateway for Indian businesses lets you collect online payments from overseas customers. Razorpay supports international cards and, for eligible Standard Checkout businesses, Apple Pay and card-based Google Pay. Check merchant approval, wallet eligibility, total charges and recurring-payment compatibility before choosing your flow.

This guide covers the methods, the selection criteria, the costs, the subscription boundaries and the launch checks.

Key Takeaways

  • Razorpay offers documented international card acceptance plus Apple Pay and card-based Google Pay for eligible checkout accounts.
  • International Google Pay card payments and Google Pay UPI are separate flows on separate rails.
  • Apple Pay may require domain verification depending on your integration; international card acceptance requires merchant approval and banking-partner checks.
  • Wallet visibility depends on the customer, card, device and browser as well as your merchant configuration.
  • Verify recurring billing separately from the initial wallet payment. A completed wallet checkout is not proof of a renewal mandate.
  • Confirm the complete fee and FX treatment, your settlement schedule and the available remittance documents before going live.

Which International Cards and Wallets Can Indian SaaS Businesses Accept?

Razorpay lets approved Indian businesses accept international card payments and offers Apple Pay and card-based Google Pay on eligible Standard Checkout accounts. The wallet button a buyer actually sees depends on account enablement plus that buyer’s eligible card, device and browser. Confirm the specific wallet flow rather than assuming international card approval switches on every payment method.

The India international payments documentation states that Razorpay supports cards issued by overseas banks across Visa, Mastercard, Amex, Diners and Discover, with Diners and Discover requiring a support request. That is the card layer. Wallets sit on top of it and carry their own conditions.

International Cards, Apple Pay and Google Pay Serve Different Checkout Needs

Payment option How it fits a SaaS checkout Razorpay scope to explain Check before launch
International card entry Buyer enters an eligible foreign-issued card at checkout International cards require account approval and banking-partner risk checks Business category, KYC, card networks, currency and account configuration
Apple Pay Eligible buyer completes an Apple Wallet payment flow Documented on Standard Checkout with international payments enabled Compatible buyer setup, HTTPS, domain verification where required
Google Pay international cards Buyer pays with eligible cards stored in a Google Account or wallet Documented on eligible international Standard Checkout accounts Account eligibility, a saved supported card, and a supported device and browser
Google Pay UPI UPI-based payment flow for eligible customers Separate from the international card-based Google Pay integration Do not treat UPI activation as proof that overseas wallet card payments are enabled

Supporting references: international debit and credit cards and Apple Pay Standard Checkout. Confirm the current international Google Pay setup guide with your account team before you build against it.

One more 2026 clarification worth making internally. Apple Pay launched domestically in India in late September 2026, with Axis Bank as the first banking partner supporting eligible Visa and Mastercard cards, and no RuPay support. Domestic availability in India and the export wallet checkout your overseas buyers use are two separate questions.

Google Pay International Card Payments Are Different From Google Pay UPI

Look at the funding method, not the logo. On Razorpay surfaces, the Google Pay name appears in more than one place:

  • Google Pay UPI is a domestic UPI route, documented inside the UPI payment method on Standard Checkout.
  • Google Pay card payments on Android apps are a separate saved-card flow. The Google Pay Cards FAQ states this is supported on Android apps, not iOS or web.
  • International card-based Google Pay is the checkout flow relevant to overseas buyers. Razorpay announced on 22 April 2026 that it became the first Indian payment aggregator to enable a card-based wallet experience through Google Pay for international transactions.

A domestic Google Pay UPI option on your checkout does not establish that the international flow is active. Nor does any Google Pay payment automatically bypass bank authentication; stored-card flows can still require 3D Secure.

DID YOU KNOW: Two buttons carrying the Google Pay name can run on completely different payment rails. Check whether the documented flow is a saved-card payment or a UPI collect before you make an international acceptance claim.

When Does Razorpay Fit an Indian SaaS Business Selling Internationally?

Razorpay is a relevant option for an Indian SaaS business that needs international card checkout alongside Apple Pay and Google Pay on eligible accounts. Evaluate it against your target markets, integration effort, recurring-billing requirements, total charges, and finance workflow. An international-first customer base does not by itself require a separate gateway for every geography.

Choose a Checkout Based on Your Buyers and Billing Flow

  • Self-serve overseas signup: Connect documented cards and eligible wallets to the buyer’s actual task, whether that is converting a trial, buying an annual plan, or making a one-time purchase without typing card details where the wallet flow permits it.
  • Existing or new Razorpay implementation: International features require approval regardless. Already using Razorpay domestically may be convenient, but it is not a shortcut past banking-partner checks.
  • Subscription business: Razorpay Subscriptions provides the recurring-payment functionality. Read the next section before you assume method and currency compatibility.
  • Enterprise invoices: Bank-transfer collection exists as a separate route when large customers prefer it. Do not present bank-transfer pricing as the rate for card or wallet checkout.

What Should You Verify Before Choosing Razorpay?

Run a compact decision test. Confirm your supported buyer markets and card networks, the correct wallet flow for those buyers, your checkout implementation path, renewal compatibility, written commercial terms, and the financial evidence your accountant needs. Choose Razorpay when those six requirements match what is both documented and confirmed on your account.

PRO TIP: Write the required payment flow out in full: “overseas customer, saved international card, supported wallet, chosen currency, first payment or renewal.” That sentence makes an account-readiness conversation far more useful than asking whether a gateway simply “supports wallets.”

What Should Indian SaaS Teams Check About Fees, FX and Export Documentation?

Compare the complete cost and finance workflow for your approved route. The India international product page advertises card pricing “up to 3%” with a qualification attached; that is a headline, not a final merchant quote. Confirm processing fees, applicable GST, currency conversion treatment, subscription charges and settlement terms, then check which remittance documents your transactions actually generate.

Separate Card Processing Charges From FX and Optional Services

The international payment gateway in India page carries that qualified up-to-3% headline, with an asterisk. Do not silently convert it into a fixed all-in price or treat it as a contractual floor or ceiling.

Ask your quote to identify each layer separately: processing fee, applicable tax, conversion treatment, recurring-product add-ons where relevant, and refund or dispute charges. Razorpay’s own cost explainer describes MDR, forex markup, GST on the service fee and settlement timing as distinct cost layers, with 18% GST applying to the gateway’s service fee rather than the full transaction value.

There is one widely repeated error worth correcting. A 3.5% figure circulates as “the Razorpay international rate.” Razorpay’s Shopify guide distinguishes the export flow for an Indian business accepting foreign card payments at 3% per transaction from an import flow figure of 3.5% including forex. Direction of payment matters. An Indian SaaS exporter is on the export side.

On wallets specifically, the Apple Pay documentation states there are no additional charges for Apple Pay transactions and that standard card processing rates apply. Do not extend that statement to every wallet or every product without confirmation.

Confirm Settlement and Downloadable FIRS for Your Payment Route

For the documented standard gateway flow, the payment amount is converted to INR and settled to the account as per its settlement schedule, using the processing bank’s exchange rate. Check your own schedule in the Dashboard rather than assuming a universal timeline.

For remittance evidence, the FIRS section of the Dashboard is the starting point. Razorpay’s settlement explainer describes bank-provided certificates and Razorpay-generated statements available based on monthly transactions, with the correct purpose code required, and separates the document types: FIRC is a certificate, eFIRC its electronic form, FIRA an advice and FIRS a statement, while a BRC is issued through the DGFT portal and confirms realisation of export proceeds.

Give finance a practical output: match the payment identifier, the fee and FX deductions, the settlement reference and the relevant statement.

DID YOU KNOW: The FIRS workflow is built around monthly transaction sets and requires a correct purpose code first. That is more precise than assuming every international payment instantly produces every type of export certificate.

Can International Wallet Payments Also Support SaaS Subscription Renewals?

A wallet payment at signup does not establish that the same wallet can fund automatic renewals. Razorpay documents international card support for Subscriptions and states that international-currency subscriptions use cards. Confirm whether your exact Apple Pay or Google Pay flow can establish the required recurring credentials before promising wallet-based renewals.

Separate the First Checkout Payment From Renewal Authorisation

Take a hypothetical monthly software plan priced in US dollars. An overseas buyer completes the first purchase with an eligible wallet. That event proves one thing only: the first charge cleared. Your team must separately confirm how renewal consent and renewal credentials are established.

A saved card inside a buyer’s wallet does not automatically become a reusable merchant token or mandate. Keep six concepts distinct in your design docs: wallet authentication, card tokenisation, customer consent, recurring authorisation, invoice creation and subscription status.

International-Currency Subscriptions Use the Supported Card Flow

The subscriptions documentation is explicit. Only card payments support international currencies, UPI payments do not support international currencies, and settlements are always made in INR. A domestic UPI AutoPay mandate is not an answer to overseas renewal billing.

The authorisation mechanism is also documented: subscriptions are permitted on listed networks provided the customer authorises the first transaction using 2FA or 3D Secure. Separately, the same FAQ notes that the 2021 RBI guidelines for recurring card payments apply to domestic cards rather than international cards.

Distinguish plan-based Subscriptions, suited to fixed billing schedules, from merchant-initiated recurring charges controlled through APIs, which suit usage-based or milestone billing.

Design against the documented lifecycle. Subscription webhook events cover authentication, charges, cancellation, pausing and resuming. For failures, a failed auto-charge moves the subscription to pending, notifies you by webhook and triggers an automatic retry the following day, with the subscription moving to halted once retries are exhausted.

Match the Integration to Your SaaS Billing Model

Fixed monthly and annual plans map cleanly to plan-based subscriptions. A trial converting to paid is implemented by providing a future start date at subscription creation, so authentication happens up front and billing begins later. Variable usage and add-ons need a different decision about who initiates each charge.

Your test plan should cover first authorisation, a subsequent charge, a failed renewal, cancellation and entitlement revocation.

PRO TIP: Treat a completed first payment and an authorised renewal path as two separate launch gates. Record evidence for each before you advertise automatic subscription billing through a wallet.

How Do You Enable International Cards and Wallets on Razorpay?

Complete Razorpay account verification and request international card enablement, then follow the method-specific Standard Checkout requirements. Apple Pay may require a domain-association file and verification depending on your integration. Confirm account status and test the intended buyer environment before announcing availability.

Follow This Seven-Step Activation and Launch Checklist

  1. Define the flow. Record your business category, overseas buyer markets, transaction currency, integration type, required card networks, and whether the payment is one-time or recurring. Output: a written payment-flow specification.
  2. Complete prerequisites. International card acceptance requires an active Razorpay account with KYC completed plus a valid website carrying clearly defined Terms and Conditions, Privacy, Refund and Cancellation, and Shipping (or digital service-delivery) policies. Output: an onboarding checklist reviewed against your delivery model.
  3. Request international card enablement. Use the current Dashboard application flow. International payments are enabled only after banking partners have approved them, and supporting evidence such as invoices, bank statements or prior settlement records helps that approval. Output: actual approval, or a recorded pending status.
  4. Configure Apple Pay for your integration. The Apple Pay tile appears in the Dashboard only when international payments are active. Where hosting is required, the association file must sit at the exact path, be reachable over HTTPS, and return HTTP 200 rather than a 301 or 302 redirect, matching Razorpay’s file content exactly. Some platform integrations handle verification at the platform level instead. Output: verified domain status.
  5. Confirm international Google Pay availability. Check your eligible international Standard Checkout status and the supported card list with your account team. Build a test plan covering a compatible buyer, saved card, device and browser. Output: confirmed eligibility plus a documented test matrix.
  6. Verify the complete transaction. Check method visibility, behaviour on ineligible browsers, bank authentication where applicable, server-side payment confirmation and entitlement logic. Use webhooks for real-time notifications including payment failure rather than granting access on a browser success screen alone. Note that Apple Pay does not work in test mode, so any controlled live payment needs separate internal authorisation. Output: retained payment evidence.
  7. Verify finance and renewals separately. Reconcile the payment, deductions and settlement, confirm available FIRS records, and test the intended recurring setup independently. Output: finance sign-off plus a subscription test record.

Build the checkout itself on the Razorpay Payment Gateway Standard Checkout integration where possible.

Why a Wallet Button May Not Appear

Work through this list before escalating. International payments may not be active on the account, which means the Apple Pay tile never appears. Domain verification may be failing on a redirect or a wrong path. The buyer may not be signed in with an eligible saved card, or may be on an unsupported device or browser. Google Pay availability may not yet cover your account. Note also that Checkout is not supported on Internet Explorer, and that the Checkout pop-up does not appear in certain in-app browsers, where a callback URL is the workaround.

DID YOU KNOW: Razorpay’s documentation states that Apple Pay does not work in test mode. Plan an appropriately authorised live verification instead of treating a sandbox card payment as proof of wallet readiness.

How Should SaaS Teams Handle Payment Failures, Refunds and Reconciliation?

A successful international checkout needs more than a visible wallet button. Track each payment’s confirmed status, update SaaS access safely, give failed payments a recovery path, and reconcile fees against settlements. Review renewal failures separately from first-purchase failures.

Diagnose the Payment Stage Before Choosing a Fix

  • Distinguish a missing method, an abandoned checkout, an issuer or 3D Secure decline, a captured payment and a failed renewal. Not every failure is a gateway outage.
  • Preserve issuer authentication where it is required. Razorpay documents 3D Secure 2.0 support for international cards, so never advertise universally OTP-free payments.
  • The documentation warns that an international payment will fail if a dummy email ID and phone number are sent. Check what your trial signup flow passes through.
  • Offer supported alternative methods where appropriate and tell the customer their next action clearly.
  • Confirm current refund and dispute behaviour before promising turnaround times. International cardholders may have up to 120 days to file a dispute, so evidence retention matters.

Give Finance a Reconciliation Trail

Specify the payment and invoice IDs, transaction currency, conversion basis, processing fee, tax, refund or dispute adjustments, net settlement and statement reference. Two documented fields help: non-INR payments carry base_amount and base_currency on the payment entity, and Apple Pay payments are identifiable through a notes field containing provider: apple_pay.

International SaaS Payment-Flow Decision Table

SaaS situation Payment flow to evaluate Razorpay connection Decision that still needs confirmation
One-time annual software purchase International card or eligible wallet checkout International cards plus Apple Pay and card-based Google Pay on eligible Standard Checkout accounts Account approval, card networks, buyer compatibility, complete charges
Monthly overseas subscription Approved international card subscription flow Razorpay Subscriptions supports recurring card payments and documented international-currency billing Exact wallet-to-subscription compatibility, consent capture and renewal authorisation
Trial converting to a paid plan Plan and subscription lifecycle with a future start date Trial and plan functionality plus first-transaction authorisation and lifecycle webhooks First charge timing, failed conversion handling and entitlement behaviour
Enterprise customer paying an invoice Card checkout or separately enabled bank-transfer collection International Payments offers different collection routes Customer preference, ticket size, commercial terms and route-specific documents

Ticket size is a genuine routing factor for enterprise contracts, since cross-border aggregator export transactions operate under a maximum transaction value of Rs 25 lakh per transaction.

Choose the flow that matches the buyer and the billing requirement, then confirm that flow on your actual account before you publish pricing pages or onboarding emails.

Frequently Asked Questions

Can an Indian SaaS business accept Apple Pay and Google Pay from overseas customers?

Yes. Razorpay documents Apple Pay and card-based Google Pay on eligible Standard Checkout accounts with international payments enabled. Merchant approval and buyer compatibility still apply. Apple Pay may require domain verification depending on your integration, and international Google Pay availability should be confirmed for your specific account. Availability is not automatic for every account, card or market, so verify before you advertise the method.

Is international Google Pay the same as Google Pay UPI in India?

No. The international flow uses eligible cards saved in a Google Account or wallet. Google Pay UPI is a separate payment route, and Google Pay card payments on Android apps are a third, domestic flow. A domestic Google Pay option does not prove international card-wallet acceptance is active. Ask which flow is enabled and whether your buyer’s device and browser qualify.

Can Apple Pay or Google Pay automatically renew an international SaaS subscription?

Do not infer automatic renewals from a successful wallet checkout. Razorpay supports documented international card subscriptions, and the subscriptions documentation states that international currencies are supported on card payments while UPI is not. Your team must confirm how its exact wallet integration establishes recurring consent and credentials. A one-time wallet authorisation alone is not evidence that you can charge future renewals.

What does it cost to accept international cards and wallets with Razorpay?

The India international product page advertises qualified card pricing up to 3%. Confirm your exact merchant quote and the current offer terms. Separate the processing charge, applicable GST, FX treatment and any recurring-product charges. Apple Pay documentation says standard card-processing rates apply with no additional Apple Pay fee. Do not read the headline as all-inclusive.

What should finance check after an international SaaS payment?

Confirm the transaction and invoice identities, currency and conversion treatment, deductions, net settlement and the available remittance statement. The FIRS workflow provides downloadable records based on monthly transactions and requires an appropriate purpose code, which is assigned at payment setup rather than after settlement. FIRS, FIRC, FIRA and e-BRC are not interchangeable.

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.