Deprecated API

Contents

• Terminally Deprecated
• Fields
• Methods
• Enum Constants

Terminally Deprecated Elements

Element	Description
com.broadleafcommerce.payment.service.gateway.DefaultStripeExternalCallService.captureCharge(StripePaymentRequest, RequestOptions)	The usage of the Charges API is not compliant with SCA, so high rates of declines are likely in EEA. Related documentation https://stripe.com/docs/strong-customer-authentication#preparing
com.broadleafcommerce.payment.service.gateway.DefaultStripeExternalCallService.communicateWithVendorChargesAPI(StripePaymentRequest, RequestOptions)	The usage of the Charges API is not compliant with SCA, so high rates of declines are likely in EEA. Related documentation https://stripe.com/docs/strong-customer-authentication#preparing
com.broadleafcommerce.payment.service.gateway.DefaultStripeExternalCallService.createCharge(StripePaymentRequest, RequestOptions)	The usage of the Charges API is not compliant with SCA, so high rates of declines are likely in EEA. Related documentation https://stripe.com/docs/strong-customer-authentication#preparing
com.broadleafcommerce.payment.service.gateway.DefaultStripeExternalCallService.createChargeFromPaymentIntent(StripePaymentRequest, RequestOptions)	The usage of the Charges API is not compliant with SCA, so high rates of declines are likely in EEA. Related documentation https://stripe.com/docs/strong-customer-authentication#preparing
com.broadleafcommerce.payment.service.gateway.DefaultStripeExternalCallService.refundCharge(StripePaymentRequest, RequestOptions)	The usage of the Charges API is not compliant with SCA, so high rates of declines are likely in EEA. Related documentation https://stripe.com/docs/strong-customer-authentication#preparing
com.broadleafcommerce.payment.service.gateway.DefaultStripeTransactionService.getRequestId(Charge)	use DefaultStripeTransactionService.getGatewayTransactionId(com.stripe.model.StripeObject) instead of this
com.broadleafcommerce.payment.service.gateway.webhooks.DefaultStripeGatewayWebhookHandler.constructEvent(HttpHeaders, String, Map<String, String>)	in favor of StripeWebhookEventService.constructEvent(HttpHeaders, String, Map).
com.broadleafcommerce.payment.service.gateway.webhooks.DefaultStripeGatewayWebhookHandler.validateAndConstructEvent(HttpHeaders, String, Map<String, String>)	in favor of StripeWebhookEventService.validateEvent(HttpHeaders, String, Map) and StripeWebhookEventService.constructEvent(HttpHeaders, String, Map).
com.broadleafcommerce.vendor.stripe.service.type.StripeMethodType.CHARGE_CAPTURE	The usage of the Charges API is not compliant with SCA, so high rates of declines are likely in EEA. Related documentation https://stripe.com/docs/strong-customer-authentication#preparing
com.broadleafcommerce.vendor.stripe.service.type.StripeMethodType.CHARGE_CREATE	The usage of the Charges API is not compliant with SCA, so high rates of declines are likely in EEA. Related documentation https://stripe.com/docs/strong-customer-authentication#preparing
com.broadleafcommerce.vendor.stripe.service.type.StripeMethodType.REFUND_CREATE	The usage of the Charges API is not compliant with SCA, so high rates of declines are likely in EEA. Related documentation https://stripe.com/docs/strong-customer-authentication#preparing

Deprecated Fields

Field	Description
com.broadleafcommerce.vendor.stripe.service.payment.MessageConstants.PAYMENT_INTENT_SAVE_PAYMENT_METHOD	in favor of PaymentRequest.isCreateMultiUseToken()

Deprecated Methods

