douglasward
commented
6 years ago Hi Markus, yes that's nearly right.
(2) On checkout.html:
Here the user_url should be for the page where the user can login/register etc. To proceed with the checkout the user has to be logged in, so if he/she is not the components will redirect the user to the login section, and then redirect the user back to the checkout process once they are logged in.
(3) You need to be informed about the
Yes, when you have a payment provider we would need to be informed so we can set up the tokens and redirects in the backend, or in a staging/test environment we can set it up to skip this part.
We also need to know the chosen checkout and cart URL, so we can correctly redirect on checkout success/failure and on cancel etc.
Hope this helps to clear up any confusion. Let me know if you have any further questions.
Markus-MfN
maxseeger
Related page: CheckoutComponent
Could you please give a general description of the checkout process and how to implement it?
As far as I understand it by now, it works like this:
(1) Implement the "CheckoutComponent" on its own page (e. g. checkout.html), let "CartComponent" link to it:
<go-cart options='{"action": {"mode": "url", "url": "checkout.html"}}'></go-cart>(2) On checkout.html:
`
<ng-template #goCheckoutSuccess let-item>
Ihr Einkauf war erfolgreich!!
<ng-template #goCheckoutPending let-item>
Der Status der Bezahlung ist noch schwebend...
<ng-template #goCheckoutFailure let-item>
Ihr Einkauf war nicht erfolgreich!!
`
(3) You need to be informed about the
<Payment-Service-Provider-URL>, so you can configure the redirecting of the payment service provider's answers to the corresponding state of the "CheckoutComponent" .Thanks!