Headless 360 prerequisite guide¶
What must be true before you connect an external AI tool to ChargeOn.
Who does this: a Salesforce administrator. How long: about 20 minutes, once Headless 360 is switched on for your org.
ChargeOn must be working first
Headless 360 is a different way of reaching ChargeOn, not a way of setting it up. Complete the ChargeOn quick start guide and take a successful test payment first.
What you will check¶
- Headless 360 is switched on for your org
- Your org meets the requirements
- ChargeOn is configured and working
- Saved payment methods exist
- Users have the right permission
Part 1 — Headless 360 is switched on for your org¶
Start here, because it is the only item with a lead time.
Headless 360 needs two separate switches, and both must be on:
| Switch | Who turns it on |
|---|---|
| Switched on for your org | Cyntexa — ask your account executive or support |
| The org setting | You, during setup |
Ticking the setting on its own does nothing until Cyntexa has switched it on for your org. The connection will fail, and it will not be obvious why — the setting will sit there looking enabled.
Ask your Cyntexa account executive or support to confirm Headless 360 is switched on for your org before you go any further.
What you should see: written confirmation from Cyntexa that the grant is in place.
Part 2 — Your org¶
| Requirement | How to check |
|---|---|
| Enterprise, Unlimited or Developer edition | Setup → Company Information |
| Lightning Experience enabled | You are using the modern interface |
| My Domain deployed to all users | Setup → My Domain |
| You can create an External Client App | Setup → External Client Apps |
What you should see: all four confirmed, including that you personally have rights to create an External Client App. That last one often needs a security administrator.
Part 3 — ChargeOn is configured and working¶
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 a successful test payment through the Charge button.
What you should see: a successful transaction taken the ordinary way.
Part 4 — Saved payment methods¶
As with the in-Salesforce agent, Headless 360 cannot register a new payment method. It charges methods that are already saved. Card details are never collected through an external tool.
Before testing, confirm your test customer has an active saved payment method against the gateway you will use.
What you should see: at least one active saved payment method.
Part 5 — User permissions¶
Every person connecting an external tool needs the ChargeOn MCP integration permission on their own user. Without it they cannot authenticate at all.
Decide who gets it. Everyone on the list needs:
- The ChargeOn MCP integration permission
- The ordinary ChargeOn permission sets for whatever operations they should perform
The second set matters as much as the first. The permission to connect is not the permission to take a payment.
What you should see: a list of who gets access, and what each of them should be able to do.
Part 6 — What each person will need at their end¶
Anyone connecting will need an account with the AI tool they are connecting from, and the ability to add a custom connector to it. Some organisations restrict that. Check before setup day rather than during it.
You will also generate credentials during setup that must be stored somewhere secure. Decide where in advance — a password manager, not an email or a spreadsheet.
These credentials are org access
The credentials generated during setup let an external tool authenticate to your Salesforce org. Treat them exactly as you would treat a password.
Next¶
If something went wrong¶
| Symptom | Likely cause | What to do |
|---|---|---|
| Cyntexa confirms the grant, but you cannot find the setting | The grant may not have reached your org yet | Grants apply per org. Confirm they applied it to the right one — sandboxes and production are separate |
| You cannot create an External Client App | You lack the rights | Ask a security administrator. This is a Salesforce permission, not a ChargeOn one |
| Your AI tool does not allow custom connectors | Organisational policy at that vendor | Resolve before setup day. Nothing in ChargeOn can work around it |