Jump to content

phi148

Members
  • Content count

    254
  • Joined

  • Last visited

  • Days Won

    2

phi148 last won the day on January 25 2019

phi148 had the most liked content!

About phi148

  • Birthday 01/01/2006

Profile Information

Recent Profile Visitors

12,613 profile views
  1. phi148

    AIM and SIM have reached End of Life

    I need to find out for sure. You may be right. Assuming you are correct, then it looks like I need to implement Authorize.net "CIM". Which doesn't exist either right now
  2. phi148

    AIM and SIM have reached End of Life

    Hey all. I’m currently using AIM. However the “rebill” function is going away and AIM is also end of life. Having to call customers to get their payment info over and over will really become a pain and I was hoping to avoid that.
  3. I'm in need of this too. Looks like I may have to switch payment processors if the community no longer wants to support authorize.net
  4. phi148

    AIM and SIM have reached End of Life

    Really need this to be updated! Anybody working this by chance?
  5. phi148

    Multi_Vendor_Shipping new thread

    I don't believe this has been done yet, but I also would be interested in this... if and when I upgrade to Phoenix.
  6. Hi John, Yes, SSL does provide security - but only between the client and the server. It does not ensure the data itself traversing the SSL is accurate. Hashing, encryption, etc.. protects the data itself from breaches and verifies the validity of said data. Is it overkill? Probably... and again personal preference. In my opinion, if the option to further validate my data is there, I'll take it. Notice they say "not as useful for AIM or CP merchants". If it was completely "not useful" then I imagine it would of been abandoned entirely.
  7. I use the MD5 code and I highly suggest everybody else use the new method with the sha512 hash. From a security perspective it is critical. Is security optional? Yes. However, why wouldn’t you take the extra five minutes to implement this for you and your customers security?
  8. I don't think any exist right now. I stumbled into this just today as I was searching for a solution to the same problem.....
  9. I always use the MD5 hash ... simply for added security. It is optional. However, as Wiljen and John stated above, this is not good news that AIM is now deprecated. I was not aware of that. We probably will survive for quite some time still... however, this will eventually bite us if we don't create a new OSC addon for the new authorize.net API
  10. Authorize.Net is phasing out the MD5 based transHash element in favor of the SHA-256 based transHashSHA2. The setting in the Merchant Interface which controls the MD5 Hash option will be removed by the end of January 2019, and the transHash element will stop returning values at a later date to be determined. Please contact and work with your web developer or solutions provider to verify if you are still utilizing MD5 based hash and if still needed to move to SHA-256 hash via Signature Key. Please refer your developer or solution provider to our Transaction Hash Upgrade Guide for more details and information on this change. **** I received the above in an email from authorize.net. Just curious if anyone is planning on updating the module to support this? More info here: https://developer.authorize.net/support/hash_upgrade/?utm_campaign=19Q2 MD5 Hash EOL Merchant&utm_medium=email&utm_source=Eloqua
  11. phi148

    UPS Down?

    I haven't noticed a change in speed since switching to XML. I think it boils down to personal preference. The XML module is nice in that it should be more accurate based on the fact that it takes L, W and H into account and ties directly into your own UPS account number and negotiated rates. Probably best practice to get both versions working so you can switch easily should this happen again. We lost some sales because of it
  12. phi148

    UPS Down?

    I think I just have a super old UPS shipping module that finally bit the dust... probably due to the fact that UPS doesn't support older versions of TLS... I switched to UPS XML and that works. I'm sure there are others that may be using the old one... they'll figure it out soon enough
  13. phi148

    UPS Down?

    Anyone else having problems with UPS being down? I can't reach 153.2.228.50 which is hard coded in the UPS shipping module....
  14. phi148

    ULTIMATE Seo Urls 5 - by FWR Media

    | Id | User | Host | db | Command | Time | State | Info | +------+------------------+-----------+------------------+---------+------+---------------------------------+------------------------------------------------------------------------------------------------------+ | 1330 | xxx | localhost | xxx | Query | 1 | Waiting for table metadata lock | TRUNCATE `usu_cache` | | 1331 | xxx | localhost | xxx | Query | 1 | checking permissions | TRUNCATE `usu_cache` | | 1332 | xxx | localhost | xx | Query | 1 | Waiting for table metadata lock | TRUNCATE `usu_cache` Hey all I'm running into alot of metadata locks with my SQL database (you can see above what I'm talking about). I went and looked and the "usu_cache" table is empty. Is this even used?
  15. Is this module compatible with OSC edge (bootstrap)? Is this also still supported?
×