# Gateway Features
source: https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/index.md

Depending on your needs, Mastercard Gateway offers several optional features for handling particular data and transaction types, or improving your payment flows:

## Recurring Payments {#recurring-payments}

Recurring Payments allow merchants to collect, store, and reuse payment details for future transactions. These payments can be initiated either with the cardholder's active participation or by the merchant based on prior consent and agreement. By supporting both cardholder-initiated and merchant-initiated transactions using stored payment details, the gateway helps streamline payment processing, improve payer experience, and ensure compliance with card scheme requirements.

For more information, see [Recurring Payments](https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/cit-mit/index.md).

## Dynamic Currency Conversion {#dynamic-currency-conversion}

Dynamic Currency Conversion (DCC) lets you offer payers the choice to complete a payment in your currency or in their card billing currency at checkout using real‑time exchange rates. This provides pricing transparency for the payer while allowing you to receive a share of the currency conversion fee and settle transactions in your own currency.

For more information, see [Dynamic Currency Conversion](https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/dynamic-currency-conversion/index.md).

## Surcharging {#surcharging}

Surcharging allows you to add an extra fee to card payments to recover processing costs based on factors such as the integration method, card type, and transaction currency, subject to regional and scheme regulations.

For more information, see [Surcharging](https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/surcharging/index.md).

## Click to Pay {#click-to-pay}

Click to Pay is a fast and secure way for customers to pay online without having to manually enter their card details every time.

For more information, see [Click to Pay](https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/click-to-pay/index.md).

## Data and Reporting {#data-and-reporting}

You can use the [Reporting](https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/data-and-reporting/reporting/index.md) API to download data from the gateway about all the transactions related to your merchant account. You can get formatted reports about transactions created or updated within a specified period. The reports can be downloaded in the CSV format for analysis.
You can add supplementary data to your requests to support specific industry requirements. In addition, supplementary data can be used to ensure a smoother processing flow for the payment as it moves through the various actors in the payment system.
If you used a different payment provider before, you can bring your old payment data, like tokens from that provider, into the Mastercard Gateway system.

For more information, see [Data and Reporting](https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/data-and-reporting/index.md).

## Payment Alerts {#payment-alerts}

Payment Alerts is a network-driven notification service that informs merchants when a payment declined for insufficient funds is likely to succeed if retried. The service delivers alerts in near real time, enabling smarter retries with higher success rates and no guesswork.

For more information, see [Payment Alerts](https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/payment-alerts/index.md).

## Webhook Notifications {#webhook-notifications}

You can receive notifications on your system when a transaction for an order is created or updated in the gateway. This allows you to update your own records accordingly. The notifications can be sent to you as Webhooks or email messages, and you can also configure your payers to receive some notifications through email.

For more information, see [Webhook Notifications](https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/webhook-noti/index.md).

## Transaction Enrichment Data {#transaction-enrichment-data}

The gateway offers special features for merchants handling contactless transactions related to transit fares. For example, you can aggregate a payer's transaction fares across multiple trips for a certain time period and up to a certain amount.
If you use Point of Sale (POS) terminals for gathering payments, you can use the gateway to manage Cardholder Present (CHP) transactions through your terminal.

For more information, see [Transaction Enrichment Data](https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/trans-enrich-data/index.md) .

## Multi-Party Payment Models {#multi-party-payment-models}

Multi-Party Payment Models involve payment flows where more than two parties participate in handling a transaction. Beyond the buyer and seller, these models include additional participants such as marketplaces and aggregators, enabling more complex payment interactions within the gateway.

For more information, see [Multi-Party Payment Models](https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/multi-party-payment-model/index.md) .

## Mastercard Cloud Commerce {#mastercard-cloud-commerce}

Cloud Commerce is a cloud-based, MPOC pre‑certified acceptance solution that handles Tap on Phone and Pay by Link journeys while the actual authorization or refund runs through Gateway APIs.

For more information, see [Mastercard Cloud Commerce](https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/cloud-commerce/index.md) .