-
Terminally Deprecated ElementsElementDescriptionsince 1.7.2, in favor of using
SavedPaymentMethodSummaryin PaymentTransactionServices to manage saved payment methods.since 1.7.2, usePaymentAccount.getDisplayAttributes()insteadsince 1.7.2. The creation of saved payment methods as a portion of the checkout process is now handled via a post-transaction hook in PaymentTransactionServices. If the saved payment method storage location isBLC_CUSTOMER_SERVICES, then this listener should be enabled for a time to handle any existing messages whose saved payment methods were not created via the PaymentTransactionServices hook. Once a day or two have passed after adopting the PaymentTransactionServices changes, this listener can be disabled.since 1.7.2, saved payments should be handled by PaymentTransactionServices, therefore this should not be neededsince 1.7.2, in favor of usingJpaSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of usingJpaSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods, therefore this endpoint should not be needed.since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.since 1.7.2, in favor ofPayment.getShouldSavePaymentForFutureUse()to support owning user types other than a customer (i.e. account).since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.since 1.7.2, in favor of usingSavedPaymentMethodSummaryin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of usingSavedPaymentMethodSummaryin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 2.0.1, in favor ofCustomerExportEndpoint.exportCustomers(ExportRequest, ContextInfo). The new implementation for export grids includes the filter string as part of theExportRequest, instead of passing it as a parameter in the HTTP request.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 2.0.1, in favor ofCustomerSegmentExportEndpoint.exportSegmentMembers(ExportRequest, ContextInfo). The new implementation for export grids includes the filter string as part of theExportRequest, instead of passing it as a parameter in the HTTP request.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.
-
Deprecated InterfacesInterfaceDescriptionsince 1.7.2, saved payments should be handled by PaymentTransactionServices, therefore this should not be neededsince 1.7.2, in favor of using
JpaSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.since 1.7.2, in favor of usingSavedPaymentMethodSummaryin PaymentTransactionServices to manage saved payment methods.
-
Deprecated ClassesClassDescriptionsince 1.7.2, in favor of using
SavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of usingSavedPaymentMethodSummaryin PaymentTransactionServices to manage saved payment methods.since 1.7.2, usePaymentAccount.getDisplayAttributes()insteadsince 1.7.2. The creation of saved payment methods as a portion of the checkout process is now handled via a post-transaction hook in PaymentTransactionServices. If the saved payment method storage location isBLC_CUSTOMER_SERVICES, then this listener should be enabled for a time to handle any existing messages whose saved payment methods were not created via the PaymentTransactionServices hook. Once a day or two have passed after adopting the PaymentTransactionServices changes, this listener can be disabled.since 1.7.2, in favor of usingJpaSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods, therefore this endpoint should not be needed.since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.since 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.since 1.7.2, in favor of usingSavedPaymentMethodSummaryin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.
-
Deprecated Annotation InterfacesAnnotation InterfaceDescriptionsince 1.7.2, in favor of using PaymentTransactionServices as saved payment method storage location.
-
Deprecated MethodsMethodDescriptionUse the customer's additional phones insteadUse the customer's additional phones insteadsince 1.7.2, in favor of using
SavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.This field is unused.This field is unused.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.since 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methodssince 1.7.2, in favor of usingSavedPaymentMethodin PaymentTransactionServices to manage saved payment methodssince 1.7.2, in favor ofPayment.getShouldSavePaymentForFutureUse()to support owning user types other than a customer (i.e. account).since 1.7.2, in favor ofPayment.shouldSavePaymentForFutureUseto support owning user types other than a customer (i.e. account).since 2.0.1, in favor ofCustomerExportEndpoint.exportCustomers(ExportRequest, ContextInfo). The new implementation for export grids includes the filter string as part of theExportRequest, instead of passing it as a parameter in the HTTP request.since 2.0.1, in favor ofCustomerSegmentExportEndpoint.exportSegmentMembers(ExportRequest, ContextInfo). The new implementation for export grids includes the filter string as part of theExportRequest, instead of passing it as a parameter in the HTTP request.Use the customer's phone numbers insteadWe use the customer's email instead.We use the customer's name instead.We use the customer's name instead.Use the customer's phone numbers insteadWe use the customer's username instead.Use the customer's phone numbers insteadWe use the customer's email instead.com.broadleafcommerce.customer.web.endpoint.domain.RegisterAccountMemberRequest.setFirstName(String) We use the customer's name instead.We use the customer's name instead.Use the customer's phone numbers insteadWe use the customer's username instead.Use the customer's phone numbers insteadWe use the customer's email instead.Use the customer's phone numbers insteadUse the customer's phone numbers insteadWe use the customer's email instead.Use the customer's phone numbers instead
SavedPaymentMethodin PaymentTransactionServices to manage saved payment methods.