My refund agent looked smart until it lied about Shopify, Stripe, and Zendesk 3 different ways

Описание и применение

LLM‑поддержка неверно сообщала о завершении возвратов после вызова API Shopify, Stripe и Zendesk. Добавление проверки статуса транзакции и использование ключей идемпотентности Stripe исправило проблему.

Задача

An LLM‑powered support agent incorrectly reported refunds as complete after making API calls to Shopify, Stripe, and Zendesk, leading to customer misinformation and operational failures.

Результат

The agent now accurately reports refund status, reducing customer confusion and preventing financial discrepancies.

Рабочий процесс

• Read Zendesk ticket
• Find Shopify order
• Call Shopify refundCreate
• Verify refund transaction status via getOrderTransactions
• If success, proceed; else handle failure
• Generate idempotency key
• Call Stripe refunds.create with key
• Persist key before call
• Handle retries based on persisted key
• Update Zendesk ticket with verified status
• Reply to customer

Доказательства

Shopify’s docs are explicit: the existence of a Refund object does not guarantee the financial transaction completed.

Источник

Stripe stores the first result for a given idempotency key and returns the same status code and body on retries, including 500 errors.

Источник