Support

November 4, 2020 at 8:53 am

We have recently switched to the Bambora (under First Data) payment gateway and are receiving a “Transaction Declined” error on all transactions. We ran a dump of the response:

["trnApproved"]=>
  string(1) "0"
  ["trnId"]=>
  string(1) "0"
  ["messageId"]=>
  string(1) "0"
  ["messageText"]=>
  string(20) "Transaction+Declined"
  ["trnOrderNumber"]=>
  string(0) ""
  ["authCode"]=>
  string(0) ""
  ["errorType"]=>
  string(1) "S"
  ["errorFields"]=>
  string(0) ""
  ["responseType"]=>
  string(1) "T"
  ["trnAmount"]=>
  string(0) ""
  ["trnDate"]=>
  string(29) "11%2F4%2F2020+10%3A37%3A00+AM"
  ["avsProcessed"]=>
  string(1) "0"
  ["avsId"]=>
  string(1) "0"
  ["avsResult"]=>
  string(1) "0"
  ["avsAddrMatch"]=>
  string(1) "0"
  ["avsPostalMatch"]=>
  string(1) "0"
  ["avsMessage"]=>
  string(58) "Address+Verification+not+performed+for+this+transaction%2E"
  ["cardType"]=>
  string(0) ""
  ["trnType"]=>
  string(1) "P"
  ["paymentMethod"]=>
  string(0) ""
  ["ref1"]=>
  string(0) ""
  ["ref2"]=>
  string(0) ""
  ["ref3"]=>
  string(0) ""
  ["ref4"]=>
  string(0) ""
  ["ref5"]=>
  string(0) ""
  ["hashValue"]=>
  string(40) "a62b4c52c4f00c69e5c99ffd4b5190631fb46001"

Not sure where to go from here – the issue persists on any transaction. Note messageId=0 (there is no documentation on bambora for this error code) and errorType=S.