Fix: Updates to OrderFullfilmentServices and box now clients, order views and checkout services
This commit is contained in:
@@ -52,6 +52,24 @@ class OrderPaymentResolutionService
|
||||
}
|
||||
}
|
||||
|
||||
/**
|
||||
* A deferred-capture payment (currently only cash-on-delivery — see
|
||||
* Payment\Events\PaymentDeferred's own docblock): no money has moved,
|
||||
* so unlike resolveCaptureOrAuthorization() this never calls
|
||||
* $writer->markPaid() — Order::paid stays false until staff explicitly
|
||||
* mark it received. But per OrderStatusFlow's own docblock, payment
|
||||
* method never affects the status SEQUENCE at all — a COD order has
|
||||
* nothing to "await" at checkout (no payment attempt happens), so
|
||||
* 'awaiting_payment' is simply the wrong first status for it. Reuses
|
||||
* the exact same advancePastAwaitingPayment() a capture uses, since
|
||||
* the status-sequence logic itself doesn't differ by payment method,
|
||||
* only whether `paid` also flips alongside it.
|
||||
*/
|
||||
public function resolveDeferredPayment(Order $order, string $causeClass): void
|
||||
{
|
||||
$this->advancePastAwaitingPayment($order, $causeClass);
|
||||
}
|
||||
|
||||
/**
|
||||
* Requires the refund Transaction row to already exist (Modules\Core\
|
||||
* Order\Listeners\RecordPaymentTransaction must run first — see
|
||||
|
||||
Reference in New Issue
Block a user