> ## 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.

# One-shot authorize a payment (mandate-gated)



## OpenAPI

````yaml https://alyte-sandbox-f365cfb3ma-ey.a.run.app/openapi.public.json post /v1/payments
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: >-
      AP2 (Agent Payments Protocol, Google/FIDO) — Intent + Cart mandate
      purchase; the merchant-signed cart total is the spend cap, verified with
      real crypto (ES256 + cart_hash binding)
  - 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/payments:
    post:
      tags:
        - payments
      summary: One-shot authorize a payment (mandate-gated)
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                merchantId:
                  type: string
                  minLength: 1
                amountMinor:
                  type: integer
                  exclusiveMinimum: 0
                currency:
                  type: string
                  enum:
                    - EUR
                    - USD
                    - GBP
                scheme:
                  type: string
                  enum:
                    - visa
                    - mastercard
                    - amex
                geo:
                  type: string
                  minLength: 2
                  maxLength: 2
                instrumentToken:
                  type: string
                  minLength: 1
              required:
                - merchantId
                - amountMinor
                - currency
                - scheme
                - geo
                - instrumentToken
      responses:
        '200':
          description: Default Response
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````