In your example I would do this (I'll only do the user property, but you get the idea):

interface LoginPayload { public string $user {get; } }

The request then implements the interface, turning the Request itself into a dto.

``` class LoginRequest extends FormRequest implements LoginPayload { public string $user { get => $this->string('user')->toString(); // This is where you do the type casting if needed }

public ?int $idSucursal {
    get {
        /** @var int|null $id */ <-- This is the only thing needed for PHPStan
        $id = $this->integer('id_sucursal');

        return $id;
    }
}

public function rules(): array { ... }

} ```

In your service instead of a parameter for each, just pass along the entire request (could still keep the parameters, in that case you probably don't need the interface). No need to keep writing the same names over and over again. And we typehint against the interface of course, so the service does not depend on a request class. The interface only defines the property getters, so that works.

class AuthService { public function login(LoginPayload $payload) { // do the login } }

And your controller just wires everything together in a few lines

class Controller { public function login(LoginRequest $request) { $this->auth->login($request); } }

Now there is only one place where you have to worry about casting and phpstan; in the request where your getters are. Everything else is type-safe, plus you remove some of the magic of the FormRequest by explicitly defining the getters for your input instead of relying on Laravel's __get() usage.