<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/f6b15f02c3934c91a1d8ee13ee3de958&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/f6b15f02c3934c91a1d8ee13ee3de958-e92ed0a988e8b0ba.gif</thumbnail_url><duration>670.843</duration><title>Feedback on Nested Payments UI Design</title><description>This Loom provides design feedback on a payments card and filters/search UI for dense monthly payment data across multiple projects. The reviewer questions the nested card layout versus a table approach, notes that only a few projects would be visible at once on a large screen, and finds the two separate search fields confusing. They also flag unclear date filtering with no label, inconsistent status naming versus overdue and expecting payment, and confusion about red indicators and credit note calculations. Additional concerns include long project names that may not fit well in chips, unclear definitions such as indanning and VL payment, missing pagination, and the nesting not showing expected individual payouts.</description></oembed>