Cross-Border Payments

Accept international payments and route each transaction to an eligible channel.

Manage foreign cards, market needs and provider connections together with MagicPay. Connect international payments to routing, refunds and reporting.

Focus on your business with Cross-Border Payments

Routing based on foreign-card and market information
Controlled alternative routing for technical errors
Centralized transaction tracking by country and provider

Selling internationally requires more than translating the payment screen. The card's country of issue, the customer's preferred method, transaction currency and provider terms all matter. MagicPay cross-border payment infrastructure brings existing bank and payment institution connections into one transaction model. You select an eligible channel for each sale through your rules and track payments from different markets centrally using order and provider references.

Connect foreign cards to the right channel

BIN information is used to assess card country and type, then the transaction follows a configured priority among connections eligible to accept foreign cards. Card country alone does not determine the outcome: authentication, provider response and transaction status are followed together. Your technical team sees the route used while finance sees which sale completed in the same record.

  • Market information: consider customer country and card country of issue together in payment analysis.
  • Eligible connection: choose a provider according to card, currency and commercial priority.
  • Shared history: retain the routing decision and provider response against the order reference.

Controlled alternative routing for technical errors

A technical problem with one bank connection should not affect all international payment operations in the same way. Alternative-provider and retry rules apply to eligible error types. A definitive card decline is treated separately from a connection error, and an uncertain outcome is checked first. Support can read the initial attempt and subsequent steps in the same history when updating the customer.

Market, cost and outcome in one report

Compare transaction outcomes, fee terms and provider records by country and channel. Reflect cost priorities in your routing rules and follow their effect using your own sales data. While Multi-Currency separates pricing, collection and settlement amounts, this page focuses on the market and card flow that delivers international customers' payments to eligible channels.

Who is it for?

Export-focused online stores, hotels and tourism businesses collecting from international guests, education institutions serving international participants and digital services with global customers. Instead of separate operations for each market, support and finance work with a shared order reference. Refund investigations also continue from the international customer's original payment record.

Build your international payment flow in three steps

Prepare your target markets, existing agreements and sales channel together.

  • 1. Match customer markets and foreign-card needs to the relevant provider accounts.
  • 2. Define routes by card country, currency and cost priority; test authentication and error scenarios.
  • 3. Link payments and refunds to the order; compare country, channel and provider outcomes in the same dashboard.

Related solutions and resources

FAQ

Frequently asked questions about this product

Answers about usage, integration and operational scope.

Can I use my existing bank agreements? +

Yes. Connect existing channels eligible for foreign cards and the relevant currency to MagicPay. Provider accounts join the shared transaction model, and new connections can be added to the same structure.

How are foreign-card transactions routed? +

Card country, type, currency and configured commercial priorities are evaluated. The transaction is sent to a channel selected by your rules among active provider connections eligible for that sale.

What happens if a connection returns a technical error? +

The initial outcome is reviewed and eligible technical errors can trigger an alternative route or retry. An uncertain transaction is checked first, and all steps remain linked to the same order.

How is it different from Multi-Currency? +

Cross-border payments focus on markets, foreign cards and provider selection. Multi-Currency manages pricing, collection and settlement currencies in separate records. The two products work together.