Class AbstractPaymentGatewayConfiguration
- All Implemented Interfaces:
PaymentGatewayConfiguration
- Direct Known Subclasses:
PassthroughPaymentConfigurationImpl
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionintAll payment gateway classes that intend to make an external call, either manually from an HTTP Post or through an SDK which makes its own external call, should extend the AbstractExternalPaymentGatewayCall class.Each payment module should have a unique subclass ofPaymentGatewayTypewith only a single type.booleanbooleanbooleanbooleanDenotes whether or not this payment provider supports multiple payments on an order.booleanbooleanbooleanbooleanbooleanbooleanbooleanbooleanGets the configured transaction type for this module.voidsetFailureReportingThreshold(int failureReportingThreshold) All payment gateway classes that intend to make an external call, either manually from an HTTP Post or through an SDK which makes its own external call, should extend the AbstractExternalPaymentGatewayCall class.voidsetPerformAuthorizeAndCapture(boolean performAuthorizeAndCapture) Sets the transaction type to 'AUTHORIZE AND CAPTURE' for this gateway.
-
Constructor Details
-
AbstractPaymentGatewayConfiguration
public AbstractPaymentGatewayConfiguration()
-
-
Method Details
-
isPerformAuthorizeAndCapture
public boolean isPerformAuthorizeAndCapture()Description copied from interface:PaymentGatewayConfigurationGets the configured transaction type for this module.
The possible initial transaction types for a gateway can be: 'Authorize' or 'Authorize and Capture'
This property is intended to be configurable
- Specified by:
isPerformAuthorizeAndCapturein interfacePaymentGatewayConfiguration
-
setPerformAuthorizeAndCapture
public void setPerformAuthorizeAndCapture(boolean performAuthorizeAndCapture) Description copied from interface:PaymentGatewayConfigurationSets the transaction type to 'AUTHORIZE AND CAPTURE' for this gateway. If this is set to 'FALSE', then the gateway will only issue an 'AUTHORIZATION' request.
This property is intended to be configurable
- Specified by:
setPerformAuthorizeAndCapturein interfacePaymentGatewayConfiguration
-
getFailureReportingThreshold
public int getFailureReportingThreshold()Description copied from interface:PaymentGatewayConfigurationAll payment gateway classes that intend to make an external call, either manually from an HTTP Post or through an SDK which makes its own external call, should extend the AbstractExternalPaymentGatewayCall class. One of the configuration parameters is the failure reporting threshold.
- Specified by:
getFailureReportingThresholdin interfacePaymentGatewayConfiguration
-
setFailureReportingThreshold
public void setFailureReportingThreshold(int failureReportingThreshold) Description copied from interface:PaymentGatewayConfigurationAll payment gateway classes that intend to make an external call, either manually from an HTTP Post or through an SDK which makes its own external call, should extend the AbstractExternalPaymentGatewayCall class. One of the configuration parameters is the failure reporting threshold.
- Specified by:
setFailureReportingThresholdin interfacePaymentGatewayConfiguration
-
handlesAuthorize
public boolean handlesAuthorize()- Specified by:
handlesAuthorizein interfacePaymentGatewayConfiguration
-
handlesCapture
public boolean handlesCapture()- Specified by:
handlesCapturein interfacePaymentGatewayConfiguration
-
handlesAuthorizeAndCapture
public boolean handlesAuthorizeAndCapture()- Specified by:
handlesAuthorizeAndCapturein interfacePaymentGatewayConfiguration
-
handlesReverseAuthorize
public boolean handlesReverseAuthorize()- Specified by:
handlesReverseAuthorizein interfacePaymentGatewayConfiguration
-
handlesVoid
public boolean handlesVoid()- Specified by:
handlesVoidin interfacePaymentGatewayConfiguration
-
handlesRefund
public boolean handlesRefund()- Specified by:
handlesRefundin interfacePaymentGatewayConfiguration
-
handlesPartialCapture
public boolean handlesPartialCapture()- Specified by:
handlesPartialCapturein interfacePaymentGatewayConfiguration
-
handlesMultipleShipment
public boolean handlesMultipleShipment()- Specified by:
handlesMultipleShipmentin interfacePaymentGatewayConfiguration
-
handlesRecurringPayment
public boolean handlesRecurringPayment()- Specified by:
handlesRecurringPaymentin interfacePaymentGatewayConfiguration
-
handlesSavedCustomerPayment
public boolean handlesSavedCustomerPayment()- Specified by:
handlesSavedCustomerPaymentin interfacePaymentGatewayConfiguration
-
handlesMultiplePayments
public boolean handlesMultiplePayments()Description copied from interface:PaymentGatewayConfigurationDenotes whether or not this payment provider supports multiple payments on an order. For instance, a gift card provider might want to support multiple gift cards on a single order but a credit card provider may not support payment with multiple credit cards.
If a provider does not support multiple payments in an order then that means that all payments are deleted (archived) on an order whenever a new payment of that type is attempted to be added to the order.
- Specified by:
handlesMultiplePaymentsin interfacePaymentGatewayConfiguration
-
getGatewayType
Description copied from interface:PaymentGatewayConfigurationEach payment module should have a unique subclass of
PaymentGatewayTypewith only a single type. For instance, the Braintree module would have a 'BraintreePaymentGatewayType' subclass which adds itself to the global static map.In order to ensure that the class loader loads the extension of
PaymentGatewayType, it is recommended to add a simple bean definition to a module application context that is utilized by both the site and admin. Using the Braintree module as an example again, this might look like:<bean class="com.broadleafcommerce.payment.service.gateway.BraintreeGatewayType" />- Specified by:
getGatewayTypein interfacePaymentGatewayConfiguration
-