Skip to main content
Available in🇮🇳 India
This page covers testing international card payments on S2S JSON (POST /v1/payments/create/json) and S2S Redirect (POST /v1/payments/create/redirect) across the three forex flows. If you have not yet, read Forex Conversion first. The scenarios below check the behaviour it describes.
Before you startRun the Cards test page first. Authentication, declines, tokens and signature checks work the same way for international cards and are not repeated here. You need international payments enabled on your test account, and each non-INR currency you want to charge in enabled on that account.

1. Test Mode Coverage

FX rates in test mode are dummy ratesThe rates used to convert non-INR amounts into INR in test mode are dummy FX rates. They may not match actual mid-market rates and are subject to change. Do not hard-code or assert exact INR values in your tests.

How live mode and test mode differ

What you can test

2. Test Kit

  • Use any future expiry date and any 3-digit CVV.
  • On the mock bank page, enter any OTP of 4–10 digits, or choose Success.
  • For declines and other failures, use the failure cards on the Cards test page. They behave the same on non-INR orders.

International test cards

Amounts and currencies

amount is always in the smallest unit of the order’s currency. Test at least one INR order and one order in every non-INR currency you will charge in. If you sell in zero- or three-decimal currencies, test those too.

3. Scenarios to Test Your Integration

  • Must-have (5): the paths where money moves. All have to pass before you go live.
  • Other common scenarios (5): things that happen in normal operation.
  • Error scenarios (4): failures you trigger on purpose. Exact errors are in Simulate failures.
  • Not available in test mode (4): check these in a small live test.
Every scenario is self-contained. Each one creates its own order and payment, so you can run any scenario on its own, in any order. There are 18 scenarios in all: 14 you can run in test mode today and 4 you cannot. Any INR conversion in test mode uses dummy FX rates.

3.1 Must-have

Scenario IDFlowScenarioTrigger credsSteps to followExpected result
INTL-01Flow 1INR order paid with an international card4012 8888 8888 1881, order in INR1. Create an order: .
2. Create the payment with that order_id and the international card; complete authentication.
3. Call GET /v1/payments/{payment_id}.
Check: status: captured, international: true, currency: INR, amount: 1000000.
Webhooks: payment.authorized, payment.captured, order.paid
Your integration should: store payment_id, order_id and receipt so the payment can be matched to its settlement recon line later.
INTL-02Flow 2Non-INR order paid with an international card4012 8888 8888 1881, order in USD1. Create an order: .
2. Pay with the international card, using the same currency in the payment request.
3. Call GET /v1/payments/{payment_id}.
Check: status: captured, international: true, currency: USD, amount: 10000.
Webhooks: payment.authorized, payment.captured, order.paid
Your integration should: keep the presented amount and currency for the customer and refunds. Take the INR converted and settled amounts from the Settlement Recon API, never from amount or your own FX rate.
INTL-03Flow 1, 2Fetch settlement recon details and map them to paymentsYour test API keys1. Call GET /v1/settlements/recon/combined?year=YYYY&month=MM&day=DD.
2. Call it again with count and skip to check pagination.
3. Run your mapping logic: type: payment lines on entity_id or order_id, type: refund lines on payment_id.
Check: HTTP 200 with entity: collection. Your code handles a collection with no payment lines (test mode has no settlements) and pages until all lines are read.
Webhooks: None
Your integration should: record credit as the settled amount for each payment and debit for each refund, in INR paise. Settled values are verified live in INTL-X2.
INTL-04Flow 3Full refund of an INR order4012 8888 8888 1881, order in INR1. Create an order: .
2. Pay it with the international card and confirm it is captured.
3. POST /v1/payments/{payment_id}/refund with .
4. Fetch the payment.
Check: Refund currency: INR, moves to processed. Payment shows refund_status: full, amount_refunded: 1000000.
Webhooks: refund.created, refund.processed (or refund.failed)
Your integration should: tell the customer the refund was issued in INR and their bank may convert it at a different rate.
INTL-05Flow 3Full refund of a non-INR order4012 8888 8888 1881, order in USD1. Create an order: .
2. Pay it with the international card and confirm it is captured.
3. POST /v1/payments/{payment_id}/refund with , that is USD 100.00 in cents, not an INR converted value.
4. Fetch the payment.
Check: Refund currency: USD, amount: 10000, moves to processed. Payment shows refund_status: full.
Webhooks: refund.created, refund.processed (or refund.failed)
Your integration should: build refund amounts from the payment’s amount and currency only.

