We are using the Stripe payment provider as the shops payment option and we can finalise and process live orders fine, but there are a couple of things i wanted to check and see if its possible or how to set these.
We would like to send all the order details i.e. order lines especially to stripe so we can see whats been paid for, even temporary as part of the payment description
We have the option in the setting "sendstripereceipt" and want this receipt to include the order details above so the customer has got that in their email
When the order is placed/created in the Umbraco backend (or when we recieve the confirmation back from stripe) we would like to send an admin email with the order details to let admin users know about the new order.
Regards points 1 and 2 unfortunately that's now how the Stripe provider is setup to work. Instead it just sends a single summary line to cover the cost of the whole order.
Whilst it's possible that the individual orders lines could be sent, generally Tea Commerce's discount engine is more flexible than payment gateways tend to allow you to represent in their payment models. As we need to make our payment providers work for many different scenarios which could include complex discounting rules, we have to go for a simpler single line summary instead.
Regarding your last question, this is possible in a couple of ways. You could add the admin email as a bcc to the default Order Confirmation email in the email template settings. Or, you could create a new email template and then write some code to hook into the Order Finalized event (https://docs.teacommerce.net/3.4.0/api/events/#net-events) and then use the EmailTemplateService.Instance to send your email template to the admin.
Thanks for that i will have a look into the source code for the stripe payment provider and see where i can adjust that as i remember a while ago i did the same in a custom payment system think it was on creating the payment intent.
As for the email, we i have gone with just creating and sending another custom email with the order details both to admin users and also to the customer.
Send Cart orderlines to Stripe
We are using the Stripe payment provider as the shops payment option and we can finalise and process live orders fine, but there are a couple of things i wanted to check and see if its possible or how to set these.
Hi Denford,
Regards points 1 and 2 unfortunately that's now how the Stripe provider is setup to work. Instead it just sends a single summary line to cover the cost of the whole order.
Whilst it's possible that the individual orders lines could be sent, generally Tea Commerce's discount engine is more flexible than payment gateways tend to allow you to represent in their payment models. As we need to make our payment providers work for many different scenarios which could include complex discounting rules, we have to go for a simpler single line summary instead.
If you wish to show the individual order lines, then you would need to take the source code of the Stripe provider available here https://github.com/TeaCommerce/Tea-Commerce-Payment-Providers/tree/master/Source/TeaCommerce.PaymentProviders.Stripe and extend it to do so via a custom build.
Regarding your last question, this is possible in a couple of ways. You could add the admin email as a bcc to the default Order Confirmation email in the email template settings. Or, you could create a new email template and then write some code to hook into the Order Finalized event (https://docs.teacommerce.net/3.4.0/api/events/#net-events) and then use the
EmailTemplateService.Instanceto send your email template to the admin.Hope this helps
Matt
Hi Matt,
Thanks for that i will have a look into the source code for the stripe payment provider and see where i can adjust that as i remember a while ago i did the same in a custom payment system think it was on creating the payment intent.
As for the email, we i have gone with just creating and sending another custom email with the order details both to admin users and also to the customer.
is working on a reply...