Agentforce Prerequisite Guide¶

What must be true in your org before you set up the ChargeOn agent.

Who does this: a Salesforce administrator.
How long: about 20 minutes, assuming ChargeOn is already working.

ChargeOn must be working first

The agent uses your ChargeOn configuration to handle payments by conversation. Complete the ChargeOn quick start guide and take a successful test payment before you begin.

What You Will Check¶

Agentforce is available in your org
ChargeOn is configured and working
Saved payment methods exist
You have decided who can do what

Part 1: Agentforce in Your Org¶

Requirement	How to check
Agentforce is enabled	Agentforce Studio appears in your App Launcher
Lightning Experience is enabled	You are using the modern interface
My Domain is deployed to all users	Setup → My Domain

What you should see: Agentforce Studio opens.

Part 2: ChargeOn Is Configured and Working¶

The agent uses the same payment setup as the Charge button. Confirm that setup with a successful test payment before testing the agent.

Confirm:

ChargeOn is installed and licensed.
At least one payment gateway is active and verified.
That gateway is mapped to your payment object.
You have taken at least one successful test payment through the Charge button.

What you should see: a successful transaction in Transaction History, taken the ordinary way.

Part 3: Saved Payment Methods¶

The agent charges a customer’s saved payment method. Save a payment method through the Charge button, a payment link or Register Token before asking the agent to charge it. Enter card details on the payment form, never in a conversation.

Before testing the agent, make sure:

The customer you will test with has a saved payment method.
That payment method is against the gateway you intend to use.
The payment method is active.

What you should see: at least one active saved payment method against your test customer.

How a payment method gets saved

Take a payment through the Charge button, or through a payment link, and accept the option to save the payment method. Register Token saves one without charging.

Part 4: Who Can Do What¶

The agent enforces two separate limits, and you should decide both before setup rather than during it.

What each user may do. Assign permission sets for each person’s role, such as looking up transactions, issuing refunds or taking payments. The agent enforces those permissions for every request.

What the agent may do at all. Separately, you set ceilings and allowed operations that apply to everybody: a maximum per transaction, a maximum per user per day, and which operations are available. These can narrow access further, but never widen it.

Decide now:

Decision	Example
Maximum per transaction	The largest single amount anyone may take by conversation
Maximum per user per day	The daily total for one user
Which operations are allowed	Charge, authorise, capture, void, refund, schedule, payment link, installment plan, subscription
Which phrases count as confirmation	"Confirm", "Yes", "Proceed", "Go ahead"

The ceiling is absolute, and it applies to everything

A ceiling is enforced on the amount, not on the payment type. If a payment is refused for exceeding it, sending a payment link for the same amount will be refused too. There is no route around it except a smaller amount, or an administrator raising the ceiling.

What you should see: four answers written down, ready to enter during setup.

Next¶

Agentforce setup guide.

If Something Went Wrong¶

Symptom	Likely cause	What to do
Agentforce Studio is not in the App Launcher	Agentforce is not enabled for your org	Talk to your Salesforce account executive
Your test customer has no saved payment method	Nothing has been saved for them yet	Take a payment through the Charge button and accept the save option, or use Register Token
You are unsure what ceilings to set	Nobody has decided the policy	This is a business decision about risk, not a technical one. Settle it before setup: a ceiling that is wrong in production is a live incident