react-paypal-button | button component to implement PayPal

In your package.js file, there were some bugs.

Create a webhook listener and register for the BILLING.SUBSCRIPTION.CANCELLED event.

The Client ID is not sensitive information. It is intended to be used on the client side.

A server integration uses a client ID + secret for API calls. Server integrations are more robust and secure, so if you have the resources and ability to integrate with a backend it's recommended that you do so.

Create two routes on your server, one for 'Create Order' and one for 'Capture Order', documented here. These routes should return JSON data. The latter one should (on success) store the payment details in your database before it does the return.

Pair those two routes with the following approval flow: https://developer.paypal.com/demo/checkout/#/pattern/server

react-paypal-button-v2 is not an official module, try the newer react-paypal-js instead. See the "Docs" tab of the Storybook.

It will only show the buttons that you are eligible for as a buyer, and venmo in particular can only be eligible on mobile in the US, and maybe not at all for subscription payments (some funding types can't be used for subscriptions, and so won't be eligible)

To test as a buyer from other countries, you can add &buyer-country=XX to your SDK line, which that module should support via options={{. This buyer-country parameter only works in sandbox, will error if set in live mode

Payment methods only show up when the buyer is eligible, this is the normal and expected behavior.

You won't see both paylater and credit, you won't see giropay outside Germany, you won't see mercadopago outside south america, etc.

To test different locations in sandbox mode, use &buyer-country=XX. This only works for sandbox.

rd and del are Windows commands, but Heroku doesn't run Windows. You won't be able to use those commands on Heroku.

I suggest using a cross-platform alternative like rimraf insted of platform-specific commands so your scripts will run properly on your local development environment as well as your hosted environment.

Add it to your dependencies and then use something like

Store a record of the subscriptionID when it is first created. Typically you'll want to associate this with a user.

For keeping track of future payments, set up a webhook listener for PAYMENT.SALE.COMPLETED events.

Why do you want to redirect away from your site? That's how things were done 5+ years ago.

It's much better to keep your site loaded and present in the background and show payers an in-context approval experience, instead of redirecting them over to a new and possibly unfamiliar login page.

You are asking for how to do something you shouldn't even be trying to do, and which will result in an inferior buyer experience and fewer completed checkouts, which is the opposite of what you should want.

But since you ask, the way to do it is not not use the PayPal JavaScript SDK button. Just use the /v2/checkout/orders REST API to create an order and receive an approval_url, which you can redirect to with a static "Checkout with PayPal" button from, say, https://www.paypal.com/us/webapps/mpp/logos-buttons

Again, full page redirects are an old integration method that give a poor buyer experience and you shouldn't use this method.

In the