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

# Finish adding a card — re-verifies the capture session SERVER-SIDE with the provider and stores only the reference (scheme + last4), bound to this buyer



## OpenAPI

````yaml https://app.alytegen.com/openapi.public.json post /v1/buyer/instruments/confirm
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/buyer/instruments/confirm:
    post:
      tags:
        - buyer
      summary: >-
        Finish adding a card — re-verifies the capture session SERVER-SIDE with
        the provider and stores only the reference (scheme + last4), bound to
        this buyer
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                reference:
                  type: string
                  minLength: 1
                  maxLength: 1024
                setupIntentId:
                  type: string
                  minLength: 1
                  maxLength: 1024
                sessionResult:
                  type: string
                  minLength: 1
                  maxLength: 65536
      responses:
        '200':
          description: Default Response
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````

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