Jump to content
  • Checkout
  • Login
  • Get in touch


The e-commerce.

Search the Community

Showing results for tags 'cba'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News and Announcements
    • News and Announcements
  • osCommerce v4.x
    • General Support
    • Migration from old osCommerce
    • Design and Templates
    • Apps / Add-ons
    • Translations
    • API and import/export
    • Marketplace integration
    • Manuals and How-to
    • Blog's discussion
  • osCommerce Online Merchant v2.x
    • General Support
    • osCommerce Online Merchant Community Bootstrap Edition
    • Add-Ons
  • Development
  • General
    • General Discussions
    • Live Shop Reviews
    • Security
    • Commercial Support Inquiries
    • Developer Feedback

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Real Name




Found 2 results

  1. Hi All, I have installed the latest release of MIGS payment module and have run into a few little issues, hoping someone out there could shead some light on the matter. running 3 stores 2 x OSC 2.2 RC2A 1 x OSC 2.3.1 it has installed fine on all three sites and seems to be processing ok until the end of the process when you get redirected back to the store to confirm the order. It will give an error and instead of redirecting back to the conformation page to complete the order it redirects back to the payment option page to select a payment type, even after the CommWeb has approved the payment and returned a "00" status. So the problem is this: the customer will be caught in an endless loop of ordering. order, pay, error. order, pay, error...etc.. so when i check my merchant account the payments have been received, with no OSC order.... each order will send me this error reporting email: Secure Hash was not able to be verified against the Secret Hash, possible tampering with response I have done: double checked the Merchant ID double checked the secret hash double checked the access code problems i think it could be: comments (POST): contains apostrophes ", (, ) and characters that need to be escaped out - this is done by (looks to be both ends) OSC and CommWeb. could this be issuing the error? Reason I ask is that when I get the error reporting email from the MIGS payment gateway the POST data for comments looks different. What I sent: I would like to Sign for my order Please deliver between and ( ) and ( ). I would like to Sign for my order Please deliver between and ' ' and ' '. What has came back in the email: I would like to Sign for my order Please deliver between and . Completely removed ' ' and ' ' from the POST data besides that i have absolutely no idea to why the errors happen, i have tried to read the code but still unsure, any help would be appreciated. Thanks Ben
  2. Having searched high and low for a sign that even a single person has successfully updated their Checkout by Amazon payment module to use the new Amazon Merchant Web Services (MWS) protocol (which will become mandatory on October 8th when they shut off SOAP support), I thought I'd just ask it here: Has anyone been able to do it? I've searched these forums, the osCMax forums, and even the Zen Cart forums, and have only been able to turn up a small handful of people expressing variations of the same concern: How will the October 8th switch to MWS affect me? Not a single one of them has gotten an answer. I'm writing this (embarrassingly long) post in the hope of maybe discovering a kindred soul. Right now, customers on my osC site can choose Checkout By Amazon as a payment method, before they even create an account or log in to my site. If they choose CBA, they are taken to an Amazon payment page where they enter their Amazon login info, review the details of their order, and confirm. After that, they are taken back to my osC checkout_success.php page. Their customer account and address book entries are automatically created on my site, and their order is created in my database and viewable from my /admin/orders.php page. I can process, ship, or cancel the order from within my site's backend, and the information (shipping status, tracking number, etc.) is transmitted to Amazon. In other words, it all works as it should, and it has been for months. Then I started getting the e-mails from Amazon that say: Hello from Checkout by Amazon: According to our records you have used SOAP (Simple Object Access Protocol) to manage your Checkout by Amazon orders within the last 30 days. This is a follow-up to messages that have been sent to you by the Amazon MWS team starting April of 2011 to remind you that Amazon plans to discontinue support of SOAP on October 8, 2012. This e-mail contains important information to help you implement our latest technology that will replace SOAP. Amazon Marketplace Web Service (Amazon MWS) is replacing SOAP for sellers and developers who have integrated with Checkout by Amazon. While we will continue to support the current state of SOAP until October 8, 2012, after October 8th, 2012, SOAP operations will be discontinued. To the extent that I've been able to dive into this, it looks as though, at the very least, come October 8th I will no longer be able to update/process/ship/cancel orders from within my site's backend, as those are all SOAP operations. I tried to narrow down exactly where the SOAP operations were being performed, and I did a little test in which I commented out a small section in catalog/checkout_by_amazon/library/merchantAtAPIs/lib/amazon/amazon_merchant_at_soap_client.php. The section I commented out was: // Parse the WSDL and get the client $this->client = new SOAP_Client(WSDLPATH, true, false, $proxy, false); if (PEAR::isError($this->client)) { $this->error = "Error: " . $this->client->getMessage(); return false; } I left it commented out for a short time, and it seemed like Checkout By Amazon orders could still come through to my site and appear along with the rest of the orders in admin/orders.php. However, when I attempted to cancel out a test order I had placed using CBA during this time, the process failed. As soon as I uncommented the section above and tried again, it worked. The bottom line is, I don't know where to go from here. Amazon themselves seemed to create and support the osCommerce Checkout By Amazon payment mod back in 2009-ish (the one found in the Contributions section of addons dot oscommerce dot com), but from what I can tell (and I've searched endlessly), they no longer do, and have virtually nothing to say on the topic of the upcoming switch to MWS as it pertains to the osCommerce mod. Attempts to get help from Amazon themselves have beem mostly futile-- one day their answer is that we don't have to do anything and the CBA mod will continue to function normally (nothing seems to support this) and the next day they go back to insisting that we're using SOAP operations and we have to update by October 8th or everything will stop working. And perhaps most maddeningly of all, I've only been able to find very few people in the same situation-- people who have the CBA mod working right now the way it should, and who are concerned about the October 8th switch to MWS. And they haven't gotten any answers, either. So are there really fewer than half a dozen people in the world who run a shop that uses osC/osCMax/ZenCart and accepts Checkout By Amazon payments, or are there a lot more but they just don't know or care about the switch to MWS, or have I lost my mind and this really isn't as big a deal as I'm thinking it is? :blink: That last one is certainly a possibility.
  • Create New...