diff --git a/select/mid-management.md b/select/mid-management.md
index c6c2b41..98ca05e 100644
--- a/select/mid-management.md
+++ b/select/mid-management.md
@@ -325,6 +325,11 @@ These are the error codes for failed MID requests:
No MIDs were found at the card scheme
The MID provided as part of the MID request does not exist at the card network/scheme.
+
+
visa-invalid-input
+
Invalid input provided for Visa
+
One or more Visa-specific MID fields (e.g., VMID, VSID, Visa BIN, or Visa Acquiring MID) contain invalid values.
+
unexpected-error
Unexpected error
diff --git a/select/missing-transaction-requests.md b/select/missing-transaction-requests.md
index ada1309..90e93e0 100644
--- a/select/missing-transaction-requests.md
+++ b/select/missing-transaction-requests.md
@@ -212,7 +212,7 @@ fileName:missing-transaction-request-succeeded.json
}
```
-> **💡 Note:** The `matchScore` field is a calculated value between 0 and 100 that indicates how likely the returned transaction is the one you're looking for. A higher score means a stronger match based on the provided details.
+> **💡 Note:** See the [Match Score](#match-score) section below for details on how the `matchScore` field works and how to use it to select the best match.
### Example Webhook Payload (Failed)
@@ -245,6 +245,85 @@ fileName:missing-transaction-request-failed.json
---
+## Match Score
+
+When you submit a request for a missing transaction, the API evaluates the transaction details you provided against the data received from the card network. Each result includes a `matchScore` to quantify that relationship.
+
+
+
+*Screenshot: Matched transactions modal showing match score percentages for each result, helping identify the best match*
+
+- **Ranking**: Results are ranked in descending order, with the most likely match appearing first.
+- **Use Case**: This is particularly useful for automating the selection of a **Merchant ID** when multiple similar transactions are found for a single request.
+
+### Field Specification
+
+The `matchScore` field is included in the response object for each transaction result:
+
+
+
+
+
Property
+
Detail
+
+
+
+
+
Type
+
Number
+
+
+
Range
+
0–100
+
+
+
Description
+
A score indicating the likelihood that the returned transaction is the one you're looking for. A higher score means a stronger match based on the provided details.
+
+
+
+
+### Implementation Example
+
+In a scenario where a single request yields two potential matches, your integration can use the `matchScore` to decide which record to process based on the higher score.
+
+```json
+{
+ "result": {
+ "transactions": [
+ {
+ "amount": 10.17,
+ "date": "2026-02-09",
+ "networkStatus": "SUCCEED",
+ "merchantCity": "Goleta",
+ "merchantName": "Cake Corporation",
+ "matchScore": 98,
+ "type": "authorization",
+ "vmid": "14246971590487O",
+ "vsid": "27315004037738S",
+ "visaStoreName": "Jeannine's Baking Co."
+ },
+ {
+ "amount": 10.17,
+ "date": "2026-02-09",
+ "networkStatus": "SUCCEED",
+ "merchantCity": "Goleta",
+ "merchantName": "Cake Corporation",
+ "matchScore": 26,
+ "type": "settlement",
+ "vmid": "17132168905952S",
+ "vsid": "22361983717297O",
+ "visaStoreName": "Jeannine's Baking Co."
+ }
+ ]
+ }
+}
+```
+
+In this example, the authorization transaction with a score of **98** is the most likely match and should be prioritized over the settlement transaction scoring **26**.
+
+---
+
## Dashboard Support
The Missing Transaction Requests feature is fully available in the Fidel Dashboard, providing a user-friendly interface for creating, tracking, and managing your transaction lookup requests without writing code.
@@ -252,7 +331,7 @@ The Missing Transaction Requests feature is fully available in the Fidel Dashboa
### Video Walkthrough