Mandatory MID Header Requirements

To enhance transaction traceability and platform security, we are introducing a mandatoryMID (Merchant ID) header for customer-level API calls.

---

🚨 MID Header Policy

📌 Previous Behavior

• Only Merchant-level and Sub-merchant-level accounts were required to include the MID header in API requests.

🆕 New Behavior (Effective Soon)

The MID header is now required for all levels, including:

• Merchant
• Sub-merchant
• Customer (new requirement)

---

🔧 API Changes

🔹 Header Requirement

🔒 Enhanced Validation

• Real-time validation of the MID header for all request types.
• Requests without a valid MID will be automatically rejected.
• Enables stronger audit logging and transaction tracking.

---

✅ What Remains Unchanged

• API Endpoints: URLs and HTTP methods are unchanged.
• Authentication: Existing auth methods continue to work as-is.
• Response Format: No changes to the structure or fields in API responses.

---

🛠️ Required Action for Integrators

All integrators must:

• Add the MID header to every API request.
• Example:
  HTTP

  POST /api/v1/customer/transaction
  Headers:
    Authorization: Bearer <your-token>
    MID: <your-merchant-id>

---

⚠️ Error Handling

After enforcement begins, requests without MID header will return a 400 Bad Request status with:

{
  "error": "Missing required MID header",
  "code": "MISSING_MID_HEADER",
  "message": "All API requests must include a valid MID (Merchant ID) header"
}

Error Response Fields:

• error - Short, human-readable error summary
• code - Machine-readable error identifier for programmatic handling
• message - Detailed explanation of the error and resolution steps

---

🗓️ Timeline

⚠️

After enforcement begins, any customer-level request missing the MID header will be rejected.

---

🧑‍💻 Support

Need help?
Reach out to our support team via your existing communication channels for technical assistance or integration questions.