[bop-devel] Business::OnlinePayment 3.00_04 developer release...

[Ivan Kohler]

Developer release 3.00_04 has been uploaded to CPAN.

http://search.cpan.org/dist/Business-OnlinePayment/

If there are no major problems or objections, I'd like to release a 
proper 3.00 soon.

The bulk of this release is a bunch of great cleanup work from Phil 
Lobbes, but I wanted to point out one new feature, especially to 
module authors: failure statuses.

>From 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.
      
    - (NEW IN 3.00_04) You should set "failure_status" depending on the
      specific failure result, if (and only if) the failure results from one
      of the defined statuses:

      - "expired"
      - "nsf" (non-sufficient funds / credit limit)
      - "stolen"
      - "pickup"
      - "blacklisted"
      - "inactive" (inactive card or not authorized for card-not-present) (?)
      - "decline" (other card/transaction declines only, not other errors)
  
      You should use code like this so your module can work with B:OP versions
      before 3.00_04:

        $self->build_subs('failure_status') unless $self->can('failure_status');

      (or add "failure_status" to your build_subs call if you have one during
      initialization)


-- 
_ivan