-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(docs): add combined docs for paypal #1641
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you want to go the extra mile, you could also document other payment methods, such as ACDC, Google Pay, Apple Pay, PUI 🤔 or at least list the ones, for which the buttons are required and this tutorial works.
orderCreated.value = await createOrder({ | ||
paypalOrderId: data.orderID, | ||
// optional - can be acdc, applepay, googlepay or venmo | ||
product: 'sbp', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
spb
, not sbp
;)
Also, please document which product for which payment method, since it may be important, because different paymentSources get filled.
orderId: orderCreated.value.id, | ||
successUrl: `${window.location.origin}/order/success?order=${orderCreated.value.id}&success=true`, | ||
errorUrl: `${window.location.origin}/order/success?order=${orderCreated.value.id}&success=false`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
doesn't that need the paypalOrderId
to capture the created order? Same below in the existing example, I believe this was always an issue that this was not documented.
Description
The current documentation on integrating PayPal only covers Express Checkout. Therefore, we would like to adapt the existing documentation to cover both a standard PayPal checkout and an express checkout.
Type of change
Tweak the existing documentation, as most of it is generic for a PayPal checkout anyway, and add some dedicated sections for the express case.
ToDo's
Currently, the different sections for standard and express checkout are duplicated. Perhaps there is a better way to structure this?