Reply
Member
Posts: 2
Registered: ‎02-27-2014

Authorize.NET PHP SDK Bugs

[ Edited ]

On parse an AuthorizeNet SIM Response property invoice_number always NULL

 

@package AuthorizeNet

@subpackage    AuthorizeNetSIM

 

AuthorizeNetSIM.php#41

 

Need to update $map array with:


'invoice_number' => 'x_invoice_num',
'transaction_type' => 'x_type',
'zip_code' => 'x_zip',
'email_address' => 'x_email',
'ship_to_zip_code' => 'x_ship_to_zip',
'account_number' => 'x_account_number',

 

 

With regard

Posts: 2,533
Topics: 56
Kudos: 202
Blog Posts: 67
Registered: ‎12-05-2011

Re: Authorize.NET PHP SDK Bugs

Hello exploitfate

I've reported your issue to the product team for analysis.

I'd recommend subscribing to this topic so that you'll be alerted via email if there are updates. To subscribe, click Topic Options at the top of this thread and then select Subscribe. You'll then receive an email once anyone replies to your post.

Thanks,

Richard


Build modern websites and mobile applications without increasing PCI burden using Authorize.Net Accept


DPM will be disabled in the sandbox on 7/1/2018. EOL 7/1/2019.
Posts: 2,533
Topics: 56
Kudos: 202
Blog Posts: 67
Registered: ‎12-05-2011

Re: Authorize.NET PHP SDK Bugs

This issue is now resolved and an updated SDK is available from GitHub: https://github.com/AuthorizeNet/sdk-php.

 

RIchard


Build modern websites and mobile applications without increasing PCI burden using Authorize.Net Accept


DPM will be disabled in the sandbox on 7/1/2018. EOL 7/1/2019.
Member
Posts: 2
Registered: ‎02-27-2014

Re: Authorize.NET PHP SDK Bugs

Thanks

Highlighted
New Member
Posts: 2
Registered: ‎06-30-2018

Re: Authorize.NET PHP SDK Bugs

well i recently had an issue PHP Hello World bug i posted  and this helped me

The version of the Authorize.Net PHP SDK that you're installing has a couple of dependencies on out of date components, as well as some namespace related problems that you're seeing once you run the "charge-credit-card.php" script. The latest version of the Authorize.Net PHP SDK (1.9.0) fixes these issues.

So, the big issue is just that the sample composer.json on the "Hello World" page doesn't install the newer version, but installs an older version of the SDK that no longer works.

Replacing the composer.json sample on the "Hello World" page with the following should make everything work just fine:

{
"require": {
"authorizenet/authorizenet": "1.9.0",
"jms/serializer": "dev-serializer-master as 1.0"
},
"repositories": [
{
"type": "vcs",
"url": "https://github.com/goetas/serializer.git"
}
]
}
Just replace the composer.json, do composer update or delete the "vendor" directory, then redo composer install.

We'll hopefully get this changed on the "Hello World" page soon.

 

New Member
Posts: 1
Registered: ‎07-17-2018

Re: Authorize.NET PHP SDK Bugs

[ Edited ]

A popular extension from another browser (Firefox) is HTTPS Everywhere for Chrome. with this add on, your internet surfing can be safe and secure by automatically switching websites from insecure "http" to that of a secure "http". This is important in order to prevent online surveillance, online account hacking and in some cases web censorship