The customer's email address, which must be valid and under the same account. The email format is validated against RFC standards and DNS validations are performed to ensure it is deliverable. When not provided, at least one of the following attributes should be present: old_provider_id or display_name. Required for accounts with an active TAP payment gateway.

The customer's first name. If provided, must be a string containing a maximum of 255 characters. Required for accounts with an active TAP payment gateway.

The customer's last name. If provided, must be a string containing a maximum of 255 characters. Required for accounts with an active TAP payment gateway.

Customer phone number. Non-numeric characters are stripped. Resulting digits must be between 5 and 20.

The unique identifier of this customer from the previous provider. If provided, must be unique under the same account. If email is not provided, either this attribute or display_name is required.

The customer's display name. If provided, must be a string containing a maximum of 100 characters. If email is not provided, either this attribute or old_provider_id is required.

The customer's organization. If provided, must be a string containing a maximum of 255 characters.

The customer's tax identification number.

The customer password. If provided, must match the password_bcrypt algorithm format by default, unless specified otherwise via password_type attribute.

The algorithm used on the provided password string. One of: plain_text, password_bcrypt, md5, drupal_v8.2.x, bcrypt_wordpress, crypt.

The customer's username. If provided, must be a string containing a maximum of 100 alpha-numeric characters in the ASCII range (0-9, a-z, A-Z), dashes or underscores.

The customer's title. If provided, must be a string containing a maximum of 255 characters.

The customer's salutation. If provided, must be a string containing a maximum of 255 characters.

The customer's time zone. If provided, must be a valid identifier or alias, see list of supported values.

The customer's language as a two-letter code, defined by ISO 639-1 standard.

The unique identifier for customer on your current payment gateway provider (e.g. Stripe). You can pass this identifier during a migration in-order to import the customer's payment methods from the payment gateway so that you can re-create the subscriptions using the payment methods. Once imported from the gateway, you can find the default source in the customer list API endpoint which can be used to re-create the subscriptions.

The customer's billing email.