Your full card details stay out of the assistant flow.
Your shadow uses a short secure review step so card details can be forwarded into the merchant's live checkout without being typed into chat, saved in customer memory, or passed back through the assistant after the handoff.
Selectors in, secrets out
Direct fill into merchant checkout
Full PAN, CVV, and name stay out of stored session data
Visual flow
Think of it like a secure browser autofill bridge
01
Card numberab12
CVVcd34
Name on cardef56
Merchant fields are identified
Your shadow starts with stable data-wb-id selectors from the merchant checkout, such as ab12 or cd34. Those ids tell it where the fields live, not what values go into them.
02
Secure review
4242 4242 4242 4242
Jane Doe · 01 / 2028
Entered here, outside the assistant chat.
You enter the details yourself
You type the card number, CVV, expiry, and cardholder name if needed into the hosted review step instead of sending those details through the assistant chat.
03
Encrypted handoff
Filled directly into the merchant's live fields.
Your shadow performs the secure handoff
When you press submit, the values are written directly into the merchant's live inputs and the same sort of input and change events a browser autofill flow would trigger are fired.
04
Your shadow resumes
exp_month: 01exp_year: 2028
PAN, CVV, and name stay hidden from the assistant.
Your shadow continues with only what it needs
The assistant resumes without your full card number, CVV, or name. Some merchants only need the month and year returned so your shadow can finish a separate expiry picker.
Stored briefly
Session metadata needed to run the flow
Merchant name, product summary, amount, and session status.
The merchant's stable field ids so your shadow knows where to place each value.
The short-lived secure payment session and completion state.
Not stored
Sensitive card data stays out of normal assistant memory
Full card number, CVV, and cardholder name are not written into the payment session record.
Those values are not saved into the customer memory or profile database.
Sensitive inputs are masked during the live fill so they are not exposed back to the assistant view.
