# Visa Marketplace Mandate
source: https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/multi-party-payment-model/visa-marketplace/index.md

Your payment service provider offers support for you to comply with the Visa mandate for marketplaces. According to the Visa mandate, a business entity is considered a marketplace if it runs a platform that brings together multiple Buyers and retailers.
This unique feature allows a marketplace to manage sales from retailers located in different countries. The acquirers of a marketplace must identify transactions on a marketplace that are initiated by foreign retailers, who are in a different country than the marketplace.

The following methods are supported:

| Integration methods |                             Payment methods                              |                 Transactions                  |
|---------------------|--------------------------------------------------------------------------|-----------------------------------------------|
| All                 | Credit cards (Visa\*) \*For non-Visa card payments, the data is ignored. | * AUTHORIZE * PAY * CAPTURE * REFUND * VERIFY |

If you are registered as a marketplace:

* You cannot be an [aggregator](https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/multi-party-payment-model/aggregator/index.md), payment facilitator.
* You own the transactions done by payers on your marketplace and are responsible for resolving any disputes or issues.
* Do not provide sub-merchant details when you submit transactions to the gateway.

## Prerequisites {#prerequisites}

To be considered a marketplace, you must:

* Register with Visa as a marketplace to get a Visa-issued Marketplace ID.
* Obtain the Merchant Category Code (MCC) of 5262 assigned by Visa from your payment service provider.

## Submitting transactions {#submitting-transactions}

When submitting a transaction as a marketplace, no additional details on top of the usual mandatory ones (amount, card details, currency, and transaction source) need to be provided in the [Authorize](https://developer.mastercard.com/mastercard-gateway/documentation/api-reference/v100/rest/api-ops/index.md#transaction), [Pay](https://developer.mastercard.com/mastercard-gateway/documentation/api-reference/v100/rest/api-ops/index.md#transaction), [Capture](https://developer.mastercard.com/mastercard-gateway/documentation/api-reference/v100/rest/api-ops/index.md#transaction), [Refund](https://developer.mastercard.com/mastercard-gateway/documentation/api-reference/v100/rest/api-ops/index.md#transaction), and [Verify](https://developer.mastercard.com/mastercard-gateway/documentation/api-reference/v100/rest/api-ops/index.md#transaction) Operations, except for the retailer location.

Acquirers of marketplaces must identify foreign retailer transactions (where the retailer location is different than the marketplace location) done on the marketplace platform. If the merchant is a marketplace, the merchant must provide location details of the retailer for whom they are submitting the transaction in the `order.marketplace.retailerlocation` field. The field can have the following values.

* DOMESTIC_ONLY  

  Items are only from domestic retailers.

* FOREIGN_ONLY  

  Items are only from foreign retailers.

* FOREIGN_AND_DOMESTIC  

  Items are both from foreign and domestic retailers.

For Visa Marketplace transactions processed through Worldpay™ acquirers, when the retailer's country differs from the marketplace's country, you must populate the `transaction.acquirer.customData` field with the retailer's ISO 3166‑1 alpha‑3 country code.

For example:

* `USA` for the United States
* `IND` for India

    transaction.acquirer.customData: {
      "foreignRetailerCountryCodeForMarketplace": "USA"
    } ``