Package com.broadleafcommerce.payment.service.gateway.autoconfigure

Class ChaseOrbitalGatewayConfigurationProperties

java.lang.Object
com.broadleafcommerce.payment.service.gateway.autoconfigure.ChaseOrbitalGatewayConfigurationProperties
@ConfigurationProperties("broadleaf.chase-payment.orbital-gateway.gateway-config") public class ChaseOrbitalGatewayConfigurationProperties extends Object
Properties specifically relevant for ChaseOrbitalGatewayConfiguration. This is not a catch-all ConfigurationProperties class.

  • Constructor Details

    • ChaseOrbitalGatewayConfigurationProperties

      public ChaseOrbitalGatewayConfigurationProperties()

  • Method Details

    • getGatewayReferenceForTransactionIdAndType

      @Nullable public String getGatewayReferenceForTransactionIdAndType(String transactionType)

    • getFailureReportingThreshold

      public int getFailureReportingThreshold()
      This represents the number of failed API interactions that can occur with the Orbital Gateway before the service is considered to be 'down'.
      See Also:

    • getSupportedTransactionTypes

      public Set<String> getSupportedTransactionTypes()
      See Also:
      • PaymentGatewayConfiguration.getSupportedTransactionTypes()

    • getSupportedFeatures

      public Set<String> getSupportedFeatures()

      Note - Chase partial capture documentation does mention that if a partial capture is executed, the Orbital Gateway does do a local authorization reversal for the uncaptured amount. But they are clear in stating "This authorization reversal does not go to the payment brands as its local to the Orbital Gateway". Thus, we do not include DefaultGatewayFeatureType.FORCED_REVERSE_AUTH_WITH_PARTIAL_CAPTURE in our supported features list.

      Note - Chase does offer Managed Billing for recurring payments, but as of the initial implementation of this integration, this is not a feature that is being leveraged. Thus, we do not include DefaultGatewayFeatureType.RECURRING_PAYMENTS

      Note - By default, when using HPS to create profiles with CIT type as 'CSTO', the Orbital profile stored by Chase can theoretically be used for multiple orders (each order would use CIT type 'CUSE' when authorizing). For this reason, DefaultGatewayFeatureType.MULTI_USE_PAYMENT_METHODS is declared as supported. However, as of the initial implementation of this integration, profiles are used only in the scope of 1 order (1 auth/auth-capture) and profile 'management' is not supported/exposed anywhere by the system (this is why DefaultGatewayFeatureType.SAVED_PAYMENTS is declared as unsupported). Furthermore, the tokens received from Digital Wallets such as Apple Pay are single-use anyway, so cannot be used for more than one authorization.

      See Also:
      • PaymentGatewayConfiguration.getSupportedFeatures()

    • getGatewayType

      public String getGatewayType()
      See Also:
      • PaymentGatewayTypeAware.getGatewayType()

    • getGatewayReferenceForTransactionId

      public Map<String,String> getGatewayReferenceForTransactionId()
      See Also:
      • PaymentGatewayConfiguration.getGatewayReferenceForTransactionIdByType(String)

    • setFailureReportingThreshold

      public void setFailureReportingThreshold(int failureReportingThreshold)
      This represents the number of failed API interactions that can occur with the Orbital Gateway before the service is considered to be 'down'.
      See Also:

    • setSupportedTransactionTypes

      public void setSupportedTransactionTypes(Set<String> supportedTransactionTypes)
      See Also:
      • PaymentGatewayConfiguration.getSupportedTransactionTypes()

    • setSupportedFeatures

      public void setSupportedFeatures(Set<String> supportedFeatures)

      Note - Chase partial capture documentation does mention that if a partial capture is executed, the Orbital Gateway does do a local authorization reversal for the uncaptured amount. But they are clear in stating "This authorization reversal does not go to the payment brands as its local to the Orbital Gateway". Thus, we do not include DefaultGatewayFeatureType.FORCED_REVERSE_AUTH_WITH_PARTIAL_CAPTURE in our supported features list.

      Note - Chase does offer Managed Billing for recurring payments, but as of the initial implementation of this integration, this is not a feature that is being leveraged. Thus, we do not include DefaultGatewayFeatureType.RECURRING_PAYMENTS

      Note - By default, when using HPS to create profiles with CIT type as 'CSTO', the Orbital profile stored by Chase can theoretically be used for multiple orders (each order would use CIT type 'CUSE' when authorizing). For this reason, DefaultGatewayFeatureType.MULTI_USE_PAYMENT_METHODS is declared as supported. However, as of the initial implementation of this integration, profiles are used only in the scope of 1 order (1 auth/auth-capture) and profile 'management' is not supported/exposed anywhere by the system (this is why DefaultGatewayFeatureType.SAVED_PAYMENTS is declared as unsupported). Furthermore, the tokens received from Digital Wallets such as Apple Pay are single-use anyway, so cannot be used for more than one authorization.

      See Also:
      • PaymentGatewayConfiguration.getSupportedFeatures()

    • setGatewayType

      public void setGatewayType(String gatewayType)
      See Also:
      • PaymentGatewayTypeAware.getGatewayType()

    • setGatewayReferenceForTransactionId

      public void setGatewayReferenceForTransactionId(Map<String,String> gatewayReferenceForTransactionId)
      See Also:
      • PaymentGatewayConfiguration.getGatewayReferenceForTransactionIdByType(String)

    • equals

      public boolean equals(Object o)
      Overrides:
      equals in class Object

    • canEqual

      protected boolean canEqual(Object other)

    • hashCode

      public int hashCode()
      Overrides:
      hashCode in class Object

    • toString

      public String toString()
      Overrides:
      toString in class Object