[interchange-bugs] [rt.icdevgroup.org #309] SagePay module

Jon Jensen via RT interchange at rt.icdevgroup.org
Tue Sep 1 20:42:42 UTC 2009


Tue Sep 01 20:42:41 2009: Request 309 was acted upon.
Transaction: Ticket created by jon
       Queue: Interchange
     Subject: SagePay module
       Owner: Nobody
  Requestors: jon at endpoint.com
      Status: new
 Ticket <URL: http://rt.icdevgroup.org/Ticket/Display.html?id=309 >


Should we add this to the main Interchange distribution?


Date: Tue, 21 Jul 2009 01:16:18 +0100
From: Lyn St George <lyn at zolotek.net>
To: interchange-users at icdevgroup.org
Subject: [ic] SagePay module update
Message-ID: <200907210116.18672.lyn at zolotek.net>
User-Agent: KMail/1.9.10

Sagepay have recently changed the way they handle the protocol. They decided,
out of the blue and with only telling a small subset of vendors, to reject
all transactions which contained a comma in the address field.

This resulted in a major kerfuffle with much grief all round. They have still
not made any final or definitive announcements as to the allowable character
set but it seems that they will allow alphanumeric plus commas, periods and
spaces. I had  previously allowed everything as entered by the customer, on
the basis that when passed to the Third Man for fraud checking it should be
original (and that Sagepay would strip out any really dodgy stuff
themselves). The Third Man's tech support tell me that they can handle input
that has been reformatted so long as things like 4/25 become 4 25 with a
space separator.

An updated version of the Sagepay module is available on
http://kiwi.zolotek.net which handles things to suit both Sagepay and The
Third Man. Anyone using this module should update to this version.

--
Lyn St George
http://www.zolotek.net




More information about the interchange-bugs mailing list