Retrieves a single sub-merchant belonging to the authenticated partner.
Only merchants scoped to the authenticated partner are returned. Requests for unknown merchants or merchants outside that scope return 404.
This path currently overlaps with a legacy public merchant endpoint. To avoid ambiguous response shapes or fallback behavior, send the resolve-api-version header on every request. Use resolve-api-version: partner-v1 when you need the partner API response contract documented here.
Security
bearerAuth or basicAuth
- Mock serverhttps://docs.resolvepay.com/_mock/partners-api/openapi/merchants/{merchant_id}
- Sandbox serverhttps://app-sandbox.resolvepay.com/api/merchants/{merchant_id}
curl -i -X GET \
https://docs.resolvepay.com/_mock/partners-api/openapi/merchants/mrc_1234567890abcdef \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'A merchant object.
Resolve merchant identifier (lowercase alphanumeric).
For partner API create flows, ID assignment behavior is:
- Resolve may derive a human-friendly alphanumeric candidate from merchant naming fields.
- If the candidate collides with an existing merchant ID, Resolve generates a random lowercase alphanumeric ID.
Example:"mrc_1234567890abcdef"
Partner-supplied identifier for this merchant in your own system. null when never set.
Example:"partner-crm-12345"
Response
{ "id": "mrc_1234567890abcdef", "reference_id": "partner-crm-12345", "legal_business_name": "Acme Supply LLC", "dba_name": "Acme Industrial", "business_address": { "line1": "100 Main St", "city": "Austin", "state": "TX", "postal_code": "78701", "country": "US" }, "business_email": "ops@acmesupply.com", "business_phone": "+15125550123", "entity_type": "llc", "formation_state": "TX", "underwriting_status": "pending", "seller_amount_approved": 0, "active_subscription": { "id": "sub_1234567890abcdef", "tier": "trial" }, "metadata": { "partner_reference": "mt-merchant-1029" }, "created_at": "2026-02-26T10:00:00.000Z", "updated_at": "2026-02-26T10:00:00.000Z" }