When an existing Moonbase customer’s name is updated after account confirmation, the updated name is correctly saved in Moonbase but is not propagated to the corresponding MailerLite subscriber.

Our flow is:

1. We create a passwordless customer and provision a license using:

   POST /api/licenses/provision

2. We set newsletter and product-update consent using:

   PATCH /api/customers/{customerId}

3. The customer follows the Moonbase account-confirmation link, sets a password, and signs in.

4. After authentication, we update the customer’s real name using:

   PATCH /api/customer/identity
   Authorization: Bearer {accessToken}
   Content-Type: application/json

   {
     "name": "Customer Name",
     "email": "customer@example.com",
     "communicationPreferences": {
       "newsletterOptIn": true,
       "productUpdatesOptIn": true
     }
   }
   

The new name is visible on the customer in Moonbase. However, the existing MailerLite subscriber is not updated and retains the placeholder name originally used during provisioning.

Expected behavior

When a Moonbase customer’s name changes, the MailerLite integration should update the corresponding subscriber’s name while preserving their existing subscription status and communication preferences.