Skip to main content
Skip to main content

AbstractPaymentService

This will be

Deprecated

in the near future use the AbstractPaymentProcessor instead

Implements

Properties

__configModule__Record<string, unknown>
__container__anyRequired
__moduleDeclaration__Record<string, unknown>
manager_EntityManagerRequired
transactionManager_undefined | EntityManagerRequired
identifierstringRequired

Accessors

activeManager_

Implementation of

PaymentService.activeManager_

Inherited from

TransactionBaseService.activeManager_

Methods

atomicPhase_

Wraps some work within a transactional block. If the service already has a transaction manager attached this will be reused, otherwise a new transaction manager is created.

Parameters
work(transactionManager: EntityManager) => Promise<TResult>Required
the transactional work to be done
isolationOrErrorHandlerIsolationLevel | (error: TError) => Promise<void | TResult>
the isolation level to be used for the work.
maybeErrorHandlerOrDontFail(error: TError) => Promise<void | TResult>
Potential error handler
Returns
PromisePromise<TResult>Required
the result of the transactional work

authorizePayment

Parameters
paymentSessionPaymentSessionRequired
A Payment Session is created when a Customer initilizes the checkout flow, and can be used to hold the state of a payment flow. Each Payment Session is controlled by a Payment Provider, which is responsible for the communication with external payment services. Authorized Payment Sessions will eventually get promoted to Payments to indicate that they are authorized for payment processing such as capture or refund. Payment sessions can also be used as part of payment collections.
contextDataRequired
Returns
PromisePromise<{ data: Data ; status: PaymentSessionStatus }>Required

Deprecated


cancelPayment

This will be

Parameters
paymentPaymentRequired
A payment is originally created from a payment session. Once a payment session is authorized, the payment is created to represent the authorized amount with a given payment method. Payments can be captured, canceled or refunded. Payments can be made towards orders, swaps, order edits, or other resources.
Returns
PromisePromise<Data>Required

Deprecated

in the near future


capturePayment

This will be

Parameters
paymentPaymentRequired
A payment is originally created from a payment session. Once a payment session is authorized, the payment is created to represent the authorized amount with a given payment method. Payments can be captured, canceled or refunded. Payments can be made towards orders, swaps, order edits, or other resources.
Returns
PromisePromise<Data>Required

Deprecated

in the near future


createPayment

Abstract **createPayment**(context): Promise&#60;[PaymentSessionResponse](/references/js-client/internal/types/internal.internal.PaymentSessionResponse)&#62;

Parameters
contextCart & PaymentContextRequired
The type of this argument is meant to be temporary and once the previous method signature will be removed, the type will only be PaymentContext instead of Cart & PaymentContext
Returns
PromisePromise<PaymentSessionResponse>Required

Abstract **createPayment**(cart): Promise&#60;[Data](/references/js-client/internal/types/internal.internal.Data)&#62;

This will be

Parameters
cartCartRequired
Returns
PromisePromise<Data>Required

Deprecated

in the near future use createPayment(context: Cart & PaymentContext): Promise<PaymentSessionResponse> instead


deletePayment

This will be

Parameters
paymentSessionPaymentSessionRequired
A Payment Session is created when a Customer initilizes the checkout flow, and can be used to hold the state of a payment flow. Each Payment Session is controlled by a Payment Provider, which is responsible for the communication with external payment services. Authorized Payment Sessions will eventually get promoted to Payments to indicate that they are authorized for payment processing such as capture or refund. Payment sessions can also be used as part of payment collections.
Returns
PromisePromise<void>Required

Deprecated

in the near future


getIdentifier

Returns
stringstring

getPaymentData

Parameters
paymentSessionPaymentSessionRequired
A Payment Session is created when a Customer initilizes the checkout flow, and can be used to hold the state of a payment flow. Each Payment Session is controlled by a Payment Provider, which is responsible for the communication with external payment services. Authorized Payment Sessions will eventually get promoted to Payments to indicate that they are authorized for payment processing such as capture or refund. Payment sessions can also be used as part of payment collections.
Returns
PromisePromise<Data>Required

Deprecated


getStatus

This will be

Parameters
dataDataRequired
Returns
PromisePromise<PaymentSessionStatus>Required

Deprecated

in the near future


refundPayment

This will be

Parameters
paymentPaymentRequired
A payment is originally created from a payment session. Once a payment session is authorized, the payment is created to represent the authorized amount with a given payment method. Payments can be captured, canceled or refunded. Payments can be made towards orders, swaps, order edits, or other resources.
refundAmountnumberRequired
Returns
PromisePromise<Data>Required

Deprecated

in the near future


retrievePayment

Parameters
paymentDataDataRequired
Returns
PromisePromise<Data>Required

Deprecated


retrieveSavedMethods

This will be

Parameters
customerCustomerRequired
A customer can make purchases in your store and manage their profile.
Returns
PromisePromise<Data[]>Required

Deprecated

in the near future


shouldRetryTransaction_

Parameters
errRecord<string, unknown> | { code: string }Required
Returns
booleanboolean

updatePayment

Abstract **updatePayment**(paymentSessionData, context): Promise&#60;Record&#60;string, unknown&#62; \| [PaymentSessionResponse](/references/js-client/internal/types/internal.internal.PaymentSessionResponse)&#62;

Parameters
paymentSessionDataDataRequired
contextCart & PaymentContextRequired
The type of this argument is meant to be temporary and once the previous method signature will be removed, the type will only be PaymentContext instead of Cart & PaymentContext
Returns
PromisePromise<Record<string, unknown> | PaymentSessionResponse>Required
it return either a PaymentSessionResponse or PaymentSessionResponse["session_data"] to maintain backward compatibility

Abstract **updatePayment**(paymentSessionData, cart): Promise&#60;[Data](/references/js-client/internal/types/internal.internal.Data)&#62;

This will be

Parameters
paymentSessionDataDataRequired
cartCartRequired
Returns
PromisePromise<Data>Required

Deprecated

in the near future use updatePayment(paymentSessionData: PaymentSessionData, context: Cart & PaymentContext): Promise<PaymentSessionResponse> instead


updatePaymentData

Parameters
paymentSessionDataDataRequired
dataDataRequired
Returns
PromisePromise<Data>Required

Deprecated


withTransaction

Parameters
transactionManagerEntityManager
Returns
AbstractPaymentServiceAbstractPaymentServiceRequired
Was this section helpful?