Web-based verifications are orders that are instructed towards a bank via a website (either from a bank or other party). We use several techniques to make sure customer behaviour is mimicked besides direct HTTP calling towards endpoints. In simpler words, if there is a button to push, we rather push a button than execute a lower URL.On this device a customer journey executes fully automated like a real user.
As shown in above diagram, the steps 1 till 5 generate availabilty reports. On every step we can store the actual screen as shown to a customer. Where needed we utilize the accounts to create the real transactions and monitor the end-to-end flow.
Several parties can do the monitoring of websites. Although those parties can give valuable insight on performance and availability we noticed that this is only scratching the surface as the below picture shows.
has means to actually log in and create actual transactions. These transactions are signed after creation after which (if the website allows) the status can also be scrapped.