Class CardPaymentMethodSpecificInput
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptiontrue - Default - Allows subsequent payments to use PSD2 dynamic linking from this payment (including Card On File). false - Indicates that the dynamic linking (including Card On File data) will be ignored.Determines the type of the authorization that will be used.getCard()Object containing card detailsThe end date of the last scheduled payment in a series of transactions.Period of payment occurrence for recurring and installment payments.For cobranded cards, this field indicates the brand selection method: default - The holder implicitly accepted the default brand. alternative - The holder explicitly selected an alternative brand. notApplicable - The card is not cobranded.The unique scheme transactionId of the initial transaction that was performed with SCA.true - Indicates that the transactions is part of a scheduled recurring sequence.Container announcing forecoming subsequent payments.Object containing specific input required for CB paymentsObject containing specific input required for bancontact.Object containing specific input required for OneyDuplo Leroy Merlin payments.Object containing specific input required for OneyDuplo Alcampo payments.Payment product identifier - Please see Products documentation for a full overview of possible values.Object containing data related to recurringThe URL that the customer is redirect to after the payment flow has finished.This is the unique Scheme Reference Data from the initial transaction that was performed with a Strong Customer Authentication.Deprecated.Use threeDSecure.skipAuthentication instead.Object containing specific data regarding 3-D SecuregetToken()ID of the token to use to create the payment.Indicates if this transaction should be tokenized true - Tokenize the transaction.Indicates the channel via which the payment is created.Indicates which party initiated the unscheduled recurring transaction.first = This transaction is the first of a series of unscheduled recurring transactions subsequent = This transaction is a subsequent transaction in a series of unscheduled recurring transactions Note: this property is not allowed if isRecurring is true.voidsetAllowDynamicLinking(Boolean value) true - Default - Allows subsequent payments to use PSD2 dynamic linking from this payment (including Card On File). false - Indicates that the dynamic linking (including Card On File data) will be ignored.voidsetAuthorizationMode(String value) Determines the type of the authorization that will be used.voidObject containing card detailsvoidThe end date of the last scheduled payment in a series of transactions.voidPeriod of payment occurrence for recurring and installment payments.voidFor cobranded cards, this field indicates the brand selection method: default - The holder implicitly accepted the default brand. alternative - The holder explicitly selected an alternative brand. notApplicable - The card is not cobranded.voidvoidThe unique scheme transactionId of the initial transaction that was performed with SCA.voidsetIsRecurring(Boolean value) true - Indicates that the transactions is part of a scheduled recurring sequence.voidContainer announcing forecoming subsequent payments.voidObject containing specific input required for CB paymentsvoidObject containing specific input required for bancontact.voidObject containing specific input required for OneyDuplo Leroy Merlin payments.voidObject containing specific input required for OneyDuplo Alcampo payments.voidsetPaymentProductId(Integer value) Payment product identifier - Please see Products documentation for a full overview of possible values.voidObject containing data related to recurringvoidsetReturnUrl(String value) The URL that the customer is redirect to after the payment flow has finished.voidsetSchemeReferenceData(String value) This is the unique Scheme Reference Data from the initial transaction that was performed with a Strong Customer Authentication.voidsetSkipAuthentication(Boolean value) Deprecated.Use threeDSecure.skipAuthentication instead.voidsetThreeDSecure(ThreeDSecure value) Object containing specific data regarding 3-D SecurevoidID of the token to use to create the payment.voidsetTokenize(Boolean value) Indicates if this transaction should be tokenized true - Tokenize the transaction.voidsetTransactionChannel(String value) Indicates the channel via which the payment is created.voidIndicates which party initiated the unscheduled recurring transaction.voidfirst = This transaction is the first of a series of unscheduled recurring transactions subsequent = This transaction is a subsequent transaction in a series of unscheduled recurring transactions Note: this property is not allowed if isRecurring is true.withAllowDynamicLinking(Boolean value) true - Default - Allows subsequent payments to use PSD2 dynamic linking from this payment (including Card On File). false - Indicates that the dynamic linking (including Card On File data) will be ignored.withAuthorizationMode(String value) Determines the type of the authorization that will be used.Object containing card detailsThe end date of the last scheduled payment in a series of transactions.Period of payment occurrence for recurring and installment payments.For cobranded cards, this field indicates the brand selection method: default - The holder implicitly accepted the default brand. alternative - The holder explicitly selected an alternative brand. notApplicable - The card is not cobranded.The unique scheme transactionId of the initial transaction that was performed with SCA.withIsRecurring(Boolean value) true - Indicates that the transactions is part of a scheduled recurring sequence.Container announcing forecoming subsequent payments.Object containing specific input required for CB paymentsObject containing specific input required for bancontact.Object containing specific input required for OneyDuplo Leroy Merlin payments.Object containing specific input required for OneyDuplo Alcampo payments.withPaymentProductId(Integer value) Payment product identifier - Please see Products documentation for a full overview of possible values.Object containing data related to recurringwithReturnUrl(String value) The URL that the customer is redirect to after the payment flow has finished.withSchemeReferenceData(String value) This is the unique Scheme Reference Data from the initial transaction that was performed with a Strong Customer Authentication.withSkipAuthentication(Boolean value) Deprecated.Use threeDSecure.skipAuthentication instead.withThreeDSecure(ThreeDSecure value) Object containing specific data regarding 3-D SecureID of the token to use to create the payment.withTokenize(Boolean value) Indicates if this transaction should be tokenized true - Tokenize the transaction.withTransactionChannel(String value) Indicates the channel via which the payment is created.Indicates which party initiated the unscheduled recurring transaction.first = This transaction is the first of a series of unscheduled recurring transactions subsequent = This transaction is a subsequent transaction in a series of unscheduled recurring transactions Note: this property is not allowed if isRecurring is true.
-
Constructor Details
-
CardPaymentMethodSpecificInput
public CardPaymentMethodSpecificInput()
-
-
Method Details
-
getAllowDynamicLinking
- true - Default - Allows subsequent payments to use PSD2 dynamic linking from this payment (including Card On File).
- false - Indicates that the dynamic linking (including Card On File data) will be ignored.
-
setAllowDynamicLinking
- true - Default - Allows subsequent payments to use PSD2 dynamic linking from this payment (including Card On File).
- false - Indicates that the dynamic linking (including Card On File data) will be ignored.
-
withAllowDynamicLinking
- true - Default - Allows subsequent payments to use PSD2 dynamic linking from this payment (including Card On File).
- false - Indicates that the dynamic linking (including Card On File data) will be ignored.
-
getAuthorizationMode
Determines the type of the authorization that will be used. Allowed values:- FINAL_AUTHORIZATION - The payment creation results in an authorization that is ready for capture. Final authorizations can't be reversed and need to be captured for the full amount within 7 days.
- PRE_AUTHORIZATION - The payment creation results in a pre-authorization that is ready for capture. Pre-authortizations can be reversed and can be captured within 30 days. The capture amount can be lower than the authorized amount.
- SALE - The payment creation results in an authorization that is already captured at the moment of approval.
Only used with some acquirers, ignored for acquirers that do not support this. In case the acquirer does not allow this to be specified the authorizationMode is 'unspecified', which behaves similar to a final authorization.
-
setAuthorizationMode
Determines the type of the authorization that will be used. Allowed values:- FINAL_AUTHORIZATION - The payment creation results in an authorization that is ready for capture. Final authorizations can't be reversed and need to be captured for the full amount within 7 days.
- PRE_AUTHORIZATION - The payment creation results in a pre-authorization that is ready for capture. Pre-authortizations can be reversed and can be captured within 30 days. The capture amount can be lower than the authorized amount.
- SALE - The payment creation results in an authorization that is already captured at the moment of approval.
Only used with some acquirers, ignored for acquirers that do not support this. In case the acquirer does not allow this to be specified the authorizationMode is 'unspecified', which behaves similar to a final authorization.
-
withAuthorizationMode
Determines the type of the authorization that will be used. Allowed values:- FINAL_AUTHORIZATION - The payment creation results in an authorization that is ready for capture. Final authorizations can't be reversed and need to be captured for the full amount within 7 days.
- PRE_AUTHORIZATION - The payment creation results in a pre-authorization that is ready for capture. Pre-authortizations can be reversed and can be captured within 30 days. The capture amount can be lower than the authorized amount.
- SALE - The payment creation results in an authorization that is already captured at the moment of approval.
Only used with some acquirers, ignored for acquirers that do not support this. In case the acquirer does not allow this to be specified the authorizationMode is 'unspecified', which behaves similar to a final authorization.
-
getCard
Object containing card details -
setCard
Object containing card details -
withCard
Object containing card details -
getCardOnFileRecurringExpiration
The end date of the last scheduled payment in a series of transactions. Format YYYYMMDD -
setCardOnFileRecurringExpiration
The end date of the last scheduled payment in a series of transactions. Format YYYYMMDD -
withCardOnFileRecurringExpiration
The end date of the last scheduled payment in a series of transactions. Format YYYYMMDD -
getCardOnFileRecurringFrequency
Period of payment occurrence for recurring and installment payments. Allowed values:- Yearly
- Quarterly
- Monthly
- Weekly
- Daily
-
setCardOnFileRecurringFrequency
Period of payment occurrence for recurring and installment payments. Allowed values:- Yearly
- Quarterly
- Monthly
- Weekly
- Daily
-
withCardOnFileRecurringFrequency
Period of payment occurrence for recurring and installment payments. Allowed values:- Yearly
- Quarterly
- Monthly
- Weekly
- Daily
-
getCobrandSelectionIndicator
For cobranded cards, this field indicates the brand selection method:- default - The holder implicitly accepted the default brand.
- alternative - The holder explicitly selected an alternative brand.
- notApplicable - The card is not cobranded.
-
setCobrandSelectionIndicator
For cobranded cards, this field indicates the brand selection method:- default - The holder implicitly accepted the default brand.
- alternative - The holder explicitly selected an alternative brand.
- notApplicable - The card is not cobranded.
-
withCobrandSelectionIndicator
For cobranded cards, this field indicates the brand selection method:- default - The holder implicitly accepted the default brand.
- alternative - The holder explicitly selected an alternative brand.
- notApplicable - The card is not cobranded.
-
getCurrencyConversion
-
setCurrencyConversion
-
withCurrencyConversion
-
getInitialSchemeTransactionId
The unique scheme transactionId of the initial transaction that was performed with SCA. In case this is unknown a scheme transactionId of an earlier transaction part of the same sequence can be used as a fall-back. Strongly advised to be submitted for any MerchantInitiated or recurring transaction (a subsequent one). -
setInitialSchemeTransactionId
The unique scheme transactionId of the initial transaction that was performed with SCA. In case this is unknown a scheme transactionId of an earlier transaction part of the same sequence can be used as a fall-back. Strongly advised to be submitted for any MerchantInitiated or recurring transaction (a subsequent one). -
withInitialSchemeTransactionId
The unique scheme transactionId of the initial transaction that was performed with SCA. In case this is unknown a scheme transactionId of an earlier transaction part of the same sequence can be used as a fall-back. Strongly advised to be submitted for any MerchantInitiated or recurring transaction (a subsequent one). -
getIsRecurring
- true - Indicates that the transactions is part of a scheduled recurring sequence. In addition, recurringPaymentSequenceIndicator indicates if the transaction is the first or subsequent in a recurring sequence.
- false - Indicates that the transaction is not part of a scheduled recurring sequence. The default value for this property is false.
-
setIsRecurring
- true - Indicates that the transactions is part of a scheduled recurring sequence. In addition, recurringPaymentSequenceIndicator indicates if the transaction is the first or subsequent in a recurring sequence.
- false - Indicates that the transaction is not part of a scheduled recurring sequence. The default value for this property is false.
-
withIsRecurring
- true - Indicates that the transactions is part of a scheduled recurring sequence. In addition, recurringPaymentSequenceIndicator indicates if the transaction is the first or subsequent in a recurring sequence.
- false - Indicates that the transaction is not part of a scheduled recurring sequence. The default value for this property is false.
-
getMultiplePaymentInformation
Container announcing forecoming subsequent payments. Holds modalities of these subsequent payments. -
setMultiplePaymentInformation
Container announcing forecoming subsequent payments. Holds modalities of these subsequent payments. -
withMultiplePaymentInformation
public CardPaymentMethodSpecificInput withMultiplePaymentInformation(MultiplePaymentInformation value) Container announcing forecoming subsequent payments. Holds modalities of these subsequent payments. -
getPaymentProduct130SpecificInput
Object containing specific input required for CB payments -
setPaymentProduct130SpecificInput
Object containing specific input required for CB payments -
withPaymentProduct130SpecificInput
public CardPaymentMethodSpecificInput withPaymentProduct130SpecificInput(PaymentProduct130SpecificInput value) Object containing specific input required for CB payments -
getPaymentProduct3012SpecificInput
Object containing specific input required for bancontact. -
setPaymentProduct3012SpecificInput
Object containing specific input required for bancontact. -
withPaymentProduct3012SpecificInput
public CardPaymentMethodSpecificInput withPaymentProduct3012SpecificInput(PaymentProduct3012SpecificInput value) Object containing specific input required for bancontact. -
getPaymentProduct3208SpecificInput
Object containing specific input required for OneyDuplo Leroy Merlin payments. -
setPaymentProduct3208SpecificInput
Object containing specific input required for OneyDuplo Leroy Merlin payments. -
withPaymentProduct3208SpecificInput
public CardPaymentMethodSpecificInput withPaymentProduct3208SpecificInput(PaymentProduct3208SpecificInput value) Object containing specific input required for OneyDuplo Leroy Merlin payments. -
getPaymentProduct3209SpecificInput
Object containing specific input required for OneyDuplo Alcampo payments. -
setPaymentProduct3209SpecificInput
Object containing specific input required for OneyDuplo Alcampo payments. -
withPaymentProduct3209SpecificInput
public CardPaymentMethodSpecificInput withPaymentProduct3209SpecificInput(PaymentProduct3209SpecificInput value) Object containing specific input required for OneyDuplo Alcampo payments. -
getPaymentProductId
Payment product identifier - Please see Products documentation for a full overview of possible values. -
setPaymentProductId
Payment product identifier - Please see Products documentation for a full overview of possible values. -
withPaymentProductId
Payment product identifier - Please see Products documentation for a full overview of possible values. -
getRecurring
Object containing data related to recurring -
setRecurring
Object containing data related to recurring -
withRecurring
Object containing data related to recurring -
getReturnUrl
The URL that the customer is redirect to after the payment flow has finished. You can add any number of key value pairs in the query string that, for instance help you to identify the customer when they return to your site. Please note that we will also append some additional key value pairs that will also help you with this identification process. Note: The provided URL should be absolute and contain the protocol to use, e.g. http:// or https://. For use on mobile devices a custom protocol can be used in the form of protocol://. This protocol must be registered on the device first. URLs without a protocol will be rejected. -
setReturnUrl
The URL that the customer is redirect to after the payment flow has finished. You can add any number of key value pairs in the query string that, for instance help you to identify the customer when they return to your site. Please note that we will also append some additional key value pairs that will also help you with this identification process. Note: The provided URL should be absolute and contain the protocol to use, e.g. http:// or https://. For use on mobile devices a custom protocol can be used in the form of protocol://. This protocol must be registered on the device first. URLs without a protocol will be rejected. -
withReturnUrl
The URL that the customer is redirect to after the payment flow has finished. You can add any number of key value pairs in the query string that, for instance help you to identify the customer when they return to your site. Please note that we will also append some additional key value pairs that will also help you with this identification process. Note: The provided URL should be absolute and contain the protocol to use, e.g. http:// or https://. For use on mobile devices a custom protocol can be used in the form of protocol://. This protocol must be registered on the device first. URLs without a protocol will be rejected. -
getSchemeReferenceData
This is the unique Scheme Reference Data from the initial transaction that was performed with a Strong Customer Authentication. In case this value is unknown, a Scheme Reference of an earlier transaction that was part of the same sequence can be used as a fall-back. Still, it is strongly advised to submit this value for any Merchant Initiated Transaction or any recurring transaction (hereby defined as "Subsequent"). -
setSchemeReferenceData
This is the unique Scheme Reference Data from the initial transaction that was performed with a Strong Customer Authentication. In case this value is unknown, a Scheme Reference of an earlier transaction that was part of the same sequence can be used as a fall-back. Still, it is strongly advised to submit this value for any Merchant Initiated Transaction or any recurring transaction (hereby defined as "Subsequent"). -
withSchemeReferenceData
This is the unique Scheme Reference Data from the initial transaction that was performed with a Strong Customer Authentication. In case this value is unknown, a Scheme Reference of an earlier transaction that was part of the same sequence can be used as a fall-back. Still, it is strongly advised to submit this value for any Merchant Initiated Transaction or any recurring transaction (hereby defined as "Subsequent"). -
getSkipAuthentication
Deprecated.Use threeDSecure.skipAuthentication instead. * true = 3D Secure authentication will be skipped for this transaction. This setting should be used when isRecurring is set to true and recurringPaymentSequenceIndicator is set to recurring. * false = 3D Secure authentication will not be skipped for this transaction. Note: This is only possible if your account in our system is setup for 3D Secure authentication and if your configuration in our system allows you to override it per transaction.Deprecated: Use threeDSecure.skipAuthentication instead.- true = 3D Secure authentication will be skipped for this transaction. This setting should be used when isRecurring is set to true and recurringPaymentSequenceIndicator is set to recurring.
- false = 3D Secure authentication will not be skipped for this transaction.
Note: This is only possible if your account in our system is setup for 3D Secure authentication and if your configuration in our system allows you to override it per transaction.
-
setSkipAuthentication
Deprecated.Use threeDSecure.skipAuthentication instead. * true = 3D Secure authentication will be skipped for this transaction. This setting should be used when isRecurring is set to true and recurringPaymentSequenceIndicator is set to recurring. * false = 3D Secure authentication will not be skipped for this transaction. Note: This is only possible if your account in our system is setup for 3D Secure authentication and if your configuration in our system allows you to override it per transaction.Deprecated: Use threeDSecure.skipAuthentication instead.- true = 3D Secure authentication will be skipped for this transaction. This setting should be used when isRecurring is set to true and recurringPaymentSequenceIndicator is set to recurring.
- false = 3D Secure authentication will not be skipped for this transaction.
Note: This is only possible if your account in our system is setup for 3D Secure authentication and if your configuration in our system allows you to override it per transaction.
-
withSkipAuthentication
Deprecated.Use threeDSecure.skipAuthentication instead. * true = 3D Secure authentication will be skipped for this transaction. This setting should be used when isRecurring is set to true and recurringPaymentSequenceIndicator is set to recurring. * false = 3D Secure authentication will not be skipped for this transaction. Note: This is only possible if your account in our system is setup for 3D Secure authentication and if your configuration in our system allows you to override it per transaction.Deprecated: Use threeDSecure.skipAuthentication instead.- true = 3D Secure authentication will be skipped for this transaction. This setting should be used when isRecurring is set to true and recurringPaymentSequenceIndicator is set to recurring.
- false = 3D Secure authentication will not be skipped for this transaction.
Note: This is only possible if your account in our system is setup for 3D Secure authentication and if your configuration in our system allows you to override it per transaction.
-
getThreeDSecure
Object containing specific data regarding 3-D Secure -
setThreeDSecure
Object containing specific data regarding 3-D Secure -
withThreeDSecure
Object containing specific data regarding 3-D Secure -
getToken
ID of the token to use to create the payment. -
setToken
ID of the token to use to create the payment. -
withToken
ID of the token to use to create the payment. -
getTokenize
Indicates if this transaction should be tokenized- true - Tokenize the transaction. Note that a payment on the payment platform that results in a status REDIRECTED cannot be tokenized in this way.
- false - Do not tokenize the transaction, unless it would be tokenized by other means such as auto-tokenization of recurring payments.
-
setTokenize
Indicates if this transaction should be tokenized- true - Tokenize the transaction. Note that a payment on the payment platform that results in a status REDIRECTED cannot be tokenized in this way.
- false - Do not tokenize the transaction, unless it would be tokenized by other means such as auto-tokenization of recurring payments.
-
withTokenize
Indicates if this transaction should be tokenized- true - Tokenize the transaction. Note that a payment on the payment platform that results in a status REDIRECTED cannot be tokenized in this way.
- false - Do not tokenize the transaction, unless it would be tokenized by other means such as auto-tokenization of recurring payments.
-
getTransactionChannel
Indicates the channel via which the payment is created. Allowed values:- ECOMMERCE - The transaction is a regular E-Commerce transaction.
- MOTO - The transaction is a Mail Order/Telephone Order.
Defaults to ECOMMERCE.
-
setTransactionChannel
Indicates the channel via which the payment is created. Allowed values:- ECOMMERCE - The transaction is a regular E-Commerce transaction.
- MOTO - The transaction is a Mail Order/Telephone Order.
Defaults to ECOMMERCE.
-
withTransactionChannel
Indicates the channel via which the payment is created. Allowed values:- ECOMMERCE - The transaction is a regular E-Commerce transaction.
- MOTO - The transaction is a Mail Order/Telephone Order.
Defaults to ECOMMERCE.
-
getUnscheduledCardOnFileRequestor
Indicates which party initiated the unscheduled recurring transaction. Allowed values:- merchantInitiated - Merchant Initiated Transaction.
- cardholderInitiated - Cardholder Initiated Transaction. Note:
- This property is not allowed if isRecurring is true.
- When a customer has chosen to use a token on a hosted checkout this property is set to "cardholderInitiated".
-
setUnscheduledCardOnFileRequestor
Indicates which party initiated the unscheduled recurring transaction. Allowed values:- merchantInitiated - Merchant Initiated Transaction.
- cardholderInitiated - Cardholder Initiated Transaction. Note:
- This property is not allowed if isRecurring is true.
- When a customer has chosen to use a token on a hosted checkout this property is set to "cardholderInitiated".
-
withUnscheduledCardOnFileRequestor
Indicates which party initiated the unscheduled recurring transaction. Allowed values:- merchantInitiated - Merchant Initiated Transaction.
- cardholderInitiated - Cardholder Initiated Transaction. Note:
- This property is not allowed if isRecurring is true.
- When a customer has chosen to use a token on a hosted checkout this property is set to "cardholderInitiated".
-
getUnscheduledCardOnFileSequenceIndicator
- first = This transaction is the first of a series of unscheduled recurring transactions
- subsequent = This transaction is a subsequent transaction in a series of unscheduled recurring transactions Note: this property is not allowed if isRecurring is true.
-
setUnscheduledCardOnFileSequenceIndicator
- first = This transaction is the first of a series of unscheduled recurring transactions
- subsequent = This transaction is a subsequent transaction in a series of unscheduled recurring transactions Note: this property is not allowed if isRecurring is true.
-
withUnscheduledCardOnFileSequenceIndicator
- first = This transaction is the first of a series of unscheduled recurring transactions
- subsequent = This transaction is a subsequent transaction in a series of unscheduled recurring transactions Note: this property is not allowed if isRecurring is true.
-