I'm building a Magento cart and we set up Google Checkout and went live and unfortunately I was unaware of the 'API Callback URL' setting on the Google side and didn't have that filled in until now. So now we have a few orders that went through and I need to get them into my cart system so I'm wondering if there's a way to force post existing orders across to my system?
See this document for various ways to retrieve Googe Checkout notifications.
http://code.google.com/apis/checkout/developer/Google_Checkout_Beta_Polling_API.html
In your case try the Polling API or the Notification History API.
Related
If you are familiar with Shopify draftOrderCreate API, you know that when retrieving the invoice_url via the graphql mutation, it will redirect you to the checkout page but there will be no DISCOUNT CODE Field, and Shopify docs are clear with this, but upon checking some apps (https://apps.shopify.com/draft-helper) it is possible, but on the said app, you will manually generate the checkout link.
Here's a photo of what that app is doing
I am wondering how do i integrate this automatically via graphql. When checking the Console (Network) it seems like he is only passing the draft order id as payload.
When you create a Draft Order, you can provide a discount. So if you do that, and then send the invoice, the discount should be applied correctly.
So, having discovered that customers are not returning to our website after making their PayPal payments, our Google Analytics reports are wonky as the landing page (success.phtml) which generates the order completion history/goal is never achieved.
Is there a PayPal APi callback to Magento which can generate the correct Google Analytics data? Is there a way to generate GA code at the PayPal end?
Any pointers appreciated!
Thanks, Joe.
a better question for you is why are your customers not reaching the success.phtml?
Go to Website Payments under Profile on the PayPal website. Setup your return URL and enter the succes url there...
If your customers don't return because they close their browser before returning to the shop:
You could remove the script from success.phtml and add a serverside-call to GA using something like serversidegoogleanalytics but you'll have to implement this for all paymentmethods you are accepting... This serversidecall would be done in the success-action within the controller of the paypal module
Is there any way to implement the checkout process aside from the ones found on the 2checkout site? I would like to have my own checkout page in my website and just pass the data to 2checkout instead of redirecting it to 2checkout's checkout page using the inline method.
2Checkout is currently in the process of beta testing their new checkout API solution which allows you to create a token from the card details client side and then submit the token server side with an API call to create a new sale. It sounds like you would be a great candidate for 2Checkout's API beta program. A ruby library and full documentation will be provided to you once you signup.
I think 2checkout sites ruby example has what you are looking for,
see here, or check out this rubygem
I am trying to implement Google Checkout in my website.
I have the PHP code sample named "checkout-php-1.3.2" from http://code.google.com/p/google-checkout-php-sample-code/.
I have followed the instructions and am able to send contents to Google Cart successfully.
The problem is i do not know how to update my website's database after the payment has been made.
I looked a little in the demo code and there is a page responsehandlerdemo.php and there i can see a lot of notification cases namely
merchant-calculation-callback
new-order-notification
order-state-change-notification
charge-amount-notification
If anybody can provide any help regarding which callback to use and how to parse the xml.
It will be very helpful.
Regards,
Sourav Mukherjee
With the exception of merchant-calculation-callback (ref), all the other notifications mean something to your order processing (everything that has to do after successful checkout).
E.g.
new-order-notification - is what it says it is, data representing a new order
order-state-change - orders move into different states (status), so this notification notifies you of them
You should go over the Developer docs particularly the Notification API for details.
I'm not a PHP developer (.Net) but I've seen the sample code and it already includes XML parsing for the notifications you receive. Once you get to know the API, you'll know when/where in the flow you need to add your business code (i.e. database storage, etc.).
We want to use Google Checkout for our Magento store. Currently, when users clicks checkout button data is sent to Google site and the user can checkout there. We would like to make it do a silent post to Google site, that is we don't want our users to leave our site, it should look like all the processing is in our store.
This is possible in PayPal, but can it be done in Google Checkout too? Are there any examples of implementation?
If not, are there other online payment systems implemented in Magento besides the PayPal which can be used for checkout without leaving the store? I've heard something about AlertPay but I don't know much about it.
When the buyer clicks the Checkout button the shopping cart data is not necessarly sent directly to Google. It can be sent to a web service running on your site and further processed there. The service will use the Checkout API to post the cart to Google. Google will return a URL where your customer can complete the order, and you will redirect the customer to that URL. More info here:
http://code.google.com/apis/checkout/developer/Google_Checkout_XML_API.html#server_to_server_technique
Regarding the final checkout step, the customer has to finish the order through Google - the customer's sensitive information such as login credentials, credit card info, is at Google and thus for security reasons he/she has to leave your website.
If you are selling digital content please have a look at Google In-App Payments. It offers a better in-app (in-site) experience:
http://code.google.com/apis/inapppayments/docs/index.html