I can imagine an app that automatically pays a supplier once an order arrives, even when the funds are spread across different networks. If the order is salted fish, Baster, my chubby orange cat, would happily inspect it. The box would barely reach the door before he approved delivery. A single fish would probably buy his professional opinion. The app could use one account across networks, read a price feed to calculate payment, and check delivery through a Web2 API, a connection to the courier’s system. Automation would release payment under agreed conditions, while privacy features would protect invoice details and customer information from public access. This is an app I’m imagining from the capabilities described in @RialoHQ design. Bringing them together could reduce the work of connecting separate services and make the whole payment process easier to run. To me, full integration is both Rialo advantage and its biggest security test. Incorrect delivery data could trigger payment. A permission error could expose private information. Retrying after an interruption could cause a duplicate payment. Testing needs to cover the entire process. If you used an app like this, which step would you still want to approve yourself?