Loop is a mobility and payments platform offering commuter transport booking and related cashless payment or driver-income tools.
A meaningful transaction was taken beyond a landing page into booking and invoicing. The remaining untested fulfilment steps are important but do not erase the verified live service. Keep Tier 2: live booking/invoicing workflow verified; Tier 3 unsupported without deeper operational, integration and governance evidence.
The reviewer completed a website booking, received a PDF invoice with transparent pricing and a payment link, but did not complete payment or take the ride. WhatsApp booking and other payment features were not independently exercised.
Loop's current public site and booking portal remain active and market the same booking and transport services.
Payment, ride fulfilment and WhatsApp workflow not completed in the review.
No enterprise security or API review.
These images formed part of the evidence pack considered during verification. Full-standard records retain the contributor's factual caption for each screenshot.
The verified result is the official public checkpoint record. For earlier-standard reviews, these findings may have been reconstructed from preserved evidence during Sandbox Africa’s 2026 audit; they are not presented as if the contributor originally completed a structured worksheet. Contributor-submitted checkpoint wording is shown only where explicit public reviewer attribution has been enabled.
Checking for dead links, infinite loading screens, or "Coming Soon" landing pages masquerading as live products.
The reviewer used the live Loop website booking interface.
Can a user or enterprise actually sign up, or is it gated behind broken "Contact Sales" forms?
A booking could be initiated with basic contact details without an upfront card barrier.
Does the application actually do what it claims to do? (e.g. a payment gateway completing a test transaction, a logistics app's routing engine working.)
A route booking produced a PDF invoice and payment link, but payment and ride fulfilment were not completed.
Assessing the logical flow, responsiveness, and basic accessibility of the platform.
The tested booking flow was straightforward and pricing was transparently presented.
Load speeds, uptime reliability, and basic stress responses.
The booking flow completed successfully during review, but no controlled uptime/load test was performed.
Availability, clarity, and functionality of API documentation and webhooks.
WhatsApp/Chat-to-Pay capabilities were not independently exercised and no enterprise API review was completed.
SSL certification, basic encryption standards, and data handling transparency.
The transactional web baseline was available, but enterprise security controls were outside the review scope.
Claiming verifies company ownership and enables a response or additional evidence. It does not permit editing of the independent review.
