{{-- The customer's own settings. It was one column 768 pixels wide inside a 1240-pixel shell — a third of the window empty beside it — holding everything a customer might ever change: the company address, the password, two-factor, the signed-in devices, the branding, the contract and the button that closes the account. Two thousand pixels of scroll, and the way to a particular thing was knowing how far down it lived. Four tabs, by what somebody came to do. Inside a tab the short cards sit side by side instead of each taking a full row to hold three lines. The choice is in the query string (see the #[Url] attribute on the component), so a reload, a bookmark and the back button all land where they were. --}}
{{ __('settings.eyebrow') }}
{{ __('settings.subtitle') }}
{{ __('settings.twofa_sub') }}
{{ __('settings.twofa_codes_title') }}
{{ __('settings.twofa_codes_hint') }}
{{ __('settings.cancel_scheduled_title') }}
{{ __('settings.cancel_scheduled_body', ['date' => $instance?->service_ends_at?->local()->isoFormat('LL')]) }}
{{ __('settings.package_active', ['plan' => $instance ? __('billing.plan.'.$instance->plan) : '—']) }}
{{ __('settings.no_package') }}
@endif {{-- The fourteen-day right of withdrawal. Shown only where it exists: a business customer has none and never sees this block — and the server refuses them again in Settings::withdraw(), because a card that is not rendered has never stopped anybody who can post to /livewire/update. Separate from the cancellation above it, and not a variant of it. A cancellation ends a contract that was validly concluded and keeps the term the customer paid for; a withdrawal unwinds the contract itself, ends the service the same day and sends the money back. --}} @if ($withdrawal->applies && $withdrawal->open){{ __('withdrawal.card_title') }}
{{ __('withdrawal.card_sub', [ 'date' => $withdrawal->endsAt->local()->isoFormat('LL'), 'days' => $withdrawal->daysLeft(), ]) }}
{{ __('settings.close_account_sub') }}
{{ __('settings.lifecycle_title') }}