From 9661f84f02354f16d455a381e84d45ac28ef404c Mon Sep 17 00:00:00 2001 From: plobbes Date: Mon, 12 Mar 2007 06:15:01 +0000 Subject: [PATCH] - notes for release 0.07_01: rewrite/updates for new B::OP::PayflowPro using HTTP protocol --- Changes | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/Changes b/Changes index e88ab9f..16480d5 100644 --- a/Changes +++ b/Changes @@ -1,5 +1,33 @@ Revision history for Perl extension Business::OnlinePayment::PayflowPro. +0.07 + [0.07_01 Mon Mar 12 01:56:58 EDT 2007] + - rewrite/updates for new B::OP::PayflowPro using HTTP protocol + - no longer using PFProAPI.pm (from Verisign/PayPal) + - cert_path() is now deprecated + - rewrite/updates for new B::OP::PayflowPro using HTTP protocol + - no longer use PFProAPI.pm from Verisign/PayPal + - now using name-value pair transactions + - require: CGI to parse name-value pair responses from server + - require: Digest::MD5 to generate (hopefully) unique + request_id which is required by PayflowPro HTTP protocol + - new methods: request_id(), param(), debug(), expdate_mmyy() + - renamed internal methods to start with an underscore + - removed unused remap_fields() method + - if unable to parse expiration given in %content no longer croak, + but let PayflowPro servers attempt to deal with the value as-is + - submit() now two phased per PFP HTTP protocol + - X-VPS-VIT-CLIENT-CERTIFICATION-ID is required (supposedly + this is a temporary requirement from PayPal) + - request_id() method will generate a hopefully unique id using + Digest::MD5 for use in the X-VPS-REQUEST-ID HTTP header. A + 'request_id' key may be passed in %content to specify an ID + - path() is not used as the PFP HTTP protocol uses two + different URLs (step 1) /transaction, (step 2) /commit + - patches to B::OP::HTTPS were required to support needed + functionality + - debug() sets $Business::OnlinePayment::HTTPS::DEBUG for debugging + 0.06 Thu Mar 1 10:01:33 EST 2007 - zip now allows alphanumerics for non-US zips -- 2.11.0