Combining Checkout with Paypal

Combining Checkout with Paypal



It doesn't. You need to be logged in first. I could easily test for that
with OpenUI, so I'll have to wait for now.

Jason


> How does a dynamic shipping module know where the package is going before
you fill in the info on the customer info screen?
>
> --
> Bill Weiland - Emporium Plus <A HREF ="http://www.emporiumplus.com/store.mvc">http://www.emporiumplus.com/store.mvc</A>
> Modules for eCommerce. Mail Mgr, Coupon, Rate This, Wait List Mgr,
> PayPal, Gift/Wish List, Froogle data feed, Shipping & dozens more
> Online Documentation <A HREF ="http://www.emporiumplus.com/tk3/v3/doc.htm">http://www.emporiumplus.com/tk3/v3/doc.htm</A>
> Question <A HREF ="http://www.emporiumplus.com/mivamodule_wcw.mvc?Screen=SPTS">http://www.emporiumplus.com/mivamodule_wcw.mvc?Screen=SPTS</A>
> |
>
> ---- Jason Henderson <[email protected]> wrote:
> > One thing better in mm5 is that dynamic shipping methods are available
on
> > the checkout: customer information screen and this allows the entire
> > checkout process to be on that screen. In 4.x, the dynamic shipping
methods
> > were not available until OSEL.
> >
> > So I sucessfully combined checkout on this screen with authorize.net.
> > Paypal is the problem. In 4.x, you would get sent to the OPAY screen
with an
> > error message if paypal was selected as the payment method and INVC was
the
> > hidden screen specified but also presented with the continue to paypal
> > button and message. With OpenUI/templates, you could easily hide the
error
> > message if paypal was selected and everything would be fine (thus the
> > previous message). However, mm5 presents the customer with the final
> > invoice and no continue button and message in this scenario. Changing
the
> > hidden screen variable to OPAY works for paypal but now visa and
mastercard
> > users are sent to the OPAY screen with no error message because all the
> > fields are correct and must click continue again which then authorizes
and
> > gives the invoice which is not acceptable. Any ideas on getting around
the
> > paypal problem?
> >
> > Jason
> >
> >
> >

Combining Checkout with Paypal



How does a dynamic shipping module know where the package is going before you fill in the info on the customer info screen?

--
Bill Weiland - Emporium Plus <A HREF ="http://www.emporiumplus.com/store.mvc ">http://www.emporiumplus.com/store.mvc </A>
Modules for eCommerce. Mail Mgr, Coupon, Rate This, Wait List Mgr,
PayPal, Gift/Wish List, Froogle data feed, Shipping & dozens more
Online Documentation <A HREF ="http://www.emporiumplus.com/tk3/v3/doc.htm ">http://www.emporiumplus.com/tk3/v3/doc.htm </A>
Question <A HREF ="http://www.emporiumplus.com/mivamodule_wcw.mvc?Screen=SPTS ">http://www.emporiumplus.com/mivamodu...vc?Screen=SPTS </A>
|

---- Jason Henderson <[email protected]> wrote:
> One thing better in mm5 is that dynamic shipping methods are available on
> the checkout: customer information screen and this allows the entire
> checkout process to be on that screen. In 4.x, the dynamic shipping methods
> were not available until OSEL.
>
> So I sucessfully combined checkout on this screen with authorize.net.
> Paypal is the problem. In 4.x, you would get sent to the OPAY screen with an
> error message if paypal was selected as the payment method and INVC was the
> hidden screen specified but also presented with the continue to paypal
> button and message. With OpenUI/templates, you could easily hide the error
> message if paypal was selected and everything would be fine (thus the
> previous message). However, mm5 presents the customer with the final
> invoice and no continue button and message in this scenario. Changing the
> hidden screen variable to OPAY works for paypal but now visa and mastercard
> users are sent to the OPAY screen with no error message because all the
> fields are correct and must click continue again which then authorizes and
> gives the invoice which is not acceptable. Any ideas on getting around the
> paypal problem?
>
> Jason
>
>
>

One thing better in mm5 is that dynamic shipping methods are available on
the checkout: customer information screen and this allows the entire
checkout process to be on that screen. In 4.x, the dynamic shipping methods
were not available until OSEL.

So I sucessfully combined checkout on this screen with authorize.net.
Paypal is the problem. In 4.x, you would get sent to the OPAY screen with an
error message if paypal was selected as the payment method and INVC was the
hidden screen specified but also presented with the continue to paypal
button and message. With OpenUI/templates, you could easily hide the error
message if paypal was selected and everything would be fine (thus the
previous message). However, mm5 presents the customer with the final
invoice and no continue button and message in this scenario. Changing the
hidden screen variable to OPAY works for paypal but now visa and mastercard
users are sent to the OPAY screen with no error message because all the
fields are correct and must click continue again which then authorizes and
gives the invoice which is not acceptable. Any ideas on getting around the
paypal problem?

Jason