Credit Card Verification
Credit Card Verification: Create
You can perform a standalone credit card verification without storing the card in the Vault. However, to do so you must pass raw credit card data,
which should only be done in a PCI compliant environment.
If in doubt, use a payment_method_nonce
to perform a standard
card verification and vault the card.
Parameters
:company
String:country_code_alpha2
StringThe ISO 3166-1 alpha-2 country code specified in an address. The gateway only accepts specific alpha-2 values.
:country_code_alpha3
StringThe ISO 3166-1 alpha-3 country code specified in an address. The gateway only accepts specific alpha-3 values.
:country_code_numeric
StringThe ISO 3166-1 numeric country code specified in an address. The gateway only accepts specific numeric values.
:country_name
StringThe country name specified in an address. We only accept specific country names.
:extended_address
String:first_name
String:country_code
String:national_number
String:last_name
String:locality
String:phone_number
StringDeprecated.
We recommend using international_phone
. This functionality still exists in the gateway but is no longer documented. This parameter will be removed in the future.
:postal_code
String:region
String:street_address
String:cardholder_name
String:cvv
String:expiration_date
StringThe expiration date, formatted MM/YY
or MM/YYYY
. May be used instead of expiration_month and expiration_year.
:expiration_month
StringThe expiration month of a credit card, formatted MM
. May be used with expiration_year, and instead of expiration_date.
:expiration_year
StringThe 2 or 4 digit year associated with a credit card, formatted YYYY
or YY
. May be used with expiration_month, and instead of expiration_date.
:number
String:status
StringThe option indicates the vaulted status of the externally vaulted payment method. Accepted values:
vaulted
= Indicates the payment method is already stored on behalf of the customer.will_vault
= Indicates the payment method is intended to be vaulted upon successful processing of the verification.
:amount
String:merchant_account_id
StringSpecify the merchant account ID that you want to use to verify a card. See the merchant_account_id
on Transaction: Sale
to learn more.
:payment_method_nonce
String:customer_browser
String:customer_ip
StringResults 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
StringCardholder 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
StringTransaction identifier resulting from 3D Secure 2 authentication. This field must be supplied for Mastercard Identity Check.
:eci_flag
StringThe 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
= Success04
= Data-Only (Applies to limited processors)
Accepted values for all other card brands:
07
= Failed or not attempted06
= Attempted05
= Success
:three_d_secure_version
StringThe 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
StringTransaction 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.