Documenting different User Interface requirements to the same system functionality

I need to document different User Interface requirements to the same system functionality e.g.; the customer can pay their invoice via multiple channels including in-person, web, and IVR.  Theoretically I feel that these are alternate paths of the same use case.  How do I best organize the packages and use cases to accomodate?