Package com.broadleafcommerce.paymentgateway.domain.enums

Enum DefaultGatewayFeatureType

java.lang.Object
java.lang.Enum<DefaultGatewayFeatureType>
com.broadleafcommerce.paymentgateway.domain.enums.DefaultGatewayFeatureType
All Implemented Interfaces:
Serializable, Comparable<DefaultGatewayFeatureType>
public enum DefaultGatewayFeatureType extends Enum<DefaultGatewayFeatureType>
Defines common features that gateways implement.
Author:
Nathan Moore (nathandmoore)

  • Enum Constant Details

    • THREE_D_SECURE

      public static final DefaultGatewayFeatureType THREE_D_SECURE
      Whether the payment gateway supports 3D Secure fraud detection.

    • PARTIAL_CAPTURE

      public static final DefaultGatewayFeatureType PARTIAL_CAPTURE
      Whether this gateway allows capturing less than the full amount. For example, the full price of an order is $100, but you can capture just the amount for item 1 which is $10.
      WARNING: This does not imply that the same transaction can be captured on again. For some gateways, after doing a partial capture, the rest of the funds are released back to the customer. To capture the rest, a new transaction will need to be created.

    • FORCED_REVERSE_AUTH_WITH_PARTIAL_CAPTURE

      public static final DefaultGatewayFeatureType FORCED_REVERSE_AUTH_WITH_PARTIAL_CAPTURE
      Declares that when a partial capture is executed for the gateway, they ALWAYS automatically execute a reverse-authorization for the remaining authorized amount.

    • PARTIAL_REFUND

      public static final DefaultGatewayFeatureType PARTIAL_REFUND
      Similar to PARTIAL_CAPTURE but with refunds.

    • PARTIAL_REVERSE_AUTH

      public static final DefaultGatewayFeatureType PARTIAL_REVERSE_AUTH
      Similar to PARTIAL_CAPTURE but with reverse-authorizations.

    • BUY_NOW_PAY_LATER

      public static final DefaultGatewayFeatureType BUY_NOW_PAY_LATER
      Whether the gateway supports a buy-now-pay-later feature. Some gateways call these "installments".

    • MULTI_USE_PAYMENT_METHODS

      public static final DefaultGatewayFeatureType MULTI_USE_PAYMENT_METHODS
      Whether payment methods (a.k.a tokens in some systems) can be reused to initiate a future line of transaction. For example, can the system create multiple authorization transactions using the same payment method or does each authorization require the user to re-enter their payment info? Another way to phrase this, does the gateway allow reauthorizing with the same payment method?

      Payment gateways that don't support multi-use methods/tokens, usually have some other means for allowing storing and reusing payment information such as Customer or Wallet features.

    • RECURRING_PAYMENTS

      public static final DefaultGatewayFeatureType RECURRING_PAYMENTS
      Whether the gateway supports recurring or subscription payments.

    • SAVED_PAYMENTS

      public static final DefaultGatewayFeatureType SAVED_PAYMENTS
      Whether the gateway supports saving customer payments for future use.

  • Method Details

    • values

      public static DefaultGatewayFeatureType[] values()
      Returns an array containing the constants of this enum type, in the order they are declared.
      Returns:
      an array containing the constants of this enum type, in the order they are declared

    • valueOf

      public static DefaultGatewayFeatureType valueOf(String name)
      Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)
      Parameters:
      name - the name of the enum constant to be returned.
      Returns:
      the enum constant with the specified name
      Throws:
      IllegalArgumentException - if this enum type has no constant with the specified name
      NullPointerException - if the argument is null