See also the Customer response object.
To update a customer, use its ID along with new attributes. The same validations apply as when creating a customer. Any attribute not passed will remain unchanged.
$updateResult = $gateway->customer()->update( 'a_customer_id', [ 'firstName' => 'New First', 'lastName' => 'New Last', 'company' => 'New Company', 'email' => 'email@example.com', 'phone' => 'new phone', 'fax' => 'new fax', 'website' => 'http://new.example.com' ] ); $updateResult->success # true if update was successful
If the customer can't be found, you'll receive a
A billing address associated with a specific credit card. The maximum number of addresses per customer is 50.
The country name specified in an address. We only accept specific country names.
Update the billing address associated with the payment method token specified. Other payment methods associated with the same billing address will have their addresses updated, as well.
The postal code. Postal code must be a string of 4-9 alphanumeric characters, optionally separated by a dash or a space. Spaces and hyphens are ignored.
The credit card billing street address. 255 character maximum. Only required if using card verification when AVS rules are configured to require street address.
The two-letter value for an address associated with a specific credit card. The maximum number of addresses per customer is 50.
Typically requires PCI SAQ D compliance
We recommend using paymentMethodNonce to avoid any PCI concerns with raw credit card data being present on your server.
A 3 or 4 digit card verification value assigned to a credit card. The CVV will never be stored in the gateway, but it can be provided with one-time requests to verify the card.
While we recommend using paymentMethodNonce when updating raw credit card data, the expiration date can be updated directly without any PCI concerns as long as you do not store, process, or transmit the raw PAN or CVV.
The expiration date, formatted
MM/YYYY. May be used instead of
While we recommend using paymentMethodNonce when updating raw credit card data, the expiration month can be updated directly without any PCI concerns as long as you do not store, process, or transmit the raw PAN or CVV.
The expiration month of a credit card, formatted
MM. May be used with
expirationYear, and instead of
While we recommend using paymentMethodNonce when updating raw credit card data, the expiration year can be updated directly without any PCI concerns as long as you do not store, process, or transmit the raw PAN or CVV.
The two or four digit year associated with a credit card, formatted
YY. May be used with
expirationMonth, and instead of
If this option is passed and the same payment method has already been added to the Vault for any customer, the request will fail. This option will be ignored for PayPal, Pay with Venmo, Apple Pay, Google Pay, and Samsung Pay payment methods.
Specify a non-negative amount that you want to use to verify a card. If you do not pass this option, the gateway will automatically use a verification amount of $0 or $1, depending on the processor and/or card type.
Specify the merchant account ID that you want to use to verify a card. Can't be a Braintree Marketplace sub-merchant account. For more details on merchant accounts in general, see merchantAccountId on Transaction: Sale.
If the payment method is a credit card, this option prompts the gateway to verify the card's number and expiration date. It also verifies the AVS and CVV information if you've enabled AVS and CVV rules.
In some cases, cardholders may see a temporary authorization on their account after their card has been verified. The authorization will fall off the cardholder's account within a few days and will never settle.
Only returns a
CreditCardVerification result if verification runs and is unsuccessful.
Results of a merchant-performed 3D Secure authentication. You will only need to use these fields if you've performed your own integration with a 3D Secure MPI provider (e.g. Cardinal Centinel). Otherwise, Braintree's SDKs handle this for you in our standard 3D Secure integration.
Cardholder authentication verification value or CAVV. The main
encrypted message issuers and card networks use to verify authentication
has occurred. Mastercard uses an AVV message and American Express uses an
AEVV message, each of which should also be passed in the
Transaction identifier resulting from 3D Secure 2 authentication. This field must be supplied for Mastercard Identity Check.
The value of the electronic commerce indicator (ECI) flag, which indicates the outcome of the 3DS authentication.
Accepted values for Mastercard:
00= Failed or not attempted
Accepted values for all other card brands:
07= Failed or not attempted
The version of 3D Secure authentication used for the transaction. Required
on Visa and Mastercard authentications. Must be composed of digits separated
by periods (e.g.
Transaction identifier resulting from 3D Secure authentication. Uniquely identifies the transaction and sometimes required in the authorization message. Must be base64-encoded. This field will no longer be used in 3D Secure 2 authentications.
An alphanumeric value that references a specific payment method stored in your Vault. Must be less than or equal to 36 characters. If using a custom integration, you can specify what you want the token to be. If not specified, the gateway will generate one that can be accessed on the result. If using our Drop-in UI with a customer ID to vault payment methods, you can't specify your own token. Length and format of gateway-generated tokens and IDs may change at any time.
A collection of custom field/value pairs. Fields and values must be less than 255 characters. You must set up each custom field in the Control Panel prior to passing it with a request. Querying this value returns a collection of custom field values stored on the customer object.
Update the customer's default payment method to the specified token. See example below.
Customer device information. Pass this value only if you have Premium Fraud Management Tools enabled and are adding credit card data to your Vault. Be sure to provide the full string received from the Braintree client SDK.
If specified, will replace the customer's existing ID. 36 character maximum; must be unique within your Vault; valid characters are letters, numbers, -, and _; the words "all" and "new" currently can't be used.
One-time-use reference to payment information provided by your customer, such as a credit card or PayPal account. When passed on customer update, it creates a payment method associated with the existing customer; see example below.
Phone number. Phone must be 10-14 characters and can only contain numbers, dashes, parentheses and periods.
A set of country code ID pairs, analogous to Social Security numbers in the United States. A customer may have multiple national tax identifiers in the event of multinational citizenship, but only one identifier per country code. Because tax identifiers are PII, these values are not displayed in the Control Panel or serialized on the customer response. You will only need to use these fields for processing in certain countries.
To update an existing credit card when using the customer update method, you need to pass the token of the credit card under the credit card options.
$result = $gateway->customer()->update( 'a_customer_id', [ 'paymentMethodNonce' => nonceFromTheClient, 'firstName' => 'New First', 'lastName' => 'New Last', 'creditCard' => [ 'options' => [ 'updateExistingToken' => 'a_creditcard_token' ] ] ] );
If you are only storing the customer ID in your system and using a 1:1 model of customer to credit card, then you can get the token for the credit card from the customer details.
$customer = $gateway->customer()->find('a_customer_id'); $token = $customer->creditCards->token;
The billing address can also be updated by adding in the billing address details and setting the
updateExisting option in the billing address attributes.
$result = $gateway->customer()->update( 'a_customer_id', [ 'paymentMethodNonce' => nonceFromTheClient, 'firstName' => 'New First', 'creditCard' => [ 'options' => [ 'updateExistingToken' => 'a_creditcard_token' ], 'billingAddress' => [ 'firstName' => 'New First Billing', 'lastName' => 'New Last Billing', 'options' => [ 'updateExisting' => true ] ] ] ] );
If you omit the
updateExisting option under the billing address, we will create a new address for the customer and associate it to the credit card. The old address will remain associated to the customer but no longer associated as the billing address of the credit card.
You can add a new payment method to an existing customer using the customer update API.
If you omit the
updateExistingToken option from the examples in the previous sections, a new credit card will be created and associated to the customer.
$customer = $gateway->customer()->find('a_customer_id'); sizeof($customer->creditCards) # 1 $result = $gateway->customer()->update( $customer->id, [ 'paymentMethodNonce' => nonceFromTheClient, 'firstName' => 'New Customer First', 'lastName' => 'New Customer Last' ] ); sizeof($result->customer->creditCards) # 2
You can use a payment method nonce for any payment method type—not just a credit card—to associate that payment method to the customer. The example below shows adding a payment method while also updating customer details.
$result = $gateway->customer()->update( 'a_customer_id', [ 'paymentMethodNonce' => nonceFromTheClient, 'firstName' => 'New First', 'lastName' => 'New Last', ] );
To update a customer's default payment method, get that payment method's
token and pass it as the
defaultPaymentMethodToken value below:
$updateResult = $gateway->customer()->update( 'a_customer_id', [ 'defaultPaymentMethodToken' => 'the_token' ] );
By default we will run credit card validations but not perform verification. Braintree strongly recommends verifying all cards before they are stored in your Vault by enabling card verification for your entire account in the Control Panel. If you choose to manually verify cards, set
$updateResult = $gateway->customer()->update( 'a_customer_id', [ 'paymentMethodNonce' => nonceFromTheClient, 'creditCard' => [ 'options' => [ 'updateExistingToken' => 'a_creditcard_token', 'verifyCard' => true ] ] ] );