Allow Paying with DTO or Entity Classes Instead of Only Eloquent Models

[realpvz]

Is your feature request related to a problem? Please describe.
Currently, the pay() and related wallet methods only accept Eloquent models. This creates a limitation in projects that follow DDD or service-based architecture, where we often work with DTOs or custom entities instead of directly using Eloquent.
I'm frustrated that I can't pass my ReserveDTO or ReserveEntity to the wallet and must instead tightly couple the code to Eloquent, which breaks separation of concerns.

Describe the solution you'd like
It would be great if the wallet could accept a more flexible payer object – either an interface-based solution or support for custom identifiers (like UUIDs or strings) that aren’t strictly tied to an Eloquent model.
This way, developers could implement their own payer object and still benefit from Bavix Wallet's features.

Describe alternatives you've considered

Wrapping the DTO into a temporary Eloquent model (adds unnecessary complexity and risk).

Duplicating logic in a service class just to bridge between Eloquent and DTO.

Using a separate wallet implementation, which I'd prefer to avoid because Bavix Wallet already does 90% of what I need.

Additional context
In our use case, we use DTOs throughout the domain layer, and only at the boundaries do we touch Eloquent. Supporting DTOs or at least allowing custom payloads would make this package usable in more modern, decoupled Laravel architectures.

[rez1dent3]

Hello. The architecture of the package is built on Laravel Eloquent events. Refusing them would be equivalent to rewriting the entire package and would not meet your expectations.

Why it is done this way is described here: #562, laravel/framework#44608.

The package itself tries to optimize sections of code (described here).

---

If we talk about DTO directly, then inside internal everything works through data transfer objects, yes.

laravel-wallet/src/Internal/Dto/ItemDto.php

Line 11 in 3adf027

final readonly class ItemDto implements ItemDtoInterface

But you can't just use DTO and save it, because you need an account to transfer funds to. Of course, you can do it this way https://bavix.github.io/laravel-wallet/guide/purchases/receiving.html, but in this case the refund cannot, and most likely will, work incorrectly.

[rez1dent3]

@realpvz Oh, I forgot to say. If you have a real proposal that will work, you can formalize the concept as a PR. I'll look at it and if we don't break anything along the way, we can accept it.

[github-actions]

This issue is stale because it has been open 7 days with no activity.