Solution
Keep an unattended robot unattended. One HTTP activity returns the token, so a back-office process does not queue up for a human to clear it.
Who this is for
Enterprise RPA teams and system integrators in finance, tax, insurance and banking operations. In China the builders are usually process analysts working in Yingdao RPA or UiBot rather than engineers; elsewhere it is UiPath and Power Automate shops. The robot runs on a schedule against a portal the business already holds an account on.
The problem
An unattended robot that logs into a supplier portal, an invoice-verification site or a company-registry lookup stalls at a distorted-character image or a slider, and an unattended process quietly becomes an attended one. In China this is the most common blocker of all: invoice verification, registry lookups and reconciliation sit behind Chinese-character OCR and sliders rather than reCAPTCHA. Buyers also need the endpoint callable from a locked-down network.
[ 02 ]Challenges you will hit
Works with
[ 04 ]Questions about this one
It needs outbound HTTPS to one hostname. No inbound connection and no agent installed on the runner; results are polled, or posted to a callback URL inside your network.
Distorted Chinese characters, arithmetic images, sliders, click-in-order and rotation. Invoice verification and company-registry lookups sit almost entirely in that set rather than on reCAPTCHA.
An HTTP Request activity creates the task, a delay-and-poll loop waits for it, and a second request fetches the result. The response is JSON, so the value drops straight into a process variable.
Yes. Use one key per process, or tag tasks with your own reference. Usage is reported per key in the dashboard, which is enough for internal chargeback.
Create a key, paste it into the sample above, and watch a real token come back. No card, no sales call.
