On 24 Feb 19:06, Cédric Krier wrote: > Hi, > > I have uploaded a re-worked version of the module [1] because it seems > that some banks (who said thieves?) take fees based on the number of > payment information, so grouping the payment into many transaction lower > the cost. > I tried to make a flexible grouping mechanism (and overridable). By > default, it groups the payable by date and the receivable by date and > sequence type. > > It will be great if those who tested the previous version, will test it > again with this version. > > [1] http://codereview.tryton.org/1881002/
I uploaded one minor change to always use the payment id as EndToEndId. As I understand the protocol, it will be used by the status messages to identify the original payment. So if in the future we want to manage this part of the protocol, we should be able to identify the payment from this message to set the right status on it. -- Cédric Krier - B2CK SPRL Email/Jabber: cedric.kr...@b2ck.com Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
pgpySOTlEMF9x.pgp
Description: PGP signature
