What you can ask the AI assistant

Questions it can answer

• What a customer paid, and when — for example, "What did Acme Corp pay last month?"
• What is in someone's transaction history over a given period.
• Which payment methods a customer has on file, and whether they are active.
• A summary of a payee, found by name or email.

Actions it can take

Every action below shows you exactly what it is about to do before anything happens — see before money moves.

• Charge a customer's saved payment method.
• Place an authorisation hold on a saved payment method — reserve funds without taking them yet.
• Capture a payment that was previously authorised.
• Void an authorisation.
• Refund a transaction.
• Send a payment link.
• Set up a scheduled payment.
• Set up a recurring payment.
• Turn a saved payment method on or off.

Before money moves

For anything that moves money or changes an account — a charge, a refund, a hold, a new recurring plan — the assistant always shows you a preview first: what it is about to do, to whom, and for how much. Nothing happens until you reply confirming it, in your own words — "yes", "confirm" and "go ahead" all work. That offer stays open only for a few minutes; if it has expired, just ask again.

Whatever you confirm is exactly what runs. The assistant cannot quietly change the amount or the target between showing you the preview and you confirming it.

What it will not do

• It cannot register a new payment method. Card and bank details are always entered outside the conversation, on ChargeOn's own payment form or the gateway's own secure page — never typed into the chat.
• It never sees or asks for a card number, CVV or bank account number. It only ever refers to a payment method by name, for example "the card ending 4242".
• It cannot go over a ceiling your administrator has set. If your organisation has set a maximum amount per payment, or per person per day, the assistant refuses anything over that limit, no matter how the request is phrased. Where a ceiling has been set, it is absolute — it cannot be talked around, and asking for a payment link instead will be refused for the same amount. Only a smaller amount, or an administrator raising the ceiling, changes that.
• It cannot do anything your own permissions do not already allow. If it tells you a request is not available to you, that reflects your access — ask your administrator if you think that is wrong.
• It cannot act on someone else's payments. Two customers can share an email address, so it checks names carefully rather than guessing which one you mean.

Check your ceilings rather than assuming they are set

ChargeOn ships an agent payment policy that is switched on but sets no spending limits — it carries only a timing setting. Because the policy record exists and shows as active, it is easy to assume limits are in place when none are.

Before your team uses the assistant for payments, open the agent payment policy and confirm a maximum per transaction and a maximum per user per day are actually filled in. See the Agentforce setup guide, Part 3.