com.onlinepayments.domain

Class CreateHostedTokenizationRequest

java.lang.Object

com.onlinepayments.domain.CreateHostedTokenizationRequest

public class CreateHostedTokenizationRequest
extends Object

Constructor Summary

Constructors

Constructor and Description
CreateHostedTokenizationRequest()

Method Summary

Modifier and Type	Method and Description
Boolean	getAskConsumerConsent() Indicate if the tokenization form should contain a checkbox asking the user to give consent for storing their information for future payments.
String	getLocale() Locale used in the GUI towards the consumer.
PaymentProductFiltersHostedTokenization	getPaymentProductFilters() Contains the payment product ids that will be used for manipulating the payment products available for the payment to the customer.
String	getTokens() String containing comma separated tokens (no spaces) associated with the customer of this hosted session.
String	getVariant() Using the Back-Office it is possible to upload multiple templates of your HostedCheckout payment pages, including customized templates from Merchant Portal.
void	setAskConsumerConsent(Boolean value) Indicate if the tokenization form should contain a checkbox asking the user to give consent for storing their information for future payments.
void	setLocale(String value) Locale used in the GUI towards the consumer.
void	setPaymentProductFilters(PaymentProductFiltersHostedTokenization value) Contains the payment product ids that will be used for manipulating the payment products available for the payment to the customer.
void	setTokens(String value) String containing comma separated tokens (no spaces) associated with the customer of this hosted session.
void	setVariant(String value) Using the Back-Office it is possible to upload multiple templates of your HostedCheckout payment pages, including customized templates from Merchant Portal.
CreateHostedTokenizationRequest	withAskConsumerConsent(Boolean value) Indicate if the tokenization form should contain a checkbox asking the user to give consent for storing their information for future payments.
CreateHostedTokenizationRequest	withLocale(String value) Locale used in the GUI towards the consumer.
CreateHostedTokenizationRequest	withPaymentProductFilters(PaymentProductFiltersHostedTokenization value) Contains the payment product ids that will be used for manipulating the payment products available for the payment to the customer.
CreateHostedTokenizationRequest	withTokens(String value) String containing comma separated tokens (no spaces) associated with the customer of this hosted session.
CreateHostedTokenizationRequest	withVariant(String value) Using the Back-Office it is possible to upload multiple templates of your HostedCheckout payment pages, including customized templates from Merchant Portal.

Methods inherited from class java.lang.Object

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

Constructor Detail

CreateHostedTokenizationRequest

public CreateHostedTokenizationRequest()

Method Detail

getAskConsumerConsent

public Boolean getAskConsumerConsent()

Indicate if the tokenization form should contain a checkbox asking the user to give consent for storing their information for future payments. If this parameter is false or missing, you should ask the user yourself and provide their answer when submitting the Tokenizer in your JavaScript code. To pass this choice set the submitTokenization function's parameter storePermanently to false, if you choose not to store the token for subsequent payments, or to true otherwise.

setAskConsumerConsent

public void setAskConsumerConsent(Boolean value)

Indicate if the tokenization form should contain a checkbox asking the user to give consent for storing their information for future payments. If this parameter is false or missing, you should ask the user yourself and provide their answer when submitting the Tokenizer in your JavaScript code. To pass this choice set the submitTokenization function's parameter storePermanently to false, if you choose not to store the token for subsequent payments, or to true otherwise.

withAskConsumerConsent

public CreateHostedTokenizationRequest withAskConsumerConsent(Boolean value)

Indicate if the tokenization form should contain a checkbox asking the user to give consent for storing their information for future payments. If this parameter is false or missing, you should ask the user yourself and provide their answer when submitting the Tokenizer in your JavaScript code. To pass this choice set the submitTokenization function's parameter storePermanently to false, if you choose not to store the token for subsequent payments, or to true otherwise.

getLocale

public String getLocale()

Locale used in the GUI towards the consumer.

setLocale

public void setLocale(String value)

Locale used in the GUI towards the consumer.

withLocale

public CreateHostedTokenizationRequest withLocale(String value)

Locale used in the GUI towards the consumer.

getPaymentProductFilters

public PaymentProductFiltersHostedTokenization getPaymentProductFilters()

Contains the payment product ids that will be used for manipulating the payment products available for the payment to the customer.

setPaymentProductFilters

public void setPaymentProductFilters(PaymentProductFiltersHostedTokenization value)

Contains the payment product ids that will be used for manipulating the payment products available for the payment to the customer.

withPaymentProductFilters

public CreateHostedTokenizationRequest withPaymentProductFilters(PaymentProductFiltersHostedTokenization value)

Contains the payment product ids that will be used for manipulating the payment products available for the payment to the customer.

getTokens

public String getTokens()

String containing comma separated tokens (no spaces) associated with the customer of this hosted session. Valid tokens will be used to present the customer the option to re-use previously used payment details. This means the customer for instance does not have to re-enter their card details again, which a big plus when the customer is using their mobile phone to complete the operation.

setTokens

public void setTokens(String value)

String containing comma separated tokens (no spaces) associated with the customer of this hosted session. Valid tokens will be used to present the customer the option to re-use previously used payment details. This means the customer for instance does not have to re-enter their card details again, which a big plus when the customer is using their mobile phone to complete the operation.

withTokens

public CreateHostedTokenizationRequest withTokens(String value)

String containing comma separated tokens (no spaces) associated with the customer of this hosted session. Valid tokens will be used to present the customer the option to re-use previously used payment details. This means the customer for instance does not have to re-enter their card details again, which a big plus when the customer is using their mobile phone to complete the operation.

getVariant

public String getVariant()

Using the Back-Office it is possible to upload multiple templates of your HostedCheckout payment pages, including customized templates from Merchant Portal. You can force the use of another template by specifying it in the variant field. This allows you to test out the effect of certain changes to your hostedcheckout pages in a controlled manner. Please note that you need to specify the filename of the template or customization.

setVariant

public void setVariant(String value)

Using the Back-Office it is possible to upload multiple templates of your HostedCheckout payment pages, including customized templates from Merchant Portal. You can force the use of another template by specifying it in the variant field. This allows you to test out the effect of certain changes to your hostedcheckout pages in a controlled manner. Please note that you need to specify the filename of the template or customization.

withVariant

public CreateHostedTokenizationRequest withVariant(String value)

Using the Back-Office it is possible to upload multiple templates of your HostedCheckout payment pages, including customized templates from Merchant Portal. You can force the use of another template by specifying it in the variant field. This allows you to test out the effect of certain changes to your hostedcheckout pages in a controlled manner. Please note that you need to specify the filename of the template or customization.