A bot payment flow creates an invoice, redirects to a provider, confirms the webhook, and releases the result only after server-side status verification. An “already paid” screen is not evidence of payment.

Scope includes the chosen provider, idempotency key, order state, successful, cancelled, and pending outcomes, and receipts or links where supported. The bot stores no card data. Acceptance in a test environment ensures two clicks create one business order, forged webhooks fail, late confirmation updates status, and amounts match server records. Refunds and partial payments are included only when explicit.