Google checkout/s2 sending thank you page to declined credit

[sensei]

Not sure how this is happening, but you have got to be kidding me!

We have a google checkout s2 pro post/page setup to sell access to a page which we are live streaming events..

To match up the Thank You e-mails to the google checkout receipts we setup the s2 system to send us a copy of the Thank You e-mails that are sent to the client. What we have found is that the S2 system is still sending links regardless if the credit card is valid or not.

To check on this, I registered with one of my old company credit cards in the google checkout process and google checkout proceded to tell me that the credit card was invalid. Ten seconds later I receive an e-mail (personal account) from the s2 thank you page with a link to the page in which we are live streaming our event! I then look over in our e-mail box gathering the receipts to find my thank you letter there too!

THIS IS NOT GOOD! I went back to google checked all the settings and they are spot on to what is described in the google API integration.

Help!

Thanks

Marc

[sensei]

Bump

[sensei]

I think I figured out the issue by looking at the log files from s2. The card is being charged through "optimistic" means and not "pessimistic"

This was cross referenced through google code. http://code.google.com/apis/checkout/de ... Experience

The question now arises: Can S2 google button post/page be changed to an pessimistic state where a person has to have a valid charged card in order to receive access instructions. Can this be done without deteriorating the experience of the end user?

Thanks!
Marc

[Cristián Lávaque]

Hi Marc. I'm sending Jason an email about this, he should be replying as soon as he sees it. Thanks for your patience.

[Jason Caldwell]

Thank you. Investigating now.

[Jason Caldwell]

Still investigating this.

One way or the other, we'll have a fix for this in the next release, coming soon. From my initial look at this issue, it appears that Google has changed the way they handle the OPTIMISTIC disposition since s2Member Pro was first integrated with Google Checkout. So, it looks like we'll be integrating an option for this, and possibly changing the default for s2Member to PESSIMISTIC in the next release. I'll have further details shortly.

[Jason Caldwell]

Investigation completed.
This has been corrected in the development release, which will become available soon.

Changelog excerpt for coming release.

* (s2Member Pro) **Google® Checkout ( Bug fix )**. s2Member Pro's integration with Google Checkout has been updated in this release to use `display-disposition: PESSIMISTIC` instead of `OPTIMISTIC`. This change prevents possible card declines from slipping through, and thereby granting a Customer access inadvertently. With the former `OPTIMISTIC` behavior, in rare cases when payment authorizaton at Google® Checkout took longer than 20 seconds, s2Member was giving a Customer access to the site, instead of waiting pessimistically for Google® Checkout to complete processing. The updated behavior, now set to `PESSIMISTIC`, prevents this from occurring. For technical details, see [this article](http://code.google.com/apis/checkout/developer/Google_Checkout_Digital_Delivery.html).

[sensei]

Thanks, Jason!

When do you think this release will be released.

It looks like the perfect solution!

Thanks!

Marc

[sensei]

Also, in the time being, is it possible to deactivate the link in s2 if we find that someone was given access to it with a declined card. Either through the interface or deactivating it through the sql database?

Thanks!
Marc

[Jason Caldwell]

The next release is coming in the next 2-5 days, depending on last minute issues.

Also, in the time being, is it possible to deactivate the link in s2 if we find that someone was given access to it with a declined card. Either through the interface or deactivating it through the sql database?

Can I see the ClickBank Button Shortcode that you used please?

[sensei]

<a href="http://www.abraham-hicks-spiritual-philosophy.com/abraham-hicks-live-workshop-broadcast/?s2member_pro_google_co=1&co[ids]=2888&co[exp]=336&co[desc]=Abraham%20LIVE%20Broadcast%20%2B%2048%20Hours%20On-Demand%20Video%20Playback%2C%20September%203%2C%202011%2C%209AM%20MDT%20-%20%2474.95%20USD&co[cc]=USD&co[custom]=www.abraham-hicks-spiritual-philosophy.com&co[ra]=74.95&co[sp]=1&co[image]=default&co[output]=anchor">
<img src="https://checkout.google.com/buttons/checkout.gif?w=180&h=46&style=trans&variant=text&loc=en_US" style="width:auto; height:auto; border:0;" alt="Google® Checkout" />


Also will the next release be wordpress 3.1 compatible? Not a deal breaker, just need to know so that I can test other plugins to make sure they are going to work well with a wordpress update.

Thanks!

Marc

[Jason Caldwell]

Thanks for the follow-up.

Unforunately, this is not as easy as Membership to revoke access. Specific Post/Page Access Links are self-contained, so the closest I can get you is a custom file like the one below, and you'll need to know the IP address of the User to deny them access in a way that does not hurt the credibility of your site.

Create this directory and file:
/wp-content/mu-plugins/s2-hacks.php

Code: Select all

<?php
add_filter ("ws_plugin__s2member_sp_access", "my_handler");
function my_handler ($what_s2member_says)
    {
        if ($_SERVER["REMOTE_ADDR"] === "x.x.x.x")
            return false;
        else
            return $what_s2member_says;
    }
?>

Also will the next release be wordpress 3.1 compatible? Not a deal breaker, just need to know so that I can test other plugins to make sure they are going to work well with a WordPress update.

That's a great question. No, the next release of s2Member will drop compatibility for WordPress v3.1.x, and will instead be compatible only with WordPress v3.2+.