Payment and fulfillment

A service order can have payment evidence from a provider and fulfillment events for products. Payment evidence records the provider event identifier, type, amount, occurrence time, provider reference and verification state. Fulfillment events record the product, quantity, event type, occurrence time and external event identifier. Both refer back to the parent order, so the team can compare the outside event with the local service history.

An authorization is different from a capture, refund or void. A picked item is different from a delivered one. These distinctions matter when a service manager asks whether an order was fulfilled and a finance reviewer asks whether a refund is supported. Keep the provider’s own event identifier so a duplicate message can be recognized.

• Payment evidence. The provider event and reference identify the source of each authorization, capture, refund or void.
• Fulfillment event. Product, quantity and event type show the actual external handling stage.
• Parent order. The linked order provides the service location, accepted scope and current status for comparison.

Finance Reviewer checks whether payment evidence is verified and corresponds to the intended order. Service Manager compares the fulfillment quantity with the order line and served scope. A delivered event can support a service review, but the service team still records actual served portions and time on the order.

Choose the payment provider connection and the exact source of verification. Agree how provider references map to orders and how rejected or duplicate events are surfaced. The provider remains the source for its own authorization and refund result. Decide whether an external fulfillment feed is used, which event identifier it supplies and who investigates a product or quantity mismatch.

A provider timeout does not establish a failed or completed refund on its own. Start with the recorded evidence and operation receipt before requesting another external action. Keep the original event and any later correction rather than changing a past amount to match today’s balance.

An accepted order is prepared and served at a venue. The payment provider sends a capture event for the order. Finance Reviewer matches its event identifier, amount and reference before marking the evidence verified. A later delivery event names the product and quantity associated with the order. Service Manager compares it with the served line. If a guest later receives an approved partial refund, a separate refund event and verification record explain the financial change without altering the original capture.

During rehearsal, send the same provider event twice. Confirm that the duplicate does not create a second local effect. Then test a delivery event with a quantity different from the served scope and leave it visible for review.

• Unverified Payment Evidence — Provider events requiring a finance check before use in reconciliation.
• Delivered Fulfillment Events — Delivered product quantities and their source event identifiers by order.

Use order to service for the local service sequence and receipt reconciliation for uncertain external outcomes.