Package org.broadleafcommerce.common.payment.service
package org.broadleafcommerce.common.payment.service
-
ClassDescriptionAll 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 this class.Simple interface for returning a
PaymentRequestDTObased on the current customer in the system (like something on threadlocal).Simple interface for returning aPaymentRequestDTObased on the current order in the system (like something on threadlocal).The default implementation of this interface is represented in the core Broadleaf framework atDefaultCustomerPaymentGatewayService.This interface is a lightweight replacement of gateway-specific classes extending AbstractExternalPaymentGatewayCall, and it helps expose some f the QoS inner methods, for testing purposes.The default implementation of this interface is represented in the core Broadleaf framework atoorg.broadleafcommerce.core.payment.service.DefaultPaymentGatewayCheckoutService.The intention of this API is to generate the necessary parameters and fields needed by the payment gateway's JavaScript library in order to create a tokenization request.This API is intended to define the specific configuration parameters that this gateway implementation currently supports.Each payment gateway module should configure an instance of this.This represents the main servic bus for grabbing configurations to configured payment gateways to execute service calls programmatically.Several payment gateways allow you to manage Customer and Credit Card Information from the gateway allowing you to create a transaction from the tokenized customer or payment method at a later date.Several payment gateways allow you to manage Customer and Credit Card Information from the gateway allowing you to create a transaction from the tokenized customer or payment method at a later date.Certain Payment Integrations allow you to use Fraud Services like Address Verification and Buyer Authentication, such as PayPal Payments Pro (PayFlow Edition)Certain Payment Integrations allow you to use a Hosted Solution, such as PayPal Express and SagePay Form.This API provides the ability to get the status of a Transaction after it has been submitted to the Gateway.Default Resolver implementation.This API allows each module to provide its own implementation for rollback.Some gateways allow you to create a form of recurring billing by creating a subscription profile.Several Gateways have a method of communication that uses the HTTP Request/Response model and the client's browser to transmit transaction result information back to the system.This default implementation encodes the seal using a URL-Safe Base64 encoder and 'HmacSHA1'This API is intended to be called by the Checkout Workflow to confirm all Payments on the order that have not yet been confirmed/finalized.This is a decoupled interface that provides the basic functions needed to create the normal BILLABLE Credit Card TransactionsThe purpose of this class, is to provide an API that will create any gateway specific parameters needed for a Transparent Redirect/Silent Order Post etc...This is a utility service that aids in translating the Request Attribute and Request Parameters to a single String.This default implementation produces the Request Attributes and Request Paremeters in JSON notation.The purpose of this class, is to provide an API that will translate a web response returned from a Payment Gateway into a PaymentResponseDTO