Checkout

Overview

AiFi’s checkout system offers a seamless, cashierless shopping experience where customer purchases are tracked automatically. Upon exiting the store, AiFi finalizes the transaction and notifies the retailer to initiate the payment process. Additionally, AiFi provides a mechanism for customers to contest receipts if discrepancies are found, ensuring transparency and trust in the shopping experience.

Dependencies

1. OASIS Admin API: Required for processing checkout, generating receipts, and handling receipt contests.
2. Payment System Integration: The retailer’s system must handle the actual payment request and processing after receiving the total amount from AiFi.
3. AiFi Console: The console is used for managing and reviewing contested receipts.

Prerequisites

Before utilizing the checkout and contest receipt systems, the following must be in place:

1. Check-in Process: Customers should be checked in either via a QR code or credit card at the point of entry, which links them to their shopping session.
2. Integration with Payment System: The retailer's app must handle payment requests once the checkout process is completed by AiFi.
3. Contest Functionality (Optional): Ensure that your app provides a feature for customers to contest receipts or offers alternative feedback options (such as support email) if this feature isn’t implemented yet.

Flow

Checkout Flow

1. Monitoring Purchases: AiFi’s OASIS system monitors and tracks the products customers pick up during their shopping session.
2. Customer Leaves the Store: When the customer exits, AiFi sends the Customer left a store webhook, notifying the system that the customer has finished shopping.
3. Finalizing Checkout:
   • If all events are processed, AiFi sends the Checkout webhook with the final product list and the total transaction amount.
   • If events are still pending, the system sends a Checkout webhook with status: draft. Customers are notified that their order is being processed.
4. Payment Request: Retailers handle the payment processing by creating an order in their app and requesting payment based on the amount calculated by AiFi.
5. Order Completion: Once the payment is successful, the transaction is finalized, and the customer receives their receipt.

Contest a Receipt Flow

1. Receipt Review: Customers can review their receipt in the app and flag any discrepancies in product items, quantities, or prices.
2. Submit Contest: If a customer contests the receipt, the app should call the Admin API – Contests -> Create a contest for order API, linking the contest to the original orderId.
3. Review Process: The retailer can review and manage the contested order in the AiFi Console. The customer’s receipt status is updated to Pending review until the issue is resolved.

Options

• Cart Mutator (Optional): Retailers can configure a webhook for taxes, discounts, or other price modifications before the final checkout.
• Receipt Contesting (Optional): The app can include a feature to allow customers to contest receipts directly or provide a support email for feedback.

Important Considerations

1. Receipt Finalization: Invalidate the customer's QR code when the checkout status moves to Draft, not when the order is submitted for payment.
2. Contesting a Receipt: If the contest feature is enabled, ensure the app limits the contest message to 500 characters to prevent API errors.
3. Returning to the Store: Customers can generate a new QR code for future shopping trips even if they haven’t yet received a receipt for their previous session.