[bop-devel] Proposed - Barclaycard EPDQextra Plus API Direct Link Integration

[Simon Waters]

On 24/01/13 09:13, Ivan Kohler wrote:
> On Tue, Jan 22, 2013 at 04:26:14PM +0000, Simon Waters wrote:
>>
>> Do any of the existing modules do anything along these lines already?
>
> https://metacpan.org/requires/distribution/XML-Simple lists PaymenTech,
> IPPay and Litle also using XML::Simple.

Okay so not a new sort of dependency, and not crazy bad. Wasn't sure 
with HTTPS if I should be testing the https_post return. I will feed it 
more nonsense in testing which will reveal any failings in error handling.

>> All the modules seem to split protocol, server, path for the
>> connection.  Is that an SSLeay thing, as the LWP::UserAgent approach
>> can be just strings. Do BOP authors care?  [...]
>>
>> Should I be using Business::OnlinePayments::HTTPS
>
> I would call it a "nice to have", but probably the least important thing
> in notes_for_module_writers_v3.  Problems with one or other of the SSL
> modules are less common than they used to be.

Well I'm using it.

> I'd like to ask Ivan from 7 years ago why he thought it should be at the
> top with exclamation marks.

Maybe because the other Perl SSL modules didn't verify the certificates 
correctly. I'll assume you knew what you were doing back then ;)

> AuthorizeNet was the first module and in the past was probably the
> canonical source of standard keys and value formatting.  The code itself
> has grown too much to recommend as a starting point for new modules.

Okay - useful to know.

> "MM/YY".  I have now documented this in the base B:OP documentation and
> corrected the example.

Sorted.