com.braintreepayments.api

Class ThreeDSecure

java.lang.Object

com.braintreepayments.api.ThreeDSecure

public class ThreeDSecure
extends java.lang.Object

3D Secure is a protocol that enables cardholders and issuers to add a layer of security to e-commerce transactions via password entry at checkout. One of the primary reasons to use 3D Secure is to benefit from a shift in liability from the merchant to the issuer, which may result in interchange savings. Please read our online documentation for a full explanation of 3D Secure.

Constructor Summary

Constructors

Constructor and Description
ThreeDSecure()

Method Summary

Modifier and Type	Method and Description
protected static void	onActivityResult(BraintreeFragment fragment, int resultCode, android.content.Intent data)
static void	performVerification(BraintreeFragment fragment, CardBuilder cardBuilder, java.lang.String amount) Verification is associated with a transaction amount and your merchant account.
static void	performVerification(BraintreeFragment fragment, java.lang.String nonce, java.lang.String amount) Verification is associated with a transaction amount and your merchant account.
static void	performVerification(BraintreeFragment fragment, ThreeDSecureRequest request) Verification is associated with a transaction amount and your merchant account.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

ThreeDSecure

public ThreeDSecure()

Method Detail

performVerification

public static void performVerification(BraintreeFragment fragment,
                                       CardBuilder cardBuilder,
                                       java.lang.String amount)

Verification is associated with a transaction amount and your merchant account. To specify a different merchant account (or, in turn, currency), you will need to specify the merchant account id when generating a client token During lookup the original payment method nonce is consumed and a new one is returned, which points to the original payment method, as well as the 3D Secure verification. Transactions created with this nonce will be 3D Secure, and benefit from the appropriate liability shift if authentication is successful or fail with a 3D Secure failure.

Parameters:

fragment - the BraintreeFragment backing the http request. This fragment will also be responsible for handling callbacks to it's listeners

cardBuilder - The cardBuilder created from raw details. Will be tokenized before the 3D Secure verification if performed.

amount - The amount of the transaction in the current merchant account's currency

performVerification

public static void performVerification(BraintreeFragment fragment,
                                       java.lang.String nonce,
                                       java.lang.String amount)

Verification is associated with a transaction amount and your merchant account. To specify a different merchant account (or, in turn, currency), you will need to specify the merchant account id when generating a client token During lookup the original payment method nonce is consumed and a new one is returned, which points to the original payment method, as well as the 3D Secure verification. Transactions created with this nonce will be 3D Secure, and benefit from the appropriate liability shift if authentication is successful or fail with a 3D Secure failure.

Parameters:

fragment - the BraintreeFragment backing the http request. This fragment will also be responsible for handling callbacks to it's listeners

nonce - The nonce that represents a card to perform a 3D Secure verification against.

amount - The amount of the transaction in the current merchant account's currency.

performVerification

public static void performVerification(BraintreeFragment fragment,
                                       ThreeDSecureRequest request)

Verification is associated with a transaction amount and your merchant account. To specify a different merchant account (or, in turn, currency), you will need to specify the merchant account id when generating a client token During lookup the original payment method nonce is consumed and a new one is returned, which points to the original payment method, as well as the 3D Secure verification. Transactions created with this nonce will be 3D Secure, and benefit from the appropriate liability shift if authentication is successful or fail with a 3D Secure failure.

Parameters:

fragment - the BraintreeFragment backing the http request. This fragment will also be responsible for handling callbacks to it's listeners

request - the ThreeDSecureRequest with information used for authentication.

onActivityResult

protected static void onActivityResult(BraintreeFragment fragment,
                                       int resultCode,
                                       android.content.Intent data)