PaymentMethod.update()

See also the PaymentMethod response object.

note

If you have card verification enabled, any updates made to credit cards are subject to those rules.

result = gateway.payment_method.update(
  "the_token",
  :billing_address => {
    :street_address => "1 E Main St",
    :extended_address => "Suite 3",
    :locality => "Chicago",
    :region => "IL",
    :postal_code => "60622",
    :options => {
      :update_existing => true
    }
  }
)

If the payment method can't be found, it will raise a Braintree::NotFoundError.

Arguments

Additional Parameters

Examples

Update billing address

To update the existing billing address when updating a payment method use the update_existing option. If any other payment methods are associated with the same billing address, this will also update the billing address for those payment methods.

result = gateway.payment_method.update(
  "the_token",
  :billing_address => {
    :street_address => "1 E Main St",
    :extended_address => "Suite 3",
    :locality => "Chicago",
    :region => "IL",
    :postal_code => "60622",
    :options => {
      :update_existing => true
    }
  }
)

If the payment method can't be found, it will raise a Braintree::NotFoundError.

New billing address

If you don't use the update_existing option, a new address will be created. The existing billing address will remain in the Vault associated with the customer.

result = gateway.payment_method.update(
  "the_token",
  :billing_address => {
    :street_address => "1 E Main St",
    :extended_address => "Suite 3",
    :locality => "Chicago",
    :region => "IL",
    :postal_code => "60622",
  }
)

Update with existing billing address

If a customer already has an address you'd like to use, you can update the payment method with that address.

result = gateway.payment_method.update(
  "the_token",
  :billing_address_id => "the_billing_address_id"
)

Updating a PayPal account token

The only fields that may be updated on a PayPal account are the token associated with that account, and setting the account as the default payment method for a customer.

updated_result = gateway.paypal_account.update(original_token,
  :token => new_token
)

Make default

If the payment method is a credit card or PayPal account, you can use this call to set the payment method as the customer's default. For all other payment method types, use default_payment_method_token on Customer.update() instead.

result = gateway.payment_method.update(
  "the_token",
  :options => {
    :make_default => true
  }
)

note

This only works with credit cards and PayPal accounts. We recommend updating the customer to set a default payment method.

Card verification

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 verify_card to true.

If you have AVS/CVV checks enabled, they will be performed when you call the payment method update. To skip these checks, set set verify_card to false.

result = gateway.payment_method.update("the_payment_method_token",
  :payment_method_nonce => nonce_from_the_client,
  :options => {
    :verify_card => true
  }
)

important

If you are using our Advanced Fraud Management Tools, we strongly recommend passing device_data each time you verify a card.

Updating with a nonce and additional parameters

When updating the credit card information with a nonce, you may pass additional parameters to update as well. Here is an example of updating a payment method and explicitly verifying the card.

important

If a field is passed from the client and included in the nonce data (such as postal code) it should not be passed as an explicit argument as well.

result = gateway.payment_method.update(
  "the_token",
  :payment_method_nonce => nonce_from_the_client,
  :billing_address => {
    :street_address => "1 E Main St",
    :extended_address => "Suite 3",
    :locality => "Chicago",
    :region => "IL",
  }
)

important

If you are using our Advanced Fraud Management Tools, we strongly recommend passing device_data each time you verify a card.

To verify the AVS information of an existing payment method, pass the update request with verify_card set to "true". Note that an update will create a transaction, so if your processing options are set to reject transactions without CVV, you will need to include CVV as a parameter, or disable this rule (see below).

To disable the CVV requirement:

1. Log into the Control Panel
2. Click on the gear icon in the top right corner
3. Click Fraud Management from the drop-down menu
4. Next to CVV, click the Options link
5. Under the Reject Transactions & Verifications If section, uncheck the CVV Not Provided (I) box

Payment method nonces vs. raw card data

While it is possible to pass both raw card data and a payment method nonce in the same call, we recommend passing only a payment method nonce.

Passing both will result in a payment method that has a mix of their attributes, with precedence given to the fields individually, then to the attributes of the payment method nonce. For example, if you pass both a card number and a payment method nonce, the payment method will have the number you passed explicitly, but the rest of the attributes will be obtained through the nonce.