# Cross Border Payments
source: https://developer.mastercard.com/open-finance-europe/documentation/licensed/aiia-enterprise/payments/cross-border-payments/index.md

Some ASPSPs are participants of international payment schemes, such as Single Euro Payment Area (SEPA) for payments in euros (€).

It is therefore possible using our payment initiation APIs, to request a payment between source and destination IBANs in different countries, provided that:

1. both ASPSPs are participants in the SEPA scheme; and
2. the payment is made in euros.

### Cross-border payments limitations {#cross-border-payments-limitations}

However, when doing so it is important to note the following limitations:

##### IBAN discrimination {#iban-discrimination}

Some financial institutions may practice [IBAN discrimination](https://www.ecb.europa.eu/paym/groups/pdf/efip/IBAN_discrimination_update.pdf), where they apply different rules and barriers to payments originating from other countries compared to domestic payments. This can include and is not limited to, for example, additional PSU approval/authorization steps. This is in conflict with European Commission's best practice guidance, but nonetheless IBAN discrimination does sometimes occur, and may impact conversion rates.
Note: Where this does occur, it is outside of Mastercard's control to resolve and Mastercard takes no liability for this.

##### Field requirements {#field-requirements}

ASPSPs' field requirements for the payment request (i.e. the rules determining which fields are mandatory in a payment request) sometimes changes when a payment is cross-border compared to domestic. This means that customers who have been using domestic payments might encounter failures or errors when attempting the same types of requests for a cross-border payment.
Note: It is therefore important that you carry out your own thorough testing before attempting a cross-border implementation.

##### Field mapping {#field-mapping}

Customers might also find that ASPSPs' mapping of fields sometimes change when a payment is cross-border compared to domestic, meaning that fields or values used for reconciliation may not be received as expected at the destination bank.
Note: It is therefore important that you verify (by testing) the mapping of any fields necessary for your solution before attempting a cross-border implementation.

##### Settlement time {#settlement-time}

The time period from requesting a payment initiation to payment settlement can differ when making a cross-border payment as compared to a domestic payment.

### Local destination accounts {#local-destination-accounts}

As a result, we recommend that wherever possible, you should specify a destination account which is local to the source accounts that PSUs are making payments from. This will generally result in lower development effort, less operational effort, and higher conversion.

If you do wish to proceed with cross-border SEPA payments, you will be responsible for conducting testing to observe real-world behaviors when making payments from each source ASPSP, to the desired destination IBAN(s).