# Network Uplift (Mastercard IDCI)

The integration grants access to Forter's [Fraud Management](/content/platform/fraud-management/ "Fraud Management"/index.html) and [Issuer Optimization with Mastercard](/content/platform/payment-optimization/issuer-optimization/ "Issuer Optimization with Mastercard"/index.html).

## [Integration Flow](https://docs.forter.com/network-uplift-mastercard-idci#integration-flow) Integration Flow

## [Integration Steps](https://docs.forter.com/network-uplift-mastercard-idci#integration-steps) Integration Steps

1. ### [Confirm Prerequisites](https://docs.forter.com/network-uplift-mastercard-idci#confirm-prerequisites) Confirm Prerequisites
   Verify that both Forter's and your PSP's integration requirements are met.

**Full PAN**  
   Verify that you can pass the full card number in the Order API. This information is required for Issuer Optimization with Mastercard IDCI.

If you have vaulted cards and the full card number is not exposed on the checkout page, please check with your Tokenization vendor regarding the availability of a Detokenization Proxy service. This service enables you to make a request to a 3rd party (such as Forter Order API) with a Token included in the request. The request is then routed through the proxy, where the token is replaced with the corresponding card data.

**Gateway , Processor and Acquirer Data**  
   Verify that you can pass all the details about the expected Authorization process in the Order API:
   
   **Gateway Data**  
   Name (e.g Braintree)

**Processor Data**  
   Name (e.g Chase Paymentech)

**Acquirer Data**  
   Acquirer Name (e.g Barclays)  
   Acquirer BIN  
   Acquirer Merchant Id  
   Acquirer Merchant Name  
   Merchant Category Code  
   Merchant Country Code  
   AcquirerCountry  
   
   Note that it in some cases the GW, Acquirer and Processor services are provided by the same company.

2. ### [Front-end Integration](https://docs.forter.com/network-uplift-mastercard-idci#front-end-integration)  
   Follow the instructions for front-end integration for Fraud Management, including installing Mobile SDKs on your mobile applications.

3. ### [Send Order API Request](https://docs.forter.com/network-uplift-mastercard-idci#send-order-api-request) Send Order API Request
   As with the [Checkout Integration](https://docs.forter.com/checkout-integration) for Fraud Management, send Forter the complete order details in the Order API to get real-time fraud decisions along with the issuer optimization for Mastercard. The request should be sent before calling the payment gateway to authorize funds (pre-auth flow). The full request and response data can be found in our [Order API](https://docs.forter.com/reference/order-v3 "Order API") reference documentation.
   
   Note that full card data is required for Issuer Optimization with Mastercard.

4. ### [Handle Order API Response](https://docs.forter.com/network-uplift-mastercard-idci#handle-order-api-response) Handle Order API Response
   | **Outcome** | **Call to Action** | **Order Response Fields** |
   | --- | --- | --- |
   | **Forter Approved**<br>Transaction is approved by Forter | Authorize | "> "forterDecision": "APPROVE"<br>To simulate this response, use [approve@forter.com](mailto:approve@forter.com "approve@forter.com") in the accountOwner object in the Order API request. |
   | **Forter Approved & Data Only was executed**<br>Transaction is approved by Forter and has data only recommendation | Authorize | "> "forterDecision": "APPROVE", "verificationMethod": {"status": "DATA_ONLY", ...}<br>To simulate this response, use [force_3ds_data_only@forter.com](mailto:force_3ds_data_only@forter.com "force_3ds_data_only@forter.com") in the accountOwner object in the Order API request. |
   | **Forter Declined**<br>Transaction is declined by Forter | Do not Authorize | "> "forterDecision": "DECLINE"<br>To simulate this response, use [decline@forter.com](mailto:decline@forter.com "decline@forter.com") in the accountOwner object in the Order API request. |
   | **Forter Did Not Review**<br>Transaction was not reviewed for a fraud decision | Act according to policy prior to Forter integration | "> "forterDecision": "NOT REVIEWED"<br>To simulate this response, use [notreviewed@forter.com](mailto:notreviewed@forter.com "notreviewed@forter.com") in the accountOwner object in the Order API request. |

5. ### [Post-purchase Updates](https://docs.forter.com/network-uplift-mastercard-idci#post-purchase-updates)  
   As you receive payment authentication updates, including 3DS results, and the order fulfillment status changes, it's important to keep Forter notified so that this information can be used in future decisions.
   
   We strongly recommend using a webhook to send notifications about payment authorization and disputes if your PSP is supported.

6. ### [Dispute Notifications](https://docs.forter.com/network-uplift-mastercard-idci#dispute-notifications)  
   Notifying Forter of disputes (also called claims, chargebacks, or fraud alerts) is extremely important because it enables Forter's system to learn and continually improve future decisions, tailoring our system to your company's needs. You can send these updates to Forter via a webhook from your PSP or via Forter's Dispute API endpoint.