> ## Documentation Index
> Fetch the complete documentation index at: https://alyte.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Update a shop's settings — discovery opt-in, shop image, embed origins, and purchase-time bank authentication (purchaseAuthentication, approvalWindowSeconds) (API token, merchant:write)



## OpenAPI

````yaml https://app.alytegen.com/openapi.public.json patch /v1/integration/merchants/{id}
openapi: 3.1.0
info:
  title: Alyte API
  description: >-
    Secure agentic checkout for live-events ticketing. REST is the canonical
    surface; MCP/A2A are adapters over the same orchestrator.
  version: 1.0.0
servers:
  - url: /
    description: this instance
security:
  - bearerAuth: []
tags:
  - name: catalog
    description: Shop / event / tier discovery
  - name: ticketing
    description: 'The purchase spine: quote → reserve → confirm'
  - name: payments
    description: One-shot authorize + result reads
  - name: acp
    description: Agentic Commerce Protocol — checkout sessions (OpenAI ACP conformance)
  - name: vic
    description: >-
      Visa Intelligent Commerce — mandate-governed purchase-initiate (the VIC
      mandate is the spend authority)
  - name: signed-mandate
    description: >-
      Network signed-mandate (VIC / Mastercard Agent Pay shape) — a detached
      network signature over the mandate artefact is verified with real crypto
      before the spend authority is granted
  - name: ap2
    description: Legacy AP2 purchase — unsupported pending verified checkout authorization
  - name: buyer
    description: >-
      Buyer surface — magic-link identity, bring/create agents, card capture
      (PSP iframe), and mandates whose scope is locked server-side to the shop
      the session is for
  - name: discovery
    description: >-
      PUBLIC discovery (no auth) — the opt-in shop window + the ACP product
      feed. Only shops that flipped `discoverable` appear; everything else 404s.
  - name: protocols
    description: Protocol adapters (MCP / A2A) over the same orchestrator as REST
  - name: integration
    description: >-
      Server-to-server merchant integration (API token) — e.g. minting buyer
      sessions for users the MERCHANT'S own auth has already verified
paths:
  /v1/integration/merchants/{id}:
    patch:
      tags:
        - integration
      summary: >-
        Update a shop's settings — discovery opt-in, shop image, embed origins,
        and purchase-time bank authentication (purchaseAuthentication,
        approvalWindowSeconds) (API token, merchant:write)
      parameters:
        - schema:
            type: string
          in: path
          name: id
          required: true
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              additionalProperties: false
              properties:
                discoverable:
                  type: boolean
                imageUrl:
                  type:
                    - string
                    - 'null'
                embedOrigin:
                  type:
                    - string
                    - 'null'
                  description: >-
                    Up to three bare https origins (no path), space- or
                    comma-separated, e.g. "https://fieldpass.shop
                    https://staging.fieldpass.shop"; http only for localhost.
                    Drives the frame-ancestors allowlist, the postMessage
                    targetOrigin and buyer-API CORS. null clears them.
                purchaseAuthentication:
                  type: string
                  enum:
                    - off_session
                    - buyer_present
                  description: >-
                    Whether agent purchases run off_session (default) or require
                    buyer_present bank authentication at purchase. buyer_present
                    is refused with 409 purchase_authentication_unsupported when
                    the shop's default PSP cannot run the flow.
                approvalWindowSeconds:
                  type: integer
                  minimum: 300
                  maximum: 1800
                  description: >-
                    How long (seconds, 300–1800, default 600) a hold waits for
                    the buyer under buyer_present.
      responses:
        '200':
          description: Default Response
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
                properties:
                  merchant:
                    type: object
                    additionalProperties: true
                    properties:
                      id:
                        type: string
                      name:
                        type: string
                      geo:
                        type: string
                      currency:
                        type: string
                      discoverable:
                        type: boolean
                      imageUrl:
                        type: string
                      purchaseAuthentication:
                        type: string
                        enum:
                          - off_session
                          - buyer_present
                      approvalWindowSeconds:
                        type: integer
                        minimum: 300
                        maximum: 1800
                    required:
                      - id
                      - name
                required:
                  - merchant
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.