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, and what breaks if you do

Recurring payments depend on these

A recurring payment charges a saved payment method on a schedule. Deleting or deactivating a method that a schedule uses will make that schedule fail — unless you replace it first, which ChargeOn will offer to help you do.

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

Expired is set automatically, not by hand. ChargeOn checks stored card expiry dates on its own schedule and flips a method to Expired the moment it passes — you never do this yourself, and you cannot reactivate a method once it happens.

Some payment methods have no expiry ChargeOn can check

A payment method saved through a redirect-style gateway — the customer pays on the gateway's own page, away from Salesforce — may be a card, a wallet, or a bank account. ChargeOn often does not know which, or what its expiry date is. Card expiry checks, and any "please update your card" reminder, simply do not apply to these. See the gateway reference for which gateways work this way.