Model

Class Riskv1decisionsPaymentInformationTokenizedCard

java.lang.Object

Model.Riskv1decisionsPaymentInformationTokenizedCard

public class Riskv1decisionsPaymentInformationTokenizedCard
extends Object

Use this object to submit a payment network token instead of card-based values.

Constructor Summary

Constructors

Constructor and Description
Riskv1decisionsPaymentInformationTokenizedCard()

Method Summary

Modifier and Type	Method and Description
boolean	equals(Object o)
Riskv1decisionsPaymentInformationTokenizedCard	expirationMonth(String expirationMonth)
Riskv1decisionsPaymentInformationTokenizedCard	expirationYear(String expirationYear)
String	getExpirationMonth() One of two possible meanings: - The two-digit month in which a token expires.
String	getExpirationYear() One of two possible meanings: - The four-digit year in which a token expires.
String	getNumber() Customer’s payment network token value.
String	getTransactionType() Type of transaction that provided the token data.
String	getType() Three-digit value that indicates the card type.
int	hashCode()
Riskv1decisionsPaymentInformationTokenizedCard	number(String number)
void	setExpirationMonth(String expirationMonth)
void	setExpirationYear(String expirationYear)
void	setNumber(String number)
void	setTransactionType(String transactionType)
void	setType(String type)
String	toString()
Riskv1decisionsPaymentInformationTokenizedCard	transactionType(String transactionType)
Riskv1decisionsPaymentInformationTokenizedCard	type(String type)

Methods inherited from class java.lang.Object

clone, finalize, getClass, notify, notifyAll, wait, wait, wait

Constructor Detail

Riskv1decisionsPaymentInformationTokenizedCard

public Riskv1decisionsPaymentInformationTokenizedCard()

Method Detail

transactionType

public Riskv1decisionsPaymentInformationTokenizedCard transactionType(String transactionType)

getTransactionType

public String getTransactionType()

Type of transaction that provided the token data. This value does not specify the token service provider; it specifies the entity that provided you with information about the token. Possible value: - `2`: Near-field communication (NFC) transaction. The customer’s mobile device provided the token data for a contactless EMV transaction. For recurring transactions, use this value if the original transaction was a contactless EMV transaction. #### Visa Platform Connect - `1`: For Rupay and In App tokenization. Example: InApp apple pay. - `3`: Card/Credential On File Tokenization. **NOTE** No CyberSource through VisaNet acquirers support EMV at this time. Required field for PIN debit credit or PIN debit purchase transactions that use payment network tokens; otherwise, not used.

Returns:

transactionType

setTransactionType

public void setTransactionType(String transactionType)

type

public Riskv1decisionsPaymentInformationTokenizedCard type(String type)

getType

public String getType()

Three-digit value that indicates the card type. **IMPORTANT** It is strongly recommended that you include the card type field in request messages even if it is optional for your processor and card type. Omitting the card type can cause the transaction to be processed with the wrong card type. Possible values: - `001`: Visa. For card-present transactions on all processors except SIX, the Visa Electron card type is processed the same way that the Visa debit card is processed. Use card type value `001` for Visa Electron. - `002`: Mastercard, Eurocard[^1], which is a European regional brand of Mastercard. - `003`: American Express - `004`: Discover - `005`: Diners Club - `006`: Carte Blanche[^1] - `007`: JCB[^1] - `014`: Enroute[^1] - `021`: JAL[^1] - `024`: Maestro (UK Domestic)[^1] - `031`: Delta[^1]: Use this value only for Ingenico ePayments. For other processors, use `001` for all Visa card types. - `033`: Visa Electron[^1]. Use this value only for Ingenico ePayments and SIX. For other processors, use `001` for all Visa card types. - `034`: Dankort[^1] - `036`: Cartes Bancaires[^1,4] - `037`: Carta Si[^1] - `039`: Encoded account number[^1] - `040`: UATP[^1] - `042`: Maestro (International)[^1] - `050`: Hipercard[^2,3] - `051`: Aura - `054`: Elo[^3] - `062`: China UnionPay - '070': EFTPOS [^1]: For this card type, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in your request for an authorization or a stand-alone credit. [^2]: For this card type on Cielo 3.0, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in a request for an authorization or a stand-alone credit. This card type is not supported on Cielo 1.5. [^3]: For this card type on Getnet and Rede, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in a request for an authorization or a stand-alone credit. [^4]: For this card type, you must include the `paymentInformation.card.type` in your request for any payer authentication services. #### Used by **Authorization** Required for Carte Blanche and JCB. Optional for all other card types. #### Card Present reply This field is included in the reply message when the client software that is installed on the POS terminal uses the token management service (TMS) to retrieve tokenized payment details. You must contact customer support to have your account enabled to receive these fields in the credit reply message. Returned by the Credit service. This reply field is only supported by the following processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX #### Google Pay transactions For PAN-based Google Pay transactions, this field is returned in the API response. #### GPX This field only supports transactions from the following card types: - Visa - Mastercard - AMEX - Discover - Diners - JCB - Union Pay International

Returns:

type

setType

public void setType(String type)

number

public Riskv1decisionsPaymentInformationTokenizedCard number(String number)

getNumber

public String getNumber()

Customer’s payment network token value.

Returns:

number

setNumber

public void setNumber(String number)

expirationMonth

public Riskv1decisionsPaymentInformationTokenizedCard expirationMonth(String expirationMonth)

getExpirationMonth

public String getExpirationMonth()

One of two possible meanings: - The two-digit month in which a token expires. - The two-digit month in which a card expires. Format: `MM` Possible values: `01` through `12` **NOTE** The meaning of this field is dependent on the payment processor that is returning the value in an authorization reply. Please see the processor-specific details below. #### Barclays and Streamline For Maestro (UK Domestic) and Maestro (International) cards on Barclays and Streamline, this must be a valid value (`01` through `12`) but is not required to be a valid expiration date. In other words, an expiration date that is in the past does not cause CyberSource to reject your request. However, an invalid expiration date might cause the issuer to reject your request. #### Encoded Account Numbers For encoded account numbers (`card_type=039`), if there is no expiration date on the card, use `12`.\\ **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting. #### Samsung Pay and Apple Pay Month in which the token expires. CyberSource includes this field in the reply message when it decrypts the payment blob for the tokenized transaction. For processor-specific information, see the `customer_cc_expmo` field in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html)

Returns:

expirationMonth

setExpirationMonth

public void setExpirationMonth(String expirationMonth)

expirationYear

public Riskv1decisionsPaymentInformationTokenizedCard expirationYear(String expirationYear)

getExpirationYear

public String getExpirationYear()

One of two possible meanings: - The four-digit year in which a token expires. - The four-digit year in which a card expires. Format: `YYYY` Possible values: `1900` through `3000` Data type: Non-negative integer **NOTE** The meaning of this field is dependent on the payment processor that is returning the value in an authorization reply. Please see the processor-specific details below. #### Barclays and Streamline For Maestro (UK Domestic) and Maestro (International) cards on Barclays and Streamline, this must be a valid value (1900 through 3000) but is not required to be a valid expiration date. In other words, an expiration date that is in the past does not cause CyberSource to reject your request. However, an invalid expiration date might cause the issuer to reject your request. #### Encoded Account Numbers For encoded account numbers (`card_ type=039`), if there is no expiration date on the card, use `2021`. #### FDC Nashville Global and FDMS South You can send in 2 digits or 4 digits. When you send in 2 digits, they must be the last 2 digits of the year. #### Samsung Pay and Apple Pay Year in which the token expires. CyberSource includes this field in the reply message when it decrypts the payment blob for the tokenized transaction. **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting. For processor-specific information, see the `customer_cc_expyr` or `token_expiration_year` field in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html)

Returns:

expirationYear

setExpirationYear

public void setExpirationYear(String expirationYear)

equals

public boolean equals(Object o)

Overrides:

equals in class Object

hashCode

public int hashCode()

Overrides:

hashCode in class Object

toString

public String toString()

Overrides:

toString in class Object