Payments and Tracking
Payment links, saved methods, recurring plans, invoices, tracking, and shipment communication
Payment Links
Use Send Payment Link Email from Sales Order or Payment Order records when a customer should pay remotely. Payment links should be generated from the app so email history, payment intent, payment order, and customer context stay connected.
Saved Payment Methods
Accounts and Contacts can store payment methods through the Add Payment Method action. The payment console and payment vault inventory show saved methods and gateway token coverage. Saved methods should be used before asking the customer to re-enter card details.
The app distinguishes route states such as ready, new payment method required, retokenization required, and gateway unavailable. Reps should read those messages instead of guessing whether a card can be reused.
Recurring Plans
Sales Orders can expose Manage Recurring Plan when recurring collection applies. Recurring plans can be paused, resumed, canceled, and printed from Payment Agreement records.
Tracking
Use tracking actions from Sales Order or Sales Order Tracking records:
| Action | Purpose |
|---|---|
| Add Tracking | Add tracking details when a shipment is known outside provider sync. |
| Send Tracking Email | Send tracking from the Sales Order. |
| SendTrackingEmail on Sales Order Tracking | Send tracking from a specific tracking record. |
Provider-driven fulfillment may write tracking back automatically. If a provider reports fulfillment without a tracking number, the system can still use shipment identity and packed-line evidence to complete fulfillment when supported by the provider.
Customer Follow-Up
Payment and tracking communication should be sent from the record action, not a personal email draft. The Salesforce action leaves history for support, sales management, AR, and operations.
Last updated on