> ## Documentation Index > Fetch the complete documentation index at: https://docs.dimepayments.com/llms.txt > Use this file to discover all available pages before exploring further. # Update a specific Merchant's Details > Update a Merchant's details. ## OpenAPI ````yaml https://app.dimepayments.com/openapi.yaml patch /api/merchant/update openapi: 3.0.3 info: title: Dime Payments API Documentation description: >- A simple, basic API for managing Merchants through Dime Payments. JSON based REST API version: 1.0.0 servers: - url: https://app.dimepayments.com security: - default: [] tags: - name: Merchant management description: '' - name: Transaction management description: >- APIs for managing transactions. Depending on API KEY permissions, one should be able to charge credit cards, ACH, Google/Apple Pay wallets along with other functions. - name: Addresses description: |- APIs for managing customer addresses - name: Customer management description: >- APIs for managing customers. Depending on API KEY permissions, one should be able to list, create, update, and delete customers along with several other customer specific requests. - name: Deposit management description: '' - name: Invoice management description: >- APIs for managing invoices. Depending on API KEY permissions, one should be able to list, create, update, delete, and send invoices, manage their line items, and manage recurring-invoice schedules. Every request is scoped to a single Merchant via the required `data.sid`. - name: Payment Method management description: >- APIs for managing payment methods associated with customers. Depending on API KEY permissions, one should be able to list, show, create, update, and delete payment methods. - name: Recurring Payments management description: >- APIs for managing recurring payments. Depending on API KEY permissions, one should be able to create, edit, pause, cancel along with other functions. - name: Zapier description: >- APIs for use through Zapier. Depending on API KEY permissions, one should be able to see customers and transactions data. paths: /api/merchant/update: patch: tags: - Merchant management summary: Update a specific Merchant's Details description: Update a Merchant's details. operationId: updateASpecificMerchantsDetails parameters: [] requestBody: required: false content: application/json: schema: type: object properties: data: type: object description: '' example: [] properties: sid: type: integer description: The SID of the Merchant to update. example: 99 slug: type: string description: Must be unique and HTML URL Compliant. example: acme-inc name: type: string description: >- The name of the Merchant. Avoid special characters like \ or '. example: Acme Inc mcc: type: integer description: Must be 4 digits and pre-approved by Dime Payments. example: 8661 processor_config_one: type: string description: >- Must be on approved list, this is provided by your Dime Payments Rep. example: Tier1 website: type: string description: Must be a valid full URL. example: https://acme-inc.com addr1: type: string description: Address line 1 of the Merchant. example: 123 4th Street addr2: type: string description: optional Address line 2 of the Merchant. example: Suite 5 nullable: true city: type: string description: The city of the Merchant. example: Alpharetta state: type: string description: The state abbreviation of teh Merchant. example: GA zip: type: integer description: The 5-digit zip of the Merchant. example: 30009 phone: type: string description: The main phone number for the Merchant in e164 format. example: '+177012345678' primary_phone: type: string description: >- The phone of the main contact for the Merchant in e164 format. example: '+140412345678' primary_name: type: string description: The full name of the main contact for the Merchant. example: John Doe primary_email: type: string description: The email of the main contact for the Merchant. example: john@acme.com industry: type: string description: >- Must be a supported Industry name, contact Dime Payments Rep for values. example: Church required: - sid - slug - name - mcc - processor_config_one - website - addr1 - city - state - zip - phone - primary_phone - primary_name - primary_email - industry responses: '200': description: '' content: application/json: schema: type: object example: data: name: Dime Payments sid: '00001' mcc: '8999' slug: pay pub_api_key: pkapi_prod_B5n2hQhy6uAp1rLjqs processor_mid: '650000012366624' active: true active_at: null g_pay: false a_pay: false pci_compliance: true website: https://dimepayments.com addr1: 53 S. Main St addr2: '' city: Alpharetta state: GA zip: '30009' phone: '4049064975' primary_phone: '4049064975' primary_email: ben@dimepayments.com primary_name: Ben Habeck properties: data: type: object properties: name: type: string example: Dime Payments description: The name of the merchant. sid: type: string example: '00001' description: The unique Dime Payments ID for the merchant. mcc: type: string example: '8999' description: The MCC Code assigned to the merchant. slug: type: string example: pay description: >- The unique address for the merchant's pay page. i.e. https://dimepayments.com/{slug}. pub_api_key: type: string example: pkapi_prod_B5n2hQhy6uAp1rLjqs description: The public API key for the gateway's tokenizer. processor_mid: type: string example: '650000012366624' active: type: boolean example: true description: If this merchant is active on Dime Payments. active_at: type: string example: null description: date The date the merchant was made active. g_pay: type: boolean example: false description: If this merchant is active on Google Pay. a_pay: type: boolean example: false description: If this merchant is active on Apple Pay. pci_compliance: type: boolean example: true description: >- If this merchant has an active AoC on file with Dime Payments. website: type: string example: https://dimepayments.com description: The merchant's website. addr1: type: string example: 53 S. Main St description: The merchant's first address line. addr2: type: string example: '' description: The merchant's second address line (optional). city: type: string example: Alpharetta description: The merchant's city. state: type: string example: GA description: The merchant's state. zip: type: string example: '30009' description: The merchant's zip code. phone: type: string example: '4049064975' description: The merchant's phone number. primary_phone: type: string example: '4049064975' description: The merchant's primary contact phone number. primary_email: type: string example: ben@dimepayments.com description: The merchant's primary email address. primary_name: type: string example: Ben Habeck description: The merchant's primary full name. '400': description: '' content: application/json: schema: oneOf: - description: Failed validation type: object example: errors: data.phone: - The data.phone field is required. properties: errors: type: object properties: data.phone: type: array example: - The data.phone field is required. items: type: string - description: Merchant not created type: object example: data: message: 'Something went wrong: contact Dime Payments Rep' properties: data: type: object properties: message: type: string example: 'Something went wrong: contact Dime Payments Rep' '401': description: Bad API Key Permission content: application/json: schema: type: object example: message: Permission Denied. properties: message: type: string example: Permission Denied. components: securitySchemes: default: type: http scheme: bearer description: >- You can retrieve your token by visiting your dashboard and clicking Generate API token under your profile in top right. ````