Passing two lists to a view is really easy. You can use the ViewBag or you can simply create a custom or dynamic model having the two list. That's it.
But the question is how you intend to traverse these two. As BillWoodruff asked, you probably have some relations between these two. And at that point I wouldn't pass two lists to the view - only if you want to show all the data in your repository on one web page (I doubt you want this). If by any chance you want to filter the data in the view, and use the relation you might have, you have introduced a huge overhead - this is not the concern of the view! It is agains MVC concepts. You have to consider also, that EF for example is returning IEnumerables, which are not enumerated until you traverse them. Making lists out of them means that you read all the data into memory. This is a huge mistake in a production scenario. Pass lists only if you really need to, or if they are short ones in every case.
I don't know what you repository is. I would recommend using EF and the navigator possibilities which it has, sou you can simply manage and navigate trough the relations between the entities of your model. And in the same time you can make use of the deferred execution.
[Update based on the chat below]
There is a method you can use to traverse two IEnumerables in parallel. You can evaluate it and adapt to your needs.
IEnumerable orders = new int[] {1,2,3,4};
IEnumerable payments = new int[] {30,31,32,33,34,35};
var oe = (IEnumerator)orders.GetEnumerator();
var pe = (IEnumerator)payments.GetEnumerator();
bool no, np;
while((no = oe.MoveNext()) | (np = pe.MoveNext()))
{
Console.WriteLine(String.Format("<tr><td>{0}</td><td>{1}</td></tr>",
no ? ((int)oe.Current).ToString() : " ",
np ? ((int)pe.Current).ToString() : " "
));
}