# Consume Payment Ecosystem Threat Intelligence
source: https://developer.mastercard.com/mastercard-threat-intelligence/tutorial/api-sandbox-guide/step-8/index.md

Payment Ecosystem Threat Intelligence gives you visibility into high-risk vulnerabilities that affect payment and e-commerce software. The API returns Common Vulnerabilities and Exposures (CVE) records with risk scores, severity labels, and lifecycle phases.

*** ** * ** ***

### When to Use It {#when-to-use-it}

You can use this feature to support these workflows:

* Prioritizing remediation for the most dangerous vulnerabilities.
* Assessing exposure across the software in your payment ecosystem.
* Adding vulnerability context to a security investigation.

*** ** * ** ***

### The Endpoint {#the-endpoint}

This feature uses one endpoint:

* `petiVulnerabilities` sends a GET request to `/exposures/vulnerabilities`.

You shape the results with query parameters for free-text search, filters, sorting, and pagination. Every parameter is optional.

*** ** * ** ***

### The Code {#the-code}

Add this method to your application. It searches for vulnerabilities that match a text query and prints the first five results:

```java
/** Payment Ecosystem Threat Intelligence: search high-risk vulnerabilities. */
static void runPaymentEcosystemThreatIntelligence(ApiClient apiClient) {
    System.out.println("== Payment Ecosystem Threat Intelligence ==");
    PaymentEcosystemThreatIntelligenceApi api = new PaymentEcosystemThreatIntelligenceApi(apiClient);
    try {
        // Parameters: searchText, severityLabel, lifecyclePhase, limit, offset, sortBy, sortDirection
        System.out.println(api.petiVulnerabilities("SQL injection", null, null, 5, 0, null, null));
    } catch (ApiException e) {
        printError(e);
    }
    System.out.println();
}
```

*** ** * ** ***

### Read the Response {#read-the-response}

The response is a `VulnerabilityPage`. It holds a list of records and a `page` object with the limit, offset, and total. Each record includes the CVE ID, the risk score, the severity label, and a description.

You assemble the full application, including the `printError` helper, in a later step.

*** ** * ** ***