See also the Payment Method response object.
To create a new payment method for an existing customer, the only required attributes are the customer ID and payment method nonce.
result = gateway.payment_method.create(
:customer_id => "131866",
:payment_method_nonce => nonce_from_the_client
)
Parameters
:billing_address
A billing address associated with a specific customer ID. It can be further associated with a specific payment method. The maximum number of addresses per customer is 50.
:country_code_alpha2
String
The ISO 3166-1 alpha-2 country code specified in an address. The gateway only accepts specific alpha-2 values.
:country_code_alpha3
String
The ISO 3166-1 alpha-3 country code specified in an address. The gateway only accepts specific alpha-3 values.
:country_code_numeric
String
The ISO 3166-1 numeric country code specified in an address. The gateway only accepts specific numeric values.
:country_name
String
The country name specified in an address. Braintree only accepts specific country names.
:extended_address
String
The extended address information—such as apartment or suite number. 255 character maximum.
:first_name
String
The first name. The first name value must be less than or equal to 255 characters.
:postal_code
String
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.
:region
String
The state or province. For PayPal addresses, the region must meet PayPal's state restrictions; for all other payment methods, it must be less than or equal to 255 characters.
:street_address
String
The street address. Street address must be less than or equal to 255 characters. Required to perform card verification when AVS rules are configured to require street address.
:billing_address_id
String
The two-letter value for an address associated with a specific customer ID. The maximum number of addresses per customer is 50.
:customer_id
required, String
A string value representing an existing customer in your Vault that you want to create a payment method for.
:cvv
String
Typically requires PCI SAQ D compliance
We recommend using payment_method_nonce 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.
:device_data
String
Customer device information. Pass this value only if you have Advanced 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.
:expiration_date
String
Typically requires PCI SAQ D compliance
We recommend using payment_method_nonce to avoid any PCI concerns with raw credit card data being present on your server.
The expiration date of a credit card, formatted MM/YY
or MM/YYYY
. May be used instead of expiration_month
and expiration_year
.
:expiration_month
String
Typically requires PCI SAQ D compliance
We recommend using payment_method_nonce to avoid any PCI concerns with raw credit card data being present on your server.
The expiration month of a credit card, formatted MM
. May be used with expiration_year
, and instead of expiration_date
.
:expiration_year
String
Typically requires PCI SAQ D compliance
We recommend using payment_method_nonce to avoid any PCI concerns with raw credit card data being present on your server.
The two or four digit year associated with a credit card, formatted YYYY
or YY
. May be used with expiration_month
, and instead of expiration_date
.
:number
String
Typically requires PCI SAQ D compliance
We recommend using payment_method_nonce to avoid any PCI concerns with raw credit card data being present on your server.
The 12-19 digit value on a credit card consisting of a bank identification number (BIN) and primary account number (PAN).
:fail_on_duplicate_payment_method
bool
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.
:verification_amount
String
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.
:verification_merchant_account_id
String
Specify the merchant account ID that you want to use to verify a card. See the merchant_account_id on Transaction: Sale to learn more. The merchant account can't be a marketplace sub-merchant account. See the Braintree Marketplace Guide to learn more.
:verify_card
bool
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.
:payment_method_nonce
required, String
One-time-use reference to payment information provided by your customer, such as a credit card or PayPal account.
The ability to transact on credit card information will not be verified automatically on create – you must explicitly perform card verification.
:three_d_secure_pass_thru
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.
:cavv
String
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 cavv
parameter.
:ds_transaction_id
String
Transaction identifier resulting from 3D Secure 2 authentication. This field must be supplied for Mastercard Identity Check.
:eci_flag
required, String
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 attempted01
= Attempted02
= Success
Accepted values for all other card brands:
07
= Failed or not attempted06
= Attempted05
= Success
:three_d_secure_version
required, String
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. 1.0.2
).
:xid
String
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.
:token
String
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.
Examples
Specify a token
If you are using a custom integration and want to specify what you would like the token to be, pass it with the other parameters, as in the example below. If you do not specify a payment method token, the gateway will generate a random one. Note that if you are using our Drop-in UI, you can't specify your own token.
result = gateway.payment_method.create(
:customer_id => "131866",
:token => "the_token",
:payment_method_nonce => nonce_from_the_client
)
New default payment method
If a customer has multiple payment methods, the first payment method created will be the
customer's default. The default payment method is used when
creating transactions with customer_id
. To set a new payment method as the default, use the make_default
option.
result = gateway.payment_method.create(
:customer_id => "131866",
:payment_method_nonce => nonce_from_the_client,
:options => {
:make_default => true
}
)
New payment method with billing address
To specify a billing address when creating a new payment method, use the billing_address
option
(ignored if the payment method is a PayPal account). Note that the specified billing address will override any address specified during nonce creation.
result = gateway.payment_method.create(
:customer_id => "131866",
:payment_method_nonce => nonce_from_the_client,
:billing_address => {
:street_address => "123 Abc Way"
}
)
New payment method with existing billing address
If a customer already has an address you'd like to use, you can create a new payment method with that address.
result = gateway.payment_method.create(
:customer_id => "131866",
:payment_method_nonce => nonce_from_the_client,
:billing_address_id => "the-billing-address-id"
)
Preventing duplicate payment methods
If a payment method exists in your Vault and you do not want to create a new payment method, you can reject duplicates by using the fail_on_duplicate_payment_method
option. Note: This option will be ignored for PayPal, Pay with Venmo, Apple Pay, Google Pay, and Samsung Pay payment methods.
result = gateway.payment_method.create(
:customer_id => "131866",
:payment_method_nonce => nonce_from_the_client,
:options => {
:fail_on_duplicate_payment_method => true
}
)
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
.
result = gateway.payment_method.create(
:customer_id => "the_customer_id",
:payment_method_nonce => nonce_from_the_client,
:options => {
:verify_card => true
}
)
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.