[
https://issues.apache.org/jira/browse/OFBIZ-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354787#comment-14354787 ]
Sebastian Wachinger edited comment on OFBIZ-4075 at 3/10/15 12:26 PM:
----------------------------------------------------------------------
Actually this is one of the most enlightening threads on this issue to be found. Is there a more detailed timeline available for the three stages of the PayPal integration as outlined in the description by BJ?
I was not aware that IPN is not supported anymore, or is it? Anyway, using it as is in the trunk now, it always renders the error _No valid orderId returned with PayPal Callback_, as the IPN parameter {{invoice}} is used for _orderID_ but for whatever reason is not transmitted and even does not show up in the otherwise complete parameter listing in _console.log_.
I suspect this to be the reason for no order confirmation being sent out to the shop's admin eventually, which we always receive when payment methods other than PayPal Express Checkout are used.
Are there any restricions on the API version number to be used here, and are there plans to switch to using the REST API?
Any input on this issue is highly appreciated!
was (Author: komdata):
Actually this is one of the most enlightening threads on this issue to be found. Is there a more detailed timeline available for the three stages of the PayPal integration as outlined in the description by BJ?
I was not aware that IPN is not supported anymore, or is it? Anyway, using it as is in the trunk now, it always renders the error _No valid orderId returned with PayPal Callback_, as the IPN parameter {{invoice}} is used for _orderID_ but for whatever reason is not transmitted and even does not show up in the otherwise complete parameter listing in _console.log_. I suspect this to be the reason for no order confirmation being sent out to the shop's admin eventually, which we always receive when payment methods other than PayPal Express Checkout are used.
Any input on this issue is highly appreciated!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)