{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T15:12:44.585Z",
  "record_id": "VXI-EXT-PROCUREMENT-ADYEN-IDEMPOTENCY-REGIONAL-BOUNDARY-01-v1",
  "record_kind": "external_reference",
  "title": "Adyen: Idempotency does not span regional endpoints",
  "system": "Adyen",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does reusing an Adyen idempotency key prevent duplicate payments across regional endpoints?",
  "near_questions": [
    "Can an Adyen regional failover duplicate a payment?",
    "What account scope applies to an idempotency key?",
    "Does the same key deduplicate calls in two Adyen regions?",
    "What should be reconciled before retrying on another endpoint?",
    "Can an agent equate payment failover with exactly-once execution?",
    "Which region and request reference belong in recovery evidence?"
  ],
  "supported_claims": [
    {
      "claim": "Adyen documents company-account scope for idempotency keys but says requests sent to multiple regional endpoints are not deduplicated across regions. Regional failover therefore needs reconciliation of the original attempt; the same key alone is not a cross-region exactly-once guarantee.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Permission to charge, live transaction reconciliation or guaranteed failover safety",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables"
  ],
  "public_summary": "Adyen documents company-account scope for idempotency keys but says requests sent to multiple regional endpoints are not deduplicated across regions. Regional failover therefore needs reconciliation of the original attempt; the same key alone is not a cross-region exactly-once guarantee.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Adyen API idempotency",
    "source_url": "https://docs.adyen.com/development-resources/api-idempotency/",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-ADYEN-IDEMPOTENCY-REGIONAL-BOUNDARY-01-v1",
    "candidate_record_sha256": "b3da805184d653fc9e0b0337762125148a9ae3dce4517e642488fd23ed97a1ff",
    "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": "Adyen documents company-account scope for idempotency keys but says requests sent to multiple regional endpoints are not deduplicated across regions. Regional failover therefore needs reconciliation of the original attempt; the same key alone is not a cross-region exactly-once guarantee.",
    "required_buyer_context": "The company account, endpoint region and request key. The original attempt and provider payment reference. Regional recovery policy and verified transaction outcome. 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-18",
    "claim_to_check": "Does reusing an Adyen idempotency key prevent duplicate payments across regional endpoints?",
    "documented_statement": {
      "status": "documented",
      "statement": "Adyen documents company-account scope for idempotency keys but says requests sent to multiple regional endpoints are not deduplicated across regions. Regional failover therefore needs reconciliation of the original attempt; the same key alone is not a cross-region exactly-once guarantee.",
      "source_ids": [
        "adyen-retry"
      ]
    },
    "buyer_evidence_required": [
      "The company account, endpoint region and request key.",
      "The original attempt and provider payment reference.",
      "Regional recovery policy and verified transaction outcome."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not assume cross-region deduplication when retrying an unresolved payment on a different endpoint."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "adyen-retry",
        "url": "https://docs.adyen.com/development-resources/api-idempotency/",
        "final_url": "https://docs.adyen.com/development-resources/api-idempotency/",
        "title": "Adyen API idempotency",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T15:02:03.171Z",
        "version_context": "Rolling official documentation captured on 2026-10-18; feature and deployment limits apply",
        "sha256": "744c87bb71780e94328e7f2a30eb4a140c8598368b4a9c1480ce29f26a1cb01b",
        "bytes": 261876,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Does reusing an Adyen idempotency key prevent duplicate payments across regional endpoints?"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "A payment platform owner must distinguish transport failover from safe recovery of an uncertain charge.",
      "free": "Complete review, practical questions, sources 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": "The company account, endpoint region and request key. The original attempt and provider payment reference. Regional recovery policy and verified transaction outcome."
    },
    "buyer_relevance": "A payment platform owner must distinguish transport failover from safe recovery of an uncertain charge.",
    "refusal_conditions": [
      "Do not assume cross-region deduplication when retrying an unresolved payment on a different endpoint."
    ]
  },
  "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": "A payment platform owner must distinguish transport failover from safe recovery of an uncertain charge.",
    "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#adyen-idempotency-regional-boundary",
  "machine_readable_record": "/varexis-index/records/adyen-idempotency-regional-boundary.json"
}
