Editing Customers
What can be edited
Section titled “What can be edited”All core customer fields can be edited: name, email, reference, contact details, addresses, notification preferences, and fee preferences.
The external_reference_id (cus_xxx) cannot be changed — it is assigned at creation and is permanent.
Custom attributes can be edited at any time. A required attribute cannot be left blank.
Status
Section titled “Status”A customer’s status can’t be edited. It’s shown on the customer list and detail pages, and you can filter the list by it. See customer statuses for what each one means.
Status doesn’t start or stop payments. To stop charging a customer, suspend, deactivate or close their payment plans from each plan’s detail page.
Payment method recovery
Section titled “Payment method recovery”When a payment method fails in a way that means it can’t be used again, ElasticPay suspends the plans that use it and emails the customer a recovery link. Any new payment method collected for the customer resumes those plans, whether through the link, Customer is with me or Collect Payment Details. A code about the customer, such as a deceased customer, instead suspends every plan for your review and sends no email. See Handling failures.
Click Resend customer setup email if the customer did not receive the first email. Once the link has expired, Send a new setup email sends a new one. In sandbox, these emails only reach people in your team (Emails in test mode).
Audit trail
Section titled “Audit trail”All changes to a customer record are logged in the activity log at the bottom of the detail page. Each entry shows the changed fields, old and new values, and timestamp. The consent_authorised_at timestamp is set once and is never overwritten.