Payment Methods
Part of Cross-border checkout
Testing payment acceptance with cross-border customers
Plan overseas payment checks by destination, charge currency and method, then separate sandbox behaviour from live outcomes.
Use the payment provider’s permitted test environment to check overseas checkout paths, then review real submitted attempts and their outcomes after launch. A simulated overseas card checks integration behaviour. It cannot predict whether live issuers will approve similar payments.
Define the combinations that matter
List the destinations served and methods intended for those buyers. For each combination, record the charge currency, shopper country used for method eligibility, simulated card-issuing country where relevant, merchant account and any acquiring arrangement. These are different attributes; one overseas test value cannot stand in for all of them.
| Scenario | Inspect |
|---|---|
| Eligible overseas card | Displayed amount and currency, payment request, provider result and order state. |
| Authentication required | Buyer prompt, return or cancellation, and the resulting order state. |
| Declined or unavailable method | Clear message, retained basket and a supported next action. |
| Local payment method | Country and currency eligibility, plus any delayed outcome. |
| Changed destination | Updated method choices and charge currency before payment. |
Select cases the chosen provider supports. Keep the shipping destination, shopper-country setting and simulated issuing country recorded separately, especially when they differ.
Check integration behaviour in test mode
Stripe documents sandbox cards for issuing-country examples, declines and 3-D Secure paths, and directs merchants to use test keys and values. Adyen supplies its own test cards, including issuing-country and authentication examples; they work only on Adyen’s test platform. Use the tools for the store’s provider.
For each supported case, compare the screen with the payment request and saved order. Retain the order reference, provider attempt reference, amount, currency, provider status and customer message. A failed attempt followed by a retry should remain traceable under the same order. A browser return alone is insufficient proof of success when an outcome can arrive later.
Check method availability separately from card processing. Shopify says its local methods require a supported customer country and eligible currency, and some remain in early access. Adyen configures payment-method settings by shopper country. A listed method may still be unavailable to this merchant account.
Payment Test Environment Guidance Summary
- Stripe Test Cards
- Available via https://docs.stripe.com/testing
- Adyen Test Cards
- Issuing-country and authentication examples; only work on Adyen’s test platform
- Shopify Local Payment Methods
- Require supported customer country and eligible currency; some in early access
- Adyen Method Configuration
- Set by shopper country; may still be unavailable to specific merchant accounts
Interpret live outcomes by overseas route
Once a route is live, review its actual submitted attempts by a defined destination, charge currency, method and, where recorded reliably, card-issuing region. Show counts with any rates and state the observation window. Keep pending or unknown outcomes separate until they resolve.
Where provider records allow it, separate issuer declines, merchant risk blocks, authentication failures, cancellations and method-availability errors. These are different reasons for an unsuccessful path. Link retries and method switches to the order before deciding whether a buyer ultimately completed it. A small number of attempts does not support a confident comparison between markets.
Escalate a repeated problem with the relevant attempt references, merchant account, method, currency and time. Keep the distinction between paths verified in test mode and outcomes observed from actual customers.
