The biggest stores don't offer agent checkout. So Harbor runs where your users already shop. In your app, the Harbor SDK does this with nothing for them to install. Harbor for Chrome is the same device bridge for agents on the desktop web: the user's own signed-in Chrome, where Harbor prepares the order, checks their limits, and they tap Place order.
In Harbor Approve, the user signs in at Target, Best Buy or The Home Depot on the store's own pages. In your app the SDK needs no install; on the desktop web this pairs the extension.
You create a checkout with the product link. It comes back waiting on_device.
In the user's browser, the extension opens the product, adds it to the cart and reads the real total. Harbor checks their limits.
The extension highlights the button. The user taps it, and you get checkout.completed.
Orders land in the user's own account at the store, with the address, payment and loyalty they already set up. Returns work the way they always do.
Supported
Supported
Supported
Tell us where your users shop.
It highlights the button. The final tap is always the user's.
It never fills sign-in forms or reads what the user types.
No CAPTCHA solving, no disguises. If a store asks the user something, the user answers.
It only works on checkouts your app created for this user, within their limits.