Juisi's sandbox: Commerce AJAX Checkout

Please have a test drive with the current implementation

Login/register -> checkout functionality live @ http://www.fastoftheforestmovie.com

The general idea of a streamlined checkout process.

Designed primarily for buying of digital goodies. (no shipping, billing data etc. reguired)
• Buy link activates the checkout dialog. Checkout form is rendered “on top” of the current page.
• All required user input is gathered within the checkout payment pane form. (Would be really nice to also handle the multi-step pane form with this module)
• Redirect to payment gateway or internal payment handling depending on the payment method, and redirect back to the initial node or admin defined return URL
• In case an anonymous user hits the Buy link; get and render login/register form instead. Encapsulate Logintoboggan for example. User gets logged in (Ajax) and the checkout form is rendered instantly with the initial purchase.
• Go with as few interaction steps and page loads as possible to create a nice user experience and improving the conversion rate of course..
• Publish a sandbox/contrib module for "as general as possible" Ajax checkout handling. No hax/contrib patching. The Drupal Commerce people would hopefully find the module useful.
• Takes into account the 2015 EU VAT Law changes

So, our current challenges in a nutsell:

Added a general support request for this project. Please check it for more details: https://www.drupal.org/node/2391699

• provide a functioning submit handler (callback) that can, depending on the payment method that the user has chosen, route the payment either to a payment gateway method (contrib module) or a “no payment reguired” payment method (in case of 100% discount coupon for example)
• provide a custom module (According to Payment handbook https://www.drupal.org/node/1807610) to handle “no payment reguired” payments. Supposedly this code should hook up when “no payment reguired” -method is chosen by the user.
• provide a custom module and/or a hook that can handle redirecting after the order is completed. It should hook into action no matter which payment method is chosen. In other words, when a user returns to the site after a credit payment or the “no payment reguired” payment is completed, a redirect to the initial node is launched.