Tips and Tricks HQ Support Portal › Forums › WP eStore Forum › estore – authorize.net with aweber not working as expected
Tagged: authorise.net, aweber
- This topic has 9 replies, 2 voices, and was last updated 11 years, 10 months ago by admin.
-
AuthorPosts
-
January 9, 2013 at 3:16 pm #8301blogbuilderMember
I’ve set up a product using Authorize.net as the payment gateway and automatic integration with Aweber following your tutorials.
When testing, the payment goes through Authorize.net all fine but the buyer is not added to my Aweber list.
So I followed your ‘debug’ tutorial to test things out and created a simple squeeze page and signed up. This didn’t go through authorize.net as it was just a squeeze page but the buyers name did get added to Aweber automatically.
So I must be doing something wrong in another part of the set-up with authorize.net AND Aweber?
Can you help?
Thanks,
Andrew
January 9, 2013 at 10:57 pm #52913adminKeymasterHi Andrew, Your test proves that your API setup with AWeber is correct. So lets take a look at what happens after a authorize.net sale. Please enable debug (if you don’t have it enabled) then do a full authorize.net test transaction and share the content of the debug file here so I can analyze it. This post has more details on debug:
https://support.tipsandtricks-hq.com/forums/topic/how-and-when-to-enable-debug-and-what-does-it-do
To be more specific, you will need to share the content of the following debug file so I can see what it did with the AWeber signup after the authorize.net payment:
– eStore_post_payment_debug.log
January 10, 2013 at 2:09 pm #52914blogbuilderMemberI just testing again and the – eStore_post_payment_debug.log is empty:
[01/10/2013 10:42 AM] – Advisory : Log file reset.
Another thing, today, I’m not being taken to my thank you page. I’me just being sent to the Authorize.net receipt page.
Yesterday while testing I was taken to my thank you page.
I’ve added a thank you url in the area: Return URL (in the general settings).
Thanks,
Andrew
January 11, 2013 at 12:38 am #52915adminKeymasterHi Andrew, that would be the issue we need to handle first. Looks like the IPN stuff is not setup correctly with your authorize.net account. So eStore is not getting any notification to the plugin after a payment. Once we find out what setup is wrong in your authorize.net account and fix it, the rest of the process will start to work.
Do you have the post payment notification enabled in your authorize.net merchant account? Pleaes post a link to the page where you have the eStore product in question so I can check if it is adding the correct IPN URL in the payment submission request.
Also, take a look at this post that may be helpfull too:
January 11, 2013 at 8:22 am #52916blogbuilderMemberI got my thank you page to be shown after an authorize.net transaction by changing the a.net settings.
Still no automatic integration of Aweber though.
Here’s the contents of eStore_post_payment_debug.log:
payment data from: authorize
[01/11/2013 8:15 AM] – SUCCESS :Retrieving order details… Key: 50efc9e4c9f73 Gateway: authorize
[01/11/2013 8:15 AM] – SUCCESS :Retrieved Item Details: 1|International Awakening To Animals Conference 2013|1|265||ip=82.24.15.151
[01/11/2013 8:15 AM] – SUCCESS :Order Received… verifying payment data.
[01/11/2013 8:15 AM] – SUCCESS :Performing post payment processing tasks.
[01/11/2013 8:15 AM] – SUCCESS :Item Number: 1
[01/11/2013 8:15 AM] – SUCCESS :Item Name: International Awakening To Animals Conference 2013
[01/11/2013 8:15 AM] – SUCCESS :Item Quantity: 1
[01/11/2013 8:15 AM] – SUCCESS :Item Total: 265
[01/11/2013 8:15 AM] – SUCCESS :Item Currency: USD
[01/11/2013 8:15 AM] – FAILURE :Invalid Product Currency. Expected currency: GBP, Received Currency: USD
[01/11/2013 8:15 AM] – SUCCESS :End of post payment processing tasks.
[01/11/2013 8:15 AM] – SUCCESS :gateway=authorize, custom=ip=82.24.15.151, txn_id=0, txn_type=auth_capture, transaction_subject=(TESTMODE) This transaction has been approved., first_name=Andrew, last_name=Rondeau, payer_email=andrew@webuildyourblog.com, num_cart_items=, subscr_id=50efc9e4c9f73, address=104 Lavington Road, Worthing, Sussex BN14 7SJ, UK, phone=, coupon_used=, eMember_username=, eMember_userid=, mc_gross=265.00, mc_shipping=0.00, mc_tax=0.00, address_street=104 Lavington Road, address_city=Worthing, address_state=Sussex, address_country=UK, payer_business_name=, 0=Array,
Thanks, Andrew
January 11, 2013 at 10:32 pm #52917adminKeymasterThats good. The next issue is related to your currency setup mistake. See the following debug line:
[01/11/2013 8:15 AM] – FAILURE :Invalid Product Currency. Expected currency: GBP, Received Currency: USD
Looks like, in your eStore you have specified to receive payment in GBP but on authorize.net you paid using USD? eStore will treat this as a hacking attempt and won’t process this payment notification. Please correct that currency configuration issue in the settings.
January 12, 2013 at 11:29 am #52918blogbuilderMemberIs this the settings within authorize.net – to allow GBP?
Thanks,
Andrew
January 12, 2013 at 11:39 pm #52919adminKeymasterPlease post a link to the page where you have the eStore product so I can see what currency you have set in eStore for this product.
January 13, 2013 at 10:47 am #52920blogbuilderMemberHere’s the sales page link:
[http://awakeningtoanimals.com/international-awakening-to-animals-conference-2013/]
Thanks,
Andrew
January 13, 2013 at 11:58 pm #52921adminKeymasterHi Andrew, thank you. Yeah it looks like you have set the currency code in eStore settings to be GBP which is okay but your authorize.net merchant account is set to accept money in USD.
Authorize.net used to be a US only gateway so they used to only accept USD. Recently they opened up for Canada and GB. I am pretty sure in your authorize.net account you have a setting somewhere that you have to change to accept money in GBP. Simply ask them the following question which should help:
My account is set to accept money in USD. I want to accept money in GBP. Where should I change this in my account profile?
-
AuthorPosts
- You must be logged in to reply to this topic.