-
Notifications
You must be signed in to change notification settings - Fork 253
feat: Handle Stripe webhooks payment received for DPM order fulfillment #4151
feat: Handle Stripe webhooks payment received for DPM order fulfillment #4151
Conversation
481531e
to
32d72d2
Compare
32d72d2
to
901f9bf
Compare
|
||
@property | ||
def payment_processor(self): | ||
return Stripe(self.site) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Repeating back here to make sure I understand what we chatted about, but basically this payment_processor
method is here because the payment processor this class uses is Stripe, BUT we don't use the other payment processor class because we we require different functionality than synchronous purchases (and the things that behave differently are overridden below)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I added this here because somewhere in the code it references the same of the processor, which we want it to be Stripe and not the StripeWebhooksPayment. I will get back to you where.
93705ee
to
585d670
Compare
ea669c6
to
41ec2ed
Compare
b8221e0
to
22bc6b7
Compare
22bc6b7
to
e7b43bd
Compare
54a3d5a
to
6335635
Compare
18f27eb
to
1abc1ba
Compare
1abc1ba
to
b51172c
Compare
REV-3973.
Order creation, fulfillment, billing address creation must be addressed via webhook events for Dynamic Payment Methods.
Adding a WebhooksPayment class to handle all that is needed after a payment is successfully received.
Redirect to receipt URL will happen via payment MFE redirect.
This PR also adds/updates the receipt error page to include a message specific for DPM.