Manage Memory
Memory reduces repeated user input while keeping Memory values behind MagicPay requests.
Add Memory Before A Session
Use the UI to add data you expect agents to need: marketplace logins, delivery addresses, identity details, and travel-document information.
Save Memory During A Session
When the agent reaches a field with missing data, MagicPay can ask the user to provide it and store it for next time.
Approve Reuse
Future sessions can request access to stored Memory. The user can approve or deny the request through the same delivery channels used for payment approvals.
- Keep account credentials, identity details, and payment values out of agent chat.
- Use site-specific Memory where possible.
- Review old Memory when a marketplace account or identity document changes.