{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T15:48:56.209Z",
  "record_id": "VXI-EXT-PROCUREMENT-SQUARE-IDEMPOTENCY-KEY-CHANGED-PAYMENT-REQUEST-01-v1",
  "record_kind": "external_reference",
  "title": "Square retry identity and changed payment amounts",
  "system": "Square",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can a Square CreatePayment retry reuse its idempotency key with a changed payment amount?",
  "near_questions": [
    "What happens if a Square CreatePayment amount changes under the same key?",
    "Does a repeated successful Square payment request charge again?",
    "Are Square idempotency rules identical for every endpoint?",
    "How should an agent separate a retry from a new payment amendment?"
  ],
  "supported_claims": [
    {
      "claim": "Square documents that repeating a successful CreatePayment request with the same idempotency key returns the original successful response instead of taking another payment. Reusing that key with a changed request, such as a different amount, returns an error. Square notes that idempotency behavior can vary by API, so this rule must not be generalised to every endpoint.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Universal idempotency guarantees across all Square APIs",
    "The first request outcome and any separate buyer-approved amendment require transaction evidence.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Square documents that repeating a successful CreatePayment request with the same idempotency key returns the original successful response instead of taking another payment. Reusing that key with a changed request, such as a different amount, returns an error. Square notes that idempotency behavior can vary by API, so this rule must not be generalised to every endpoint.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Idempotency",
    "source_url": "https://developer.squareup.com/docs/build-basics/common-api-patterns/idempotency",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SQUARE-IDEMPOTENCY-KEY-CHANGED-PAYMENT-REQUEST-01-v1",
    "candidate_record_sha256": "d41d7ff97c987ef32f4805936d7e59368cc55c857cd400d0de570f58829bf62c",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "Square documents that repeating a successful CreatePayment request with the same idempotency key returns the original successful response instead of taking another payment. Reusing that key with a changed request, such as a different amount, returns an error. Square notes that idempotency behavior can vary by API, so this rule must not be generalised to every endpoint.",
    "required_buyer_context": "Original CreatePayment request and idempotency key; Original or recovered provider outcome; Proposed changed amount and renewed buyer authority. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-24",
    "claim_to_check": "Can a Square CreatePayment retry reuse its idempotency key with a changed payment amount?",
    "documented_statement": {
      "status": "documented",
      "statement": "Square documents that repeating a successful CreatePayment request with the same idempotency key returns the original successful response instead of taking another payment. Reusing that key with a changed request, such as a different amount, returns an error. Square notes that idempotency behavior can vary by API, so this rule must not be generalised to every endpoint.",
      "source_ids": [
        "square-idempotency"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Preserve the original request identity during recovery and treat a changed purchase as a separately authorised operation.",
      "source_ids": [
        "square-idempotency"
      ]
    },
    "buyer_evidence_required": [
      "Original CreatePayment request and idempotency key",
      "Original or recovered provider outcome",
      "Proposed changed amount and renewed buyer authority"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not rotate keys or change amounts merely to bypass a retry conflict before reconciling the first outcome."
    },
    "unknowns": "The first request outcome and any separate buyer-approved amendment require transaction evidence.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The first request outcome and any separate buyer-approved amendment require transaction evidence."
    },
    "evidence_sources": [
      {
        "source_id": "square-idempotency",
        "url": "https://developer.squareup.com/docs/build-basics/common-api-patterns/idempotency",
        "final_url": "https://developer.squareup.com/docs/build-basics/common-api-patterns/idempotency",
        "status": 200,
        "captured_at_utc": "2026-10-24T15:10:56.524Z",
        "sha256": "c1939389df32f580dab31de26c2821af99513a01d1bc0d8aaabc74a01a294bdc",
        "bytes": 190529,
        "title": "Idempotency",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "version_context": "Rolling official vendor documentation captured on 2026-10-24; API and account applicability require buyer verification.",
        "reviewed_sections": [
          "CreatePayment replay",
          "Changed parameters with reused idempotency key"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Avoid duplicate or unintended charges while resolving uncertain payment attempts.",
      "free": "Complete review, sources, practical questions and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Recheck the documented behavior, product version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Avoid duplicate or unintended charges while resolving uncertain payment attempts.",
    "refusal_conditions": [
      "Do not rotate keys or change amounts merely to bypass a retry conflict before reconciling the first outcome."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "payments",
    "classification_label": "Agent Payments, Authority & Transaction Evidence",
    "topic_id": "payments",
    "buyer_intent": "Avoid duplicate or unintended charges while resolving uncertain payment attempts.",
    "comparison_role": "supplementary_discovery"
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#square-idempotency-key-changed-payment-request",
  "machine_readable_record": "/varexis-index/records/square-idempotency-key-changed-payment-request.json"
}
