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

[Ivan Kohler]

On Wed, Jan 23, 2013 at 03:15:24PM +0000, Simon Waters wrote:
> 
> This provider wants a "customer name" but BOP seems to offer both
> "name" and "first_name" "last_name. I suspect it can be safely left
> to implementers.

Unfortunately this is one place which is probably not as standardized as 
it could be.

In my code which uses B:OP I pass all three, to work with as many 
gateways as possible.

It probably wouldn't be a bad idea to have the B:OP base class help 
gateway classes provide name from first_name and last_name or 
vice-versa.


> Wouldn't recommend anyone else uses the code yet, on the other hand
> it may save someone a little time if they are using BOP already.
> 
> I've no idea how to do the error handling.

The most important thing is the first section of "Handling failures" in 
notes_for_module_writers_v3:

    - If your processor module encounters a setup problem, communication        
      error or other problem that's prevents the card from even being           
      run, you should die (or croak) with a useful error message.  Setting      
      is_success to 0 and returning normally should only be done when the       
      transaction *processing* was sucessful (or at least elicited some sort    
      of result from the gateway), but the transaction itself returned a        
      "normal" decline status of some sort.

The subsequent part about the new "failure_status" support would be nice 
to have, but is less important.


> Any constructive criticism or advice welcome.

Well, since you asked and all, an _info subroutine providing 
introspection data would be nice. 

-- 
_ivan