[bd] Paygate: AUTHORIZE.NET 1.2.0

[ActorMike]

Yes, but the MD5 is not a requirement, so maybe the code just needs edited to remove the MD5 requirement. Also, they said they were still sending the Hash right now, you just cannot add it anymore in AN.

Today we’re announcing final phase 2 dates when the gateway will stop populating the MD5 hash value.

• Phase 1 Complete
• Phase 2 - Stop sending the MD5 Hash data element in the API response. To continue verifying via hash, this will require applications to support the SHA-512 hash via signature key.
• Sandbox will be updated on March 7, 2019 to stop populating the MD5 Hash value, the field will still be present but empty.
• Production will be updated on March 14, 2019 to stop populating the MD5 Hash value, the field will still be present but empty.

 

[xfrocks]

We are aware of the issue. New version is coming soon.

 

[xfrocks]

xfrocks updated [bd] Paygate: AUTHORIZE.NET with a new update entry:

Compatibility update

• Update to use sha512 hash instead of md5
• Fix relay response stopped working

Read the rest of this update entry...

 

[Fattycakez1]

I know this is Unmaintained but is anyone still using this fine?

I installed it and seems to not show a button to buy in the upgrades page.

 

[ActorMike]

I know this is Unmaintained but is anyone still using this fine?

I installed it and seems to not show a button to buy in the upgrades page.

We use this now- https://xfrocks.com/resources/payment-profile-authorize-net-with-arb.38/