I don't think this is a good solution because it will be hard to scale and maintain for multiple payment providers. However, I'm inclined to say ship it but with a big comment saying not to expand this code in the future.

Instead, a scalable solution is to change the [SellerProductBoku field](https://github.com/JaredKerim-Mozilla/solitude/blob/1000375/lib/sellers/models.py#L130) and the [SellerProductBango field](https://github.com/JaredKerim-Mozilla/solitude/blob/1000375/lib/sellers/models.py#L112) to be ``ManyToOne`` relations. That will automatically give the model a set of provider products. With that, you can build this list simply with ``for provider_product in self.provider_product_set.all(): provider_product.seller.uuid...``. However, such a change may break some existing Bango API stuff. Maybe file a bug to fix the model properly?