I do not think this is a default feature in eZ publish.
But ... I have seen this done with custom php code added to eZ publish.
The custom code would store information about the order's payment gateway transaction within the order itself in an unused field with information regarding the payment gateway transaction and that information was later displayed to the admin / user through a template operator.
So it is possible to do with eZ publish with not too much additional code but it requires custom development for your two payment gateways to uniformly store this information in an extra field in the order object in order to later display information based on it.
I think ezauthorize happens to store information in the way I describe which would provide for that feature but I'm not certain it provides the display feature you describe, one could add an additional field to the information stored and then write an operator to retrieve this value for a given order.
Notice folks that he used the second 'unused' field
in the order instead of adding his text string into
the first field which stores multiple records in xml format.
In this way he will not incur any conflict storing
a single string as the second field is completely
'unused' by eZ Publish by default leaving it's
purpose to be decided by the rules and conventions of your own application.
FYI. I do recommend storing the information
in question in xml format for flexibility (more than one value stored).
Well it was quite easy because I was working from the eZSips extension (http://ez.no/fr/developer/contribs/workflow/ezsips__1) Martin Harispuru (eZSips author) has already implemented this part of code, but I didn't look at it before
Here is my own contribution eZSPPlus http://ez.no/fr/developer/contribs/workflow/ezspplus
Thanks for your advices
Fabien
You must be logged in to post messages in this topic!