Payment Methods¶
A saved payment method lets you charge a customer again without asking them for their details a second time. ChargeOn stores a token from the gateway, never the card number. The card data itself never reaches your Salesforce org.
| Page | What it covers |
|---|---|
| Save a payment method | Storing a card or bank account against a customer |
| Activate or deactivate | Stopping a method being used without deleting it |
| Delete a payment method | Removing one permanently, with checks for payments using it |
Installment plans and subscriptions depend on these
Installment plans and subscriptions charge a saved payment method on a schedule. Before retiring a method, review the plans and scheduled payments using it. ChargeOn offers a replacement where the gateway supports it; see activate or deactivate a payment method.
The Four Statuses¶
| Status | Meaning | Can it be charged? |
|---|---|---|
| Active | Ready to use | Yes |
| Inactive | Switched off, reversibly, by an admin | No: switch it back to Active first |
| Expired | Past its card expiry date | No: this is set automatically and cannot be undone |
| Deleted | Removed permanently | No: this cannot be undone |
ChargeOn checks saved card expiry dates on a schedule and marks expired cards Expired. Save a new payment method when a card expires.
Expiry reminders for saved cards
ChargeOn checks expiry dates on saved cards that include those details. Some gateways hold the payment method on their own secure page; use the gateway’s payment-method details to review those methods. See the gateway reference.