Method	Description
com.broadleafcommerce.payment.service.gateway.DefaultStripeExternalCallService.captureCharge(StripePaymentRequest, RequestOptions)	The usage of the Charges API is not compliant with SCA, so high rates of declines are likely in EEA. Related documentation https://stripe.com/docs/strong-customer-authentication#preparing
com.broadleafcommerce.payment.service.gateway.DefaultStripeExternalCallService.communicateWithVendorChargesAPI(StripePaymentRequest, RequestOptions)	The usage of the Charges API is not compliant with SCA, so high rates of declines are likely in EEA. Related documentation https://stripe.com/docs/strong-customer-authentication#preparing
com.broadleafcommerce.payment.service.gateway.DefaultStripeExternalCallService.createCharge(StripePaymentRequest, RequestOptions)	The usage of the Charges API is not compliant with SCA, so high rates of declines are likely in EEA. Related documentation https://stripe.com/docs/strong-customer-authentication#preparing
com.broadleafcommerce.payment.service.gateway.DefaultStripeExternalCallService.createChargeFromPaymentIntent(StripePaymentRequest, RequestOptions)	The usage of the Charges API is not compliant with SCA, so high rates of declines are likely in EEA. Related documentation https://stripe.com/docs/strong-customer-authentication#preparing
com.broadleafcommerce.payment.service.gateway.DefaultStripeExternalCallService.refundCharge(StripePaymentRequest, RequestOptions)	The usage of the Charges API is not compliant with SCA, so high rates of declines are likely in EEA. Related documentation https://stripe.com/docs/strong-customer-authentication#preparing
com.broadleafcommerce.payment.service.gateway.DefaultStripeTransactionService.fillResponse(PaymentRequest, PaymentResponse, PaymentIntent)	in favor of DefaultStripeTransactionService.fillResponse(PaymentRequest, PaymentResponse, PaymentIntent, String)
com.broadleafcommerce.payment.service.gateway.DefaultStripeTransactionService.fillResponse(PaymentResponse, Charge)	in favor of DefaultStripeTransactionService.fillResponse(PaymentResponse, Charge, String)
com.broadleafcommerce.payment.service.gateway.DefaultStripeTransactionService.fillResponse(PaymentResponse, Refund)	in favor of DefaultStripeTransactionService.fillResponse(PaymentResponse, Refund, String)
com.broadleafcommerce.payment.service.gateway.DefaultStripeTransactionService.getRequestId(Charge)	use DefaultStripeTransactionService.getGatewayTransactionId(com.stripe.model.StripeObject) instead of this
com.broadleafcommerce.payment.service.gateway.StripeRestConfigurationProperties.getPaymentIntentReturnUrl()	in favor of StripeRestConfigurationProperties.getPaymentIntentReturnUrl(String, String)
com.broadleafcommerce.payment.service.gateway.StripeRestConfigurationProperties.getPublicApiKey()	this is not used in the gateway but on the frontend
com.broadleafcommerce.payment.service.gateway.StripeRestConfigurationProperties.getShouldIncludeLevel3Data()	in favor of StripeRestConfigurationProperties.getShouldIncludeLevel3Data(String, String)
com.broadleafcommerce.payment.service.gateway.StripeRestConfigurationProperties.setPublicApiKey(String)	this is not used in the gateway but on the frontend
com.broadleafcommerce.payment.service.gateway.webhooks.DefaultStripeGatewayWebhookHandler.constructEvent(HttpHeaders, String, Map<String, String>)	in favor of StripeWebhookEventService.constructEvent(HttpHeaders, String, Map).
com.broadleafcommerce.payment.service.gateway.webhooks.DefaultStripeGatewayWebhookHandler.validateAndConstructEvent(HttpHeaders, String, Map<String, String>)	in favor of StripeWebhookEventService.validateEvent(HttpHeaders, String, Map) and StripeWebhookEventService.constructEvent(HttpHeaders, String, Map).
com.broadleafcommerce.vendor.stripe.service.type.StripePaymentTypes.isFinalPayment()	no longer used

Deprecated Enum Constants

Enum Constant	Description
com.broadleafcommerce.vendor.stripe.service.type.StripeMethodType.CHARGE_CAPTURE	The usage of the Charges API is not compliant with SCA, so high rates of declines are likely in EEA. Related documentation https://stripe.com/docs/strong-customer-authentication#preparing
com.broadleafcommerce.vendor.stripe.service.type.StripeMethodType.CHARGE_CREATE	The usage of the Charges API is not compliant with SCA, so high rates of declines are likely in EEA. Related documentation https://stripe.com/docs/strong-customer-authentication#preparing
com.broadleafcommerce.vendor.stripe.service.type.StripeMethodType.REFUND_CREATE	The usage of the Charges API is not compliant with SCA, so high rates of declines are likely in EEA. Related documentation https://stripe.com/docs/strong-customer-authentication#preparing