Forums / Developer / Redirecting payment gateway - unfinished workflow process?

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Redirecting payment gateway - unfinished workflow process?

Previous topic

Developer

Next topic

Author	Message
Slavo Uhrin	Tuesday 26 February 2008 9:43:55 am I am using a custom gateway based on eZRedirectGateway class, with only createPaymentObject and createRedirectionUrl methods overriden. If the payment is accepted, the workflow process is finished and removed from the database, as well as the payment object. When the payment is not accepted, the workflow process and the payment object stays in the database, probably forever. Is this the standard and expected behavior? I would expect to finish and cleanup the workflow process in both the cases. As I can notice, the same case is with the standard eZPaypal extension. Tested in Exponential version 3.8.10. independent eZ developer \| http://howgh.sk

Author

Message

Slavo Uhrin

Tuesday 26 February 2008 9:43:55 am

I am using a custom gateway based on eZRedirectGateway class, with only createPaymentObject and createRedirectionUrl methods overriden. If the payment is accepted, the workflow process is finished and removed from the database, as well as the payment object. When the payment is not accepted, the workflow process and the payment object stays in the database, probably forever. Is this the standard and expected behavior? I would expect to finish and cleanup the workflow process in both the cases.

As I can notice, the same case is with the standard eZPaypal extension.

Tested in Exponential version 3.8.10.

independent eZ developer | http://howgh.sk