[Py.1.1.b] As a Payee, I should be able to set my payment preferences via a Front-end - by choosing between using a unique smart contract for each consumer or a unique Smart contract #137
Description
This feature enables a consumer or payee to define, own, and manage a payment route that determines how funds should be received. A payment route represents a persistent configuration specifying the destination wallet, blockchain, currency, and optional constraints on how payments can be made. The route is owned and controlled by the consumer through their wallet and can be referenced by payers via a route identifier. Over time, the route can be extended with additional preferences such as allowed chains, accepted currencies, or forwarding logic, without requiring changes on the payer side.
Immediate scope
As a payer, I want to connect to the system using my own wallet so that my identity and permissions are cryptographically verified and no custodial account is required.
As a payer, I want to create a payment route by specifying a destination wallet address, a target blockchain, and a preferred currency
As a payer, I want to generate a unique route identifier for my payment route, so that I can share a single reference along the process instead of exposing raw wallet addresses or configuration details.
Later scope:
As a payer, I want to manage and update my payment routes link to a wallet through a front-end interface connected to my wallet.
As a payer, I want to define constraints on my payment route, such as which chains or currencies payers are allowed to use to control compatibility or sending chains.
As a payer, I want to optionally configure to use a single request forwarder per customer creating a unique route per customer