3.2 Other Common Scenarios

Scenario IDFlowScenarioTrigger credsSteps to followExpected result
INTL-06Flow 2Non-INR orders in two different currencies4012 8888 8888 1881, orders in USD and EUR (or GBP)1. Create and .
2. Pay each with the international card.
3. Fetch both payments.
Check: Both captured, each in its own presentment currency.
Webhooks: payment.captured, order.paid
Your integration should: have no hard-coded rates or currency lists. INR values for every currency come from the Settlement Recon API.
INTL-07Flow 3Partial refunds in the presentment currency4012 8888 8888 1881, order in USD1. Create an order: and pay it.
2. Refund 3000 (USD 30.00) and fetch the payment.
3. Refund 7000 (USD 70.00) and fetch again.
Check: After the first: refund_status: partial, amount_refunded: 3000. After the second: full, 10000. Both refunds in USD.
Webhooks: refund.created, refund.processed for each
Your integration should: track the refundable balance in the presentment currency: amount − amount_refunded.
INTL-08Flow 2Zero- and three-decimal currencies4012 8888 8888 1881, orders in JPY, KWD (only if you sell in them)1. Create and .
2. Pay each and fetch the payment.
Check: Customer is charged ¥1,000 and KWD 10.500.
Webhooks: payment.captured, order.paid
Your integration should: convert prices using each currency’s exponent, not by always multiplying by 100.
INTL-09Flow 2Retry on the same non-INR order after a decline4100 2800 0005 0004 + Failure, then 4012 8888 8888 18811. Create a USD order: .
2. Pay with the decline card and choose Failure.
3. Pay the same order again with the international card.
Check: First payment failed with card_declined. Second captured. Order goes attempted → paid.
Webhooks: payment.failed, then payment.captured, order.paid
Your integration should: expect only the captured payment to appear in settlement recon. Do not wait for a line for the failed one.
INTL-10Flow 1, 2International card that asks for a billing address5105 1051 0510 5100, orders in INR and USD1. Create an INR order and a USD order.
2. Pay each with this card; collect and send the billing address when asked.
3. Fetch both payments.
Check: Both succeed, each in its own presentment currency.
Webhooks: payment.authorized, payment.captured, order.paid
Your integration should: handle the billing address step without losing the order’s currency.

3.3 Error Scenarios

Scenario IDFlowScenarioTrigger credsSteps to followExpected result
INTL-E1AllInternational payments not enabled4012 8888 8888 1881 on an account without international enabled1. Create an INR order.
2. Pay with the international card.
Check: international_transaction_not_allowed. No payment captured.
Webhooks: payment.failed if the payment was created
Your integration should: show error.description and offer another payment method.
INTL-E2Flow 2Currency not enabled or not validOrder in a currency not enabled; “currency”: “XYZ”1. Create an order in each currency.Check: HTTP 400 and no order created.
Webhooks: None
Your integration should: only offer currencies enabled on your account at checkout.
INTL-E3Flow 3Refund more than the payment amount4012 8888 8888 1881, order in USD1. Create a USD order (10000) and pay it.
2. Refund with an INR converted value in paise (for example 880000), as if mixing up INR and USD.
Check: Refund rejected with HTTP 400. No refund created.
Webhooks: None
Your integration should: validate refund amounts against amount − amount_refunded in the presentment currency before calling the API.
INTL-E4Flow 3Refund a payment that is already fully refunded4012 8888 8888 1881, order in USD1. Create a USD order (10000) and pay it.
2. Refund 10000.
3. Refund it again.
Check: Second refund rejected with HTTP 400.
Webhooks: refund.created, refund.processed for the first refund only
Your integration should: block refunds once refund_status is full.

3.4 Not Available in Test Mode

4. Webhooks: What Fires and What It Lets You Decide

5. Common Integration Gaps to Avoid

6. Simulate Failures

Branch on error.reason, never on the description text. Back to Forex Conversion
Last modified on November 18, 2026