Package com.broadleafcommerce.vendor.chasepayment.service.hps.autoconfigure

Class HPSValidationDiscriminatedProperties

java.lang.Object

com.broadleafcommerce.paymentgateway.properties.DiscriminatedProperties<HPSValidationDiscriminatedProperties>

com.broadleafcommerce.vendor.chasepayment.service.hps.autoconfigure.HPSValidationDiscriminatedProperties

@ConfigurationProperties("broadleaf.chase-payment.hps.validation.discriminated")
public class HPSValidationDiscriminatedProperties
extends com.broadleafcommerce.paymentgateway.properties.DiscriminatedProperties<HPSValidationDiscriminatedProperties>

Configuration properties configuring validation behavior around HPS.

Constructor Summary

Constructors

Constructor	Description
HPSValidationDiscriminatedProperties()

Method Summary

Modifier and Type	Method	Description
boolean	getValidateHpsProfileAndBlcPaymentContextConsistency(String applicationId, String tenantId)
boolean	getValidateHpsProfileAndBlcPaymentOwnerConsistency(String applicationId, String tenantId)
protected void	logUnresolvedPropertyError(String propertyFriendlyName, String propertyPath, String applicationId, String tenantId)
void	setValidateHpsProfileAndBlcPaymentContextConsistency(boolean validateHpsProfileAndBlcPaymentContextConsistency)	By default, when the HPS init request is initially made, our backend will track a minimal representation of the ContextRequest in the HPS metadata.
void	setValidateHpsProfileAndBlcPaymentOwnerConsistency(boolean validateHpsProfileAndBlcPaymentOwnerConsistency)	By default, when the HPS init request is initially made, our backend will track a minimal representation of the intended payment owner type and payment owner ID in the HPS metadata.

Methods inherited from class com.broadleafcommerce.paymentgateway.properties.DiscriminatedProperties

getApplication, getField, getTenant, setApplication, setTenant

Methods inherited from class java.lang.Object

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

Constructor Details

HPSValidationDiscriminatedProperties

public HPSValidationDiscriminatedProperties()

Method Details

getValidateHpsProfileAndBlcPaymentContextConsistency

public boolean getValidateHpsProfileAndBlcPaymentContextConsistency(@Nullable
 String applicationId,
 @Nullable
 String tenantId)

getValidateHpsProfileAndBlcPaymentOwnerConsistency

public boolean getValidateHpsProfileAndBlcPaymentOwnerConsistency(@Nullable
 String applicationId,
 @Nullable
 String tenantId)

logUnresolvedPropertyError

protected void logUnresolvedPropertyError(String propertyFriendlyName,
 String propertyPath,
 @Nullable
 String applicationId,
 @Nullable
 String tenantId)

setValidateHpsProfileAndBlcPaymentContextConsistency

public void setValidateHpsProfileAndBlcPaymentContextConsistency(boolean validateHpsProfileAndBlcPaymentContextConsistency)

By default, when the HPS init request is initially made, our backend will track a minimal representation of the ContextRequest in the HPS metadata. After the customer submits the HPS form/page, the next step is typically to create a BLC Payment object with the results. When this flag is enabled, at BLC Payment creation time, the backend will verify that the recorded ContextRequest information for the HPS interaction matches the context that the BLC Payment is being created in. This ensures an HPS profile created for a different application/tenant cannot be used to create a BLC Payment in a different application/tenant. When this flag is disabled, that verification is skipped.

setValidateHpsProfileAndBlcPaymentOwnerConsistency

public void setValidateHpsProfileAndBlcPaymentOwnerConsistency(boolean validateHpsProfileAndBlcPaymentOwnerConsistency)

By default, when the HPS init request is initially made, our backend will track a minimal representation of the intended payment owner type and payment owner ID in the HPS metadata. After the customer submits the HPS form/page, the next step is typically to create a BLC Payment object with the results. When this flag is enabled, at BLC Payment creation time, the backend will verify that the recorded payment owner information for the HPS interaction matches the payment owner information that the BLC Payment is being created for. This ensures, for example, that a profile created for cartX cannot be used to create a payment for cartY. When this flag is disabled, that verification is skipped.