Order Lifecycle Management
As an Admin, you want to have the concept of an order for single and multi payments.
Key Features:
Create an orders table with columns: id, date, order_status (active, failed, cancelled), order_type (payment_plan, single_payment), cart, initial_transaction_id, event_id, partner_id, group_id, member_idCreate an order id when first transaction occurs for payment plan reservation and single paymentAdd order_id references to transactions, reservations, invoices, and payment_attempts tablesPass Order Id to Adyen in metadata as merchant order referenceBehavior:
An order is created whenever a Manual Reservation, Ticket purchase, Refund, Account credit, Autopay, Manual invoice payment, BOE Iframe, or Marketplace payment is performed.An order_id must be created for all these actions.The order_status lifecycle includes active, failed, and cancelled states.Acceptance Criteria:
Create an orders table with the specified columns.Create an order id when first transaction occurs for payment plan reservation and single payment.Add order_id references to transactions, reservations, invoices, and payment_attempts tables.Pass Order Id to Adyen in metadata as merchant order reference.Notes:
The current behavior does not match the acceptance criteria, which state that an order_id must be created whenever a Manual Reservation, Ticket purchase, Refund, Account credit, Autopay, Manual invoice payment, BOE Iframe, or Marketplace payment is performed.An order_id is only created when the first payment is made through BOE or marketplace payments, but no order_id is generated for refunds, reservations, account credits, manual invoice payments, autopay or other actions listed in the AC.