2026-07-19 03:35:16 +03:00
|
|
|
<?php
|
|
|
|
|
|
2026-09-10 00:14:42 +03:00
|
|
|
use Modules\Core\Payment\Pipelines\Cart\ApplyPaymentMethodFee;
|
2026-07-19 03:35:16 +03:00
|
|
|
|
|
|
|
|
return [
|
|
|
|
|
/*
|
|
|
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Lunar cart pipeline additions
|
|
|
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
|
| Appended to config('lunar.cart.pipelines.cart') after ApplyShipping so
|
2026-09-10 00:14:42 +03:00
|
|
|
| the selected payment method's own fee (if any) is added to the
|
|
|
|
|
| shipping total before the final Calculate step sums everything up.
|
2026-07-19 03:35:16 +03:00
|
|
|
|
|
2026-09-09 00:48:09 +03:00
|
|
|
| This is the one thing left in this file — everything about WHICH
|
|
|
|
|
| payment methods exist (driver mapping, capture_mode, statuses) moved
|
|
|
|
|
| onto Modules\Core\Payment\Models\PaymentMethod's own row (see
|
|
|
|
|
| docs/payments.md): that's a per-instance, merchant decision, not a
|
|
|
|
|
| store-wide-singular setting, so it never belonged in config at all.
|
|
|
|
|
| This pipeline registration IS genuinely cross-cutting — every store
|
|
|
|
|
| using this driver gets the same cart-pipeline wiring, regardless of
|
|
|
|
|
| how many payment methods it configures.
|
|
|
|
|
|
|
2026-07-19 03:35:16 +03:00
|
|
|
*/
|
|
|
|
|
'cart_pipeline' => [
|
2026-09-10 00:14:42 +03:00
|
|
|
ApplyPaymentMethodFee::class,
|
2026-07-19 03:35:16 +03:00
|
|
|
],
|
|
|
|
|
];
|