Class HPSOrderAbstractionInitRequest
- All Implemented Interfaces:
Serializable
When using Chase Hosted Payment Solutions (HPS), this is the POJO representing the actual request body sent to the Chase UID Init API.
- See Also:
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionprotected booleanbooleanCustomer street billing address first line.Customer street billing address second line.Customer billing address name.Card Indicators are authorization data elements available to merchants who use the Stratus (BIN 000001) platform.getCity()City of billing address.ISO Code of country of billing address.Useful if we want the Orbital profile to be created with a pre-determined ID value.Text description of the purchase this is being submitted for.getEmail()Customer email for the billing address.Custom field that can be used by the merchant to pass system related values.Custom field that can be used by the merchant to pass system related values.Custom field that can be used by the merchant to pass system related values.Custom field that can be used by the merchant to pass system related values.Custom field that can be used by the merchant to pass system related values.System value of the order, reversal, or payment.getPhone()Customer phone number for the billing address.Postal (ZIP) code of billing addressState or province of billing addressThis is used to identify whether an Orbital customer profile should be created as part of an HPS submission.The total amount of the transaction that should be engaged upon HPS submission, including a decimal and excluding a currency symbol.inthashCode()voidsetAddress(String address) Customer street billing address first line.voidsetAddress2(String address2) Customer street billing address second line.voidsetApi_key(String api_key) voidsetBilling_name(String billing_name) Customer billing address name.voidsetCard_indicators(String card_indicators) Card Indicators are authorization data elements available to merchants who use the Stratus (BIN 000001) platform.voidCity of billing address.voidsetCountry(String country) ISO Code of country of billing address.voidsetCustomer_ref_num(String customer_ref_num) Useful if we want the Orbital profile to be created with a pre-determined ID value.voidsetDescription(String description) Text description of the purchase this is being submitted for.voidCustomer email for the billing address.voidsetForm_name(String form_name) voidsetMerchant_data1(String merchant_data1) Custom field that can be used by the merchant to pass system related values.voidsetMerchant_data2(String merchant_data2) Custom field that can be used by the merchant to pass system related values.voidsetMerchant_data3(String merchant_data3) Custom field that can be used by the merchant to pass system related values.voidsetMerchant_data4(String merchant_data4) Custom field that can be used by the merchant to pass system related values.voidsetMerchant_data5(String merchant_data5) Custom field that can be used by the merchant to pass system related values.voidsetMit_msg_type(String mit_msg_type) voidsetOrder_id(String order_id) System value of the order, reversal, or payment.voidCustomer phone number for the billing address.voidsetPostal_code(String postal_code) Postal (ZIP) code of billing addressvoidsetRetry_limit(String retry_limit) voidsetSecure_id(String secure_id) voidsetState_province(String state_province) State or province of billing addressvoidsetTokenize(String tokenize) This is used to identify whether an Orbital customer profile should be created as part of an HPS submission.voidsetTotal_amount(String total_amount) The total amount of the transaction that should be engaged upon HPS submission, including a decimal and excluding a currency symbol.voidsetTxn_type(String txn_type) toString()
-
Constructor Details
-
HPSOrderAbstractionInitRequest
public HPSOrderAbstractionInitRequest()
-
-
Method Details
-
getSecure_id
-
getApi_key
-
getTxn_type
-
getTokenize
This is used to identify whether an Orbital customer profile should be created as part of an HPS submission. The only valid value (if supplied) is "1".
Chase states that this is specifically relevant when using
DefaultHPSTransactionTypes.ACCOUNT_VERIFYor any transaction type that would engage an Authorization or Authorization-Capture request. -
getCard_indicators
Card Indicators are authorization data elements available to merchants who use the Stratus (BIN 000001) platform. Card Indicators, also referred to as Card Type Indicators (CTI), are designed to capture valuable data that helps merchants make better payment decisions both at the time of the transaction and afterward
When set to 'Y', card indicators will be made available to the backend in responses to subsequent UID query requests. When 'N', card indicators will not be made available. Having this information can be helpful for determining whether the customer supplied a purchasing card and thus whether Level 2 data should be included in subsequent auth/capture transactions.
-
getCustomer_ref_num
Useful if we want the Orbital profile to be created with a pre-determined ID value. The recommendation is to leave this blank to allow Chase to auto-generate the Orbital profile ID. -
getTotal_amount
The total amount of the transaction that should be engaged upon HPS submission, including a decimal and excluding a currency symbol. For example, "10.00". A decimal must be included to ensure the correct amount is sent. Not including a decimal may result in the incorrect amount being processed. -
getOrder_id
System value of the order, reversal, or payment. This field is defined and supplied by us, and echoed back by Chase in responses. -
getDescription
Text description of the purchase this is being submitted for. -
getForm_name
-
getRetry_limit
-
getMit_msg_type
-
getMerchant_data1
Custom field that can be used by the merchant to pass system related values. -
getMerchant_data2
Custom field that can be used by the merchant to pass system related values. -
getMerchant_data3
Custom field that can be used by the merchant to pass system related values. -
getMerchant_data4
Custom field that can be used by the merchant to pass system related values. -
getMerchant_data5
Custom field that can be used by the merchant to pass system related values. -
getBilling_name
Customer billing address name. -
getAddress
Customer street billing address first line. -
getAddress2
Customer street billing address second line. -
getCity
City of billing address. -
getState_province
State or province of billing address -
getPostal_code
Postal (ZIP) code of billing address -
getCountry
ISO Code of country of billing address. 2 or 3 character ISO code. -
getEmail
Customer email for the billing address. -
getPhone
Customer phone number for the billing address. -
setSecure_id
-
setApi_key
-
setTxn_type
-
setTokenize
This is used to identify whether an Orbital customer profile should be created as part of an HPS submission. The only valid value (if supplied) is "1".
Chase states that this is specifically relevant when using
DefaultHPSTransactionTypes.ACCOUNT_VERIFYor any transaction type that would engage an Authorization or Authorization-Capture request. -
setCard_indicators
Card Indicators are authorization data elements available to merchants who use the Stratus (BIN 000001) platform. Card Indicators, also referred to as Card Type Indicators (CTI), are designed to capture valuable data that helps merchants make better payment decisions both at the time of the transaction and afterward
When set to 'Y', card indicators will be made available to the backend in responses to subsequent UID query requests. When 'N', card indicators will not be made available. Having this information can be helpful for determining whether the customer supplied a purchasing card and thus whether Level 2 data should be included in subsequent auth/capture transactions.
-
setCustomer_ref_num
Useful if we want the Orbital profile to be created with a pre-determined ID value. The recommendation is to leave this blank to allow Chase to auto-generate the Orbital profile ID. -
setTotal_amount
The total amount of the transaction that should be engaged upon HPS submission, including a decimal and excluding a currency symbol. For example, "10.00". A decimal must be included to ensure the correct amount is sent. Not including a decimal may result in the incorrect amount being processed. -
setOrder_id
System value of the order, reversal, or payment. This field is defined and supplied by us, and echoed back by Chase in responses. -
setDescription
Text description of the purchase this is being submitted for. -
setForm_name
-
setRetry_limit
-
setMit_msg_type
-
setMerchant_data1
Custom field that can be used by the merchant to pass system related values. -
setMerchant_data2
Custom field that can be used by the merchant to pass system related values. -
setMerchant_data3
Custom field that can be used by the merchant to pass system related values. -
setMerchant_data4
Custom field that can be used by the merchant to pass system related values. -
setMerchant_data5
Custom field that can be used by the merchant to pass system related values. -
setBilling_name
Customer billing address name. -
setAddress
Customer street billing address first line. -
setAddress2
Customer street billing address second line. -
setCity
City of billing address. -
setState_province
State or province of billing address -
setPostal_code
Postal (ZIP) code of billing address -
setCountry
ISO Code of country of billing address. 2 or 3 character ISO code. -
setEmail
Customer email for the billing address. -
setPhone
Customer phone number for the billing address. -
equals
-
canEqual
-
hashCode
public int hashCode() -
toString
-