Re: [PEPr] Comment on Payment::Ewire_Payment

Asbjørn Sloth Tønnesen wrote:

I wouldn't think they implemented the e-mail notification as THE way to integrate their payment platform into a system...

No, they have a expensive business solution, but are still interested in getting smaller sites using the normal private customer system. Ok, so you may want to design the package with a factory pattern. Maybe only the "customer/email" back end could be coded for now (that would be the current package.) So if you need later on, adding the business solution wouldn't cause a BC break in your package... Or you could simply rename the package Payment_Ewire_Email... Not big deal for now...

I take contact to them tomorrow, as I see it there are 2 options. 1) attach a signed xml file (posible key manage problem) 2) add a verification link/button (no key problem / design problem) other ideas? 3) A callback to a website (but maybe that's the business solution),

4) A shared secret (i.e. a password or secret key setup in the account) that would be use to generate a finger print of the message. So this is very similar to the public/private key encryption solution but without the key management problem. -Philippe