com.ingenico.connect.gateway.sdk.java.domain.payment.definitions.MobilePaymentMethodSpecificInput Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of connect-sdk-java Show documentation
Show all versions of connect-sdk-java Show documentation
SDK to communicate with the Ingenico ePayments platform using the Ingenico Connect Server API
/*
* This class was auto-generated from the API references found at
* https://epayments-api.developer-ingenico.com/s2sapi/v1/
*/
package com.ingenico.connect.gateway.sdk.java.domain.payment.definitions;
import com.ingenico.connect.gateway.sdk.java.domain.definitions.AbstractPaymentMethodSpecificInput;
public class MobilePaymentMethodSpecificInput extends AbstractPaymentMethodSpecificInput {
private String authorizationMode = null;
private DecryptedPaymentData decryptedPaymentData = null;
private String encryptedPaymentData = null;
private MobilePaymentProduct320SpecificInput paymentProduct320SpecificInput = null;
private Boolean requiresApproval = null;
private Boolean skipFraudService = null;
private String transactionId = null;
/**
* 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.
*/
public String getAuthorizationMode() {
return authorizationMode;
}
/**
* 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.
*/
public void setAuthorizationMode(String value) {
this.authorizationMode = value;
}
/**
* The payment data if you want to do the decryption of the vendor's encrypted payment data yourself.
* Typically you'd use encryptedCustomerInput in the root of the create payment request to provide the payment data for mobile payment methods.
* Only when you do not do this you need to use either this field or encryptedPaymentData, depending on who should do the decryption of the vendor's encrypted payment data.
*/
public DecryptedPaymentData getDecryptedPaymentData() {
return decryptedPaymentData;
}
/**
* The payment data if you want to do the decryption of the vendor's encrypted payment data yourself.
* Typically you'd use encryptedCustomerInput in the root of the create payment request to provide the payment data for mobile payment methods.
* Only when you do not do this you need to use either this field or encryptedPaymentData, depending on who should do the decryption of the vendor's encrypted payment data.
*/
public void setDecryptedPaymentData(DecryptedPaymentData value) {
this.decryptedPaymentData = value;
}
/**
* The payment data if you want to let us do the decryption of the vendor's encrypted payment data.
* Typically you'd use encryptedCustomerInput in the root of the create payment request to provide the payment data for mobile payment methods.
* Only when you do not do this you need to use either this field or decryptedPaymentData, depending on who should do the decryption of the vendor's encrypted payment data.
* This maps to the following field in the vendor's encrypted payment data:
*
* - Apple Pay: PKPayment.token.paymentData
*
- Android Pay: FullWallet.paymentMethodToken.token
*
*/
public String getEncryptedPaymentData() {
return encryptedPaymentData;
}
/**
* The payment data if you want to let us do the decryption of the vendor's encrypted payment data.
* Typically you'd use encryptedCustomerInput in the root of the create payment request to provide the payment data for mobile payment methods.
* Only when you do not do this you need to use either this field or decryptedPaymentData, depending on who should do the decryption of the vendor's encrypted payment data.
* This maps to the following field in the vendor's encrypted payment data:
*
* - Apple Pay: PKPayment.token.paymentData
*
- Android Pay: FullWallet.paymentMethodToken.token
*
*/
public void setEncryptedPaymentData(String value) {
this.encryptedPaymentData = value;
}
/**
* Android Pay (payment product 320) specific details.
*/
public MobilePaymentProduct320SpecificInput getPaymentProduct320SpecificInput() {
return paymentProduct320SpecificInput;
}
/**
* Android Pay (payment product 320) specific details.
*/
public void setPaymentProduct320SpecificInput(MobilePaymentProduct320SpecificInput value) {
this.paymentProduct320SpecificInput = 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
*
*/
public Boolean getRequiresApproval() {
return requiresApproval;
}
/**
* - 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
*
*/
public void setRequiresApproval(Boolean value) {
this.requiresApproval = 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.
*/
public Boolean getSkipFraudService() {
return skipFraudService;
}
/**
* - 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.
*/
public void setSkipFraudService(Boolean value) {
this.skipFraudService = value;
}
/**
* The vendor's transaction id. This maps to the following field in the vendor's encrypted payment data:
*
* - Apple Pay: PKPayment.token.transactionIdentifier
*
- Android Pay: FullWallet.googleTransactionId
*
*/
public String getTransactionId() {
return transactionId;
}
/**
* The vendor's transaction id. This maps to the following field in the vendor's encrypted payment data:
*
* - Apple Pay: PKPayment.token.transactionIdentifier
*
- Android Pay: FullWallet.googleTransactionId
*
*/
public void setTransactionId(String value) {
this.transactionId = value;
}
}