Integrations

• Payment provider. Record provider-issued authorization, capture, refund and void receipts with their event identities, references, amounts and verification state.
• Delivery channel. Carry the customer and delivery references into the meal order and ticket, then attach actual fulfillment events with external event identity.
• Menu source. Align active products, standard prices, ingredients and approved recipe revisions with the operation’s menu maintenance process.

A local order status records the team’s work; a provider or delivery outcome requires the corresponding external evidence. Agree which system issues each identity, how duplicate events are recognized and who reviews an uncertain response. Operations Reviewer should inspect the receipt and linked effects before repeating a guarded action. Finance Reviewer verifies provider evidence when the action involves money. Use a pilot order to compare the same external reference across the order, ticket, event and receipt.