How to Handle Failed International Payments as an Indian Business in 2026

Failed international payments are inevitable. Cards expire, credit limits hit, banks decline suspicious transactions, 3DS authentication times out. For Indian businesses billing international clients, a failed payment isn't just a missed receipt — it's a potential relationship risk if not handled correctly and promptly.

This guide covers every type of failed international payment, why it happens, and what to do.

Types of Failed International Payments

1. Card Declines

The most common failure. When an international client's card is declined, it falls into two categories:

Soft decline: Temporary failure. Can be retried.

Insufficient funds at moment of charge
Bank's fraud detection triggered (unusual merchant geography)
Daily/monthly card limit reached
3DS authentication failure or timeout Hard decline: Permanent failure. Do not retry.
Card cancelled or expired
Card reported lost or stolen
Card permanently blocked by bank
Account closed How to know which type: Playto Pay's dashboard shows decline codes. Soft declines typically show codes like insufficient_funds, card_velocity_exceeded, authentication_required. Hard declines show card_not_supported, do_not_honor permanently, lost_card, stolen_card.

2. 3DS Authentication Failures

For European clients especially (EU SCA requirements), 3DS authentication is required. Failure modes:

Customer doesn't complete OTP within timeout window
Customer closes 3DS window
Customer's bank doesn't support 3DS 2.0 Response: Resend a fresh payment link with a note that the previous one expired. Many customers who fail 3DS just need a second attempt.

3. Wire Transfer Failures

Beneficiary account issues: Wrong VBA account details provided (typo in account number or routing)
Currency mismatch: Client sent USD to your GBP VBA
AML hold: Bank held the wire for anti-money laundering review
Sanctions screening: Rare but can affect wires from certain countries
Correspondent bank deduction: Fees deducted mid-route, short payment received

4. Recurring Billing Failures

For SaaS or membership subscription auto-charges:

Expired card
New card issued (client got a new card number, old card on file no longer valid)
Insufficient balance at charge date
Card issuer blocked recurring charges from your merchant descriptor

Immediate Response Protocol

For card declines:

Check decline type (soft vs hard) in your payment platform dashboard
For soft declines: wait 24-48 hours, retry once automatically (most platforms do this)
If retry fails: send customer an email with fresh payment link
Keep email professional, not accusatory: "Our payment system encountered an issue processing your card. Please update your payment method using this link."
Follow up once more after 5 days if no response
After 14 days of non-payment: pause service, contact client directly For 3DS timeouts:
Resend payment link immediately with note: "The previous payment link expired. Please use this new link to complete your payment."
Most 3DS timeouts resolve on second attempt For wire failures:
Check your VBA dashboard — if the wire hasn't arrived in 3 business days, contact client
Ask client to share wire confirmation (shows reference number, amount, destination)
Trace the wire with your payment platform's support team
If currency mismatch (client sent wrong currency), coordinate return and re-send For recurring billing failures:
Auto-retry via dunning (Playto Pay does this automatically)
Email customer on Day 1 of failure: "We couldn't process your subscription renewal. Please update your card here."
Retry on Day 3, Day 7, Day 14
Suspend subscription access on Day 21 if unresolved
Offer a pause option as alternative to cancel (reduces permanent churn)

Preventing Failed Payments

Card expiry prevention:

Send card expiry reminders 30 days before a client's stored card expires (Playto Pay's dunning handles this)
Include "update payment method" link in pre-expiry emails 3DS completion rate improvement:
Use 3DS 2.0 (risk-based, frictionless for low-risk transactions) rather than 3DS 1.0
Ensure your payment descriptor matches your business name (unfamiliar descriptors trigger bank declines)
Send checkout links with context: "Click to pay for Invoice #001" not just a bare URL Wire transfer accuracy:
Double-check VBA details before providing to client
Include reference number in wire instructions (helps match received wire to invoice)
Confirm currency: ensure client is sending the currency your VBA accepts Recurring billing failure reduction:
Offer annual plans (less failure exposure than 12 monthly charges per year)
Use Visa Account Updater / Mastercard Automatic Billing Updater (Playto Pay integrates with these services to auto-update stored card details when banks reissue cards)

What to Say to Clients

Card decline email (professional, not accusatory):

Subject: Action needed: payment for Invoice #[X]

Hi [Name],

We encountered an issue processing your payment for Invoice #[X] dated [date].

This can happen for various reasons — often a quick card update resolves it.

Please complete your payment here: [payment link]

If you have any questions, reply to this email.

[Your name]

Wire failure email:

Subject: Following up on wire for Invoice #[X]

Hi [Name],

We haven't received your wire transfer for Invoice #[X] dated [date]. This may be a delay in processing.

Could you share the wire transfer confirmation from your bank? This helps us trace it.

Payment details for re-sending if needed: [VBA details]

[Your name]

How Playto Pay Handles Failed Payments

Playto Pay includes:

Dashboard alerts for failed charges with decline code classification
Automatic retry for soft declines (configurable timing)
Dunning email sequences for recurring billing failures
Customer portal for clients to update payment methods
Visa/MC card updater integration to auto-refresh expired cards on file
3DS 2.0 for improved authentication success rates

FAQ

What should I do when an international client's card is declined? Check the decline type (soft vs hard) in your dashboard. For soft declines: retry after 24-48 hours and send a fresh payment link. For hard declines: contact the client to update their payment method.

How long should I wait before following up on a failed international wire? If a wire hasn't arrived within 3 business days of the expected receipt date, contact the client and ask them to share the wire confirmation from their bank.

Should I suspend service immediately when a payment fails? Not immediately. Follow a 21-day dunning sequence (retry + reminders) before suspending. Most payment failures are administrative, not intentional non-payment.

What is a soft decline vs hard decline for international cards? Soft declines are temporary (insufficient funds, fraud flag, velocity limit) and can be retried. Hard declines are permanent (card cancelled, reported stolen) and should not be retried — contact the client for a new card.

How do I prevent 3DS authentication timeouts for European clients? Use 3DS 2.0 (better UX than 3DS 1.0). Ensure your payment descriptor is recognizable. Resend payment link immediately if client fails to complete 3DS — most retry successfully on second attempt.

Does Playto Pay handle dunning automatically? Yes. Failed subscription charge triggers automatic retry sequences and customer notification emails. Configurable timing (Day 3, Day 7, Day 14 retries).

What happens to FIRA when a payment fails and is later recovered? FIRA is generated only when the payment is successfully processed and settled. A failed payment generates no FIRA. The successful retry generates a new FIRA with the actual settlement date.