You can query it like shown below:
@YourXML.nodes('//Payments') T(c);BUT, you will notice that it returns only two rows, and not 3.
If you want to return all 3 rows, there is more work required. This would have been easy if SQL Server had a full implementation of the W3C specifications for XML (i.e., next sibling, previous sibling etc.)
Since the SQL XML implementation is rather limited, the simplest thing would be if you are able to get the data with only one payment in each Payments section, or if each payment was wrapped in another xml node. For example, like shown below:
Even without that, it can be done, but it is not pleasant.