- Introduction to Payments
- Standard Payment Processing
- Card Present Connect | Retail Processing
- Authorization with Contact EMV and Online PIN
- Authorization with Contact EMV and Offline PIN
- Card Present Connect | Mass Transit Processing
- Debit and Prepaid Card Processing
- Processing Debit and Prepaid Authorizations
- Airline Data Processing
- Japanese Payment Options Processing
- Processing Payments Using Credentials
- Using Stored Customer Credentials During a CIT
- Merchant-Initiated Delayed Transaction with PAN
- Merchant-Initiated Incremental Transaction with PAN
- Merchant-Initiated No-Show Transactions with PAN
- Merchant-Initiated Reauthorization Transactions with PAN
- Merchant-Initiated Resubmission Transaction with PAN
- Installment Payments
- Recurring Payments
- Merchant-Initiated Recurring Payments with PAN
- Token Management Service Processing
On This Page
REST API | Visa Platform Connect
Authorizations with Foreign Merchants
Visa mandates marketplaces identify domestic marketplace transactions where the
marketplace and issuer are in the same country, but the retailer is in a different
country. For marketplaces in the European Economic Area (EEA) and the UK (and
Gibraltar), this includes transactions where the marketplace and the issuer are within
the EEA, UK, and Gibraltar, but the retailer is not located within the EEA, UK, and
Gibraltar. This is flagged using the Foreign Retail Indicator (FRI).
IMPORTANT
This feature is intended to be used during a settlement. While you
can include this information in an authorization, this is not the preferred
method.
When you include the
merchantInformation.merchantDescriptor.country
and aggregatorInformation.subMerchant.country
fields and the merchant and submerchant
are located in separate locations, within the authorization request, the transaction
includes the foreign retail indicator flag. However, this flag is only submitted during
settlement process and if the same fields are included in the capture request, the
capture request will override the information included in the authorization request.Fields Specific to this Use Case
These fields are required for this use case:
- merchantInformation.merchantDescriptor.country
- If the Merchant country is not submitted, the merchant country associated with the transaction MID will be used.
- aggregatorInformation.subMerchant.country
- If the Merchant country is not submitted, the merchant country associated with the transaction MID will be used.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/paymentsTest:
POST
https://apitest.cybersource.com
/pts/v2/payments