Map ChargeOn fields to your objects¶
This mapping is what makes the Charge button and payment links work on your own records. It tells ChargeOn what you are collecting payment for, who is paying, and where to find the amount.
Before you start¶
- A connected, verified gateway.
- Decide which Salesforce object you are taking payments against — a standard object such as Opportunity, or any custom object you use to track work worth billing.
- Know how that object relates to the person paying — does it look up to a Contact or Account, or is the payer looked up from the other direction?
Steps¶
- Open the ChargeOn app, go to the ChargeOn tab (or Settings Hub → Object Mappings), and click New.
- Under Payment Details, choose the Payment Object Name — the object you are taking payments against.
- Choose the Remaining Amount field — the currency field on that object that holds the amount to charge.
- Choose the Preferred Payment Gateway — the default gateway for this object type.
- Under Payer Details, choose how the payer relates to the payment object, then map its fields, using the table below.
- Map the payer's First Name, Last Name and Email (or enter static values, if the relationship is No Relation).
- Under Address Details, map Street, City, State/Province, Postal Code and Country — or enter static values, again for No Relation.
- Under Site & Email Configuration, choose the ChargeOn Salesforce Site your payment links will use, and the success, failed, pending and error pages, if you are not using the defaults.
- Under Email Templates, assign a template for each event — Transaction Success, Transaction Authorized, Transaction Failed, Transaction Refunded, Payment Link and Automated Collection. See customise notification emails.
- Click Save Mapping.
The four payer relationships¶
| Relationship | When to use it | What you map |
|---|---|---|
| One to Many | Most common — your payment object has a lookup to the payer, e.g. Opportunity's ContactId | The lookup field, then First Name, Last Name and Email on the referenced object |
| Many to One | The payer object has a lookup back to the payment object instead | The payer object, and the lookup field on it pointing at the payment object |
| Self-referential | The payment object is the payer — there is no separate person record | First Name, Last Name and Email directly on the payment object |
| No Relation | There is no programmatic way to resolve who is paying | Static First Name, Last Name, Email and address values, entered once |
What you should see¶
A saved mapping listed under Object and Rules, showing your object and your gateway.
Optional, and worth knowing about¶
- Pre-charge notification — emails a customer before a scheduled or recurring charge runs.
- Invoice line item mapping — breaks a payment down by product or service.
- Fallback gateways — up to three gateways ChargeOn tries in order if the preferred one fails. The list only appears once Select Fallback Type is set to Payment Gateway. See route payments between gateways for the full picture, including which gateways can genuinely participate.
- Credit Memo, Surcharge, Late Fee and Template Config — each has its own configuration section on this same record.
If it does not work¶
| Symptom | Likely cause | What to do |
|---|---|---|
| The Charge button opens but no gateway is selectable | The gateway is not Active, or is not linked to this mapping | Check Active on the gateway record, then the gateway mapping here |
| Customer details come through blank on a payment | The payer relationship or a field mapping points at the wrong field | Re-check steps 5–6 against the object you are actually using |
| "No payment gateways support…" appears on the Charge screen | The record's currency is not one any linked gateway supports | Add the currency to a linked gateway, or link a gateway that already supports it |