com.worldline.connect.sdk.java.v1.domain

Class MobilePaymentMethodSpecificInput

java.lang.Object

com.worldline.connect.sdk.java.v1.domain.AbstractPaymentMethodSpecificInput

com.worldline.connect.sdk.java.v1.domain.MobilePaymentMethodSpecificInput

public class MobilePaymentMethodSpecificInput
extends AbstractPaymentMethodSpecificInput

Constructor Summary

Constructors

Constructor and Description
MobilePaymentMethodSpecificInput()

Method Summary

Modifier and Type	Method and Description
String	getAuthorizationMode() Determines the type of the authorization that will be used.
String	getCustomerReference() Reference of the customer for the payment (purchase order #, etc.).
DecryptedPaymentData	getDecryptedPaymentData() The payment data if you do the decryption of the encrypted payment data yourself.
String	getEncryptedPaymentData() The payment data if we will do the decryption of the encrypted payment data.
MobilePaymentProduct320SpecificInput	getPaymentProduct320SpecificInput() Object containing information specific to Google Pay
Boolean	getRequiresApproval() true = the payment requires approval before the funds will be captured using the Approve payment or Capture payment API false = the payment does not require approval, and the funds will be captured automatically
Boolean	getSkipFraudService() true = Fraud scoring will be skipped for this transaction false = Fraud scoring will not be skipped for this transaction Note: This is only possible if your account in our system is setup for Fraud scoring and if your configuration in our system allows you to override it per transaction.
void	setAuthorizationMode(String value) Determines the type of the authorization that will be used.
void	setCustomerReference(String value) Reference of the customer for the payment (purchase order #, etc.).
void	setDecryptedPaymentData(DecryptedPaymentData value) The payment data if you do the decryption of the encrypted payment data yourself.
void	setEncryptedPaymentData(String value) The payment data if we will do the decryption of the encrypted payment data.
void	setPaymentProduct320SpecificInput(MobilePaymentProduct320SpecificInput value) Object containing information specific to Google Pay
void	setRequiresApproval(Boolean value) true = the payment requires approval before the funds will be captured using the Approve payment or Capture payment API false = the payment does not require approval, and the funds will be captured automatically
void	setSkipFraudService(Boolean value) true = Fraud scoring will be skipped for this transaction false = Fraud scoring will not be skipped for this transaction Note: This is only possible if your account in our system is setup for Fraud scoring and if your configuration in our system allows you to override it per transaction.

Methods inherited from class com.worldline.connect.sdk.java.v1.domain.AbstractPaymentMethodSpecificInput

getPaymentProductId, setPaymentProductId

Methods inherited from class java.lang.Object

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

Constructor Detail

MobilePaymentMethodSpecificInput

public MobilePaymentMethodSpecificInput()

Method Detail

getAuthorizationMode

public String 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, ingnored for acquirers that don't support this. In case the acquirer doesn't allow this to be specified the authorizationMode is 'unspecified', which behaves similar to a final authorization.

setAuthorizationMode

public void setAuthorizationMode(String value)

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, ingnored for acquirers that don't support this. In case the acquirer doesn't allow this to be specified the authorizationMode is 'unspecified', which behaves similar to a final authorization.

getCustomerReference

public String getCustomerReference()

Reference of the customer for the payment (purchase order #, etc.). Only used with some acquirers.

setCustomerReference

public void setCustomerReference(String value)

Reference of the customer for the payment (purchase order #, etc.). Only used with some acquirers.

getDecryptedPaymentData

public DecryptedPaymentData getDecryptedPaymentData()

The payment data if you do the decryption of the encrypted payment data yourself.

setDecryptedPaymentData

public void setDecryptedPaymentData(DecryptedPaymentData value)

The payment data if you do the decryption of the encrypted payment data yourself.

getEncryptedPaymentData

public String getEncryptedPaymentData()

The payment data if we will do the decryption of the encrypted payment data.

Typically you'd use encryptedCustomerInput in the root of the create payment request to provide the encrypted payment data instead.

• For Apple Pay, the encrypted payment data is the PKPayment.token.paymentData object passed as a string (with all quotation marks escaped).
• For Google Pay, the encrypted payment data can be found in property paymentMethodData.tokenizationData.token of the PaymentData.toJson() result.

setEncryptedPaymentData

public void setEncryptedPaymentData(String value)

The payment data if we will do the decryption of the encrypted payment data.

Typically you'd use encryptedCustomerInput in the root of the create payment request to provide the encrypted payment data instead.

• For Apple Pay, the encrypted payment data is the PKPayment.token.paymentData object passed as a string (with all quotation marks escaped).
• For Google Pay, the encrypted payment data can be found in property paymentMethodData.tokenizationData.token of the PaymentData.toJson() result.

getPaymentProduct320SpecificInput

public MobilePaymentProduct320SpecificInput getPaymentProduct320SpecificInput()

Object containing information specific to Google Pay

setPaymentProduct320SpecificInput

public void setPaymentProduct320SpecificInput(MobilePaymentProduct320SpecificInput value)

Object containing information specific to Google Pay

getRequiresApproval

public Boolean getRequiresApproval()

• true = the payment requires approval before the funds will be captured using the Approve payment or Capture payment API
• false = the payment does not require approval, and the funds will be captured automatically

setRequiresApproval

public void setRequiresApproval(Boolean value)

• true = the payment requires approval before the funds will be captured using the Approve payment or Capture payment API
• false = the payment does not require approval, and the funds will be captured automatically

getSkipFraudService

public Boolean getSkipFraudService()

• true = Fraud scoring will be skipped for this transaction
• false = Fraud scoring will not be skipped for this transaction

Note: This is only possible if your account in our system is setup for Fraud scoring and if your configuration in our system allows you to override it per transaction.

setSkipFraudService

public void setSkipFraudService(Boolean value)

• true = Fraud scoring will be skipped for this transaction
• false = Fraud scoring will not be skipped for this transaction

Note: This is only possible if your account in our system is setup for Fraud scoring and if your configuration in our system allows you to override it per transaction.