paypal-express-checkout | Polymer 2 wrapper for the Paypal Express Checkout button | Frontend Framework library

As you can read in the given message, vich/uploader-bundle using the version constraint dev-master requires Symfony 4.4 or 5. This is not compatible with your version constraint ^3.3 for symfony/symfony.

After all, is there any need to use the latest untagged version of vich/uploader-bundle? Keep in mind that this might contain stuff that is broken and should not be used in production, in constrast to tagged versions.

Using the version constraint ^1.11 for that bundle, you should be able to install it properly.

Yep sure, you're express server is running on port 5000

You're calling the api on port 3000

Updated - The following will disable Paypal Checkout Payment gateway for unlogged users:

1). For the first problem, I think you just need to use a better selector to override the style

A full explanation of CORB is here.

To summarize what you have observed:

• The checkout page will load some scripts [e.g. javascript] from PayPal to implement the checkout functionality
• In addition to checkout functionality, it seems that the script may call some PayPal API "logger". From the name, this is likely to be for PayPal's analytics or "business intelligence" purposes.
• Your Web Browser has identified that the response returned from the "logger" API is invalid or inappropriate according to the CORB logic, and also not relevant to the display or operation of the checkout web page, and so CORB has filtered out the response body/headers.

Filtering out the response body/headers eliminates any opportunity for that response data to have any malicious effect or security risk in your browser (although, in this case there is no malicious intent)

So in summary, it's nothing to worry about. The checkout functionality should not be affected, and PayPal still get their analytics as the "logger" API was still called, just that it's response was discarded.

PayPal could possibly re-engineer the way the "logger" API is used to avoid triggering the message in the browser console, however that may be complex to do with little business value.

This issue was solved by using the node SDK implementation for adding and verifying webhooks. The dashboard did not work.

The problem isn't related to function binding. onSuccess is an arrow, it cannot and shouldn't be bound. {this.props.value} is incorrect syntax for object literal.

In case value contains data that should be posted, it should be:

Paypal allows both types of uses, from the client and from the server. I guess it's possible for the client to modify the request on their end to pay less. But, in the end, whatever your business is, you'll get an order and a payment. Just check if the payment is different than it should be and don't fulfil the order, make a refund.

If you want to save the trouble, then use the server option that makes the payment through your server.

In any case, like with any other payment method, I would recommend you take the time to implement it yourself following the great and well documented API provided by Paypal. They have a lot of examples and use cases, with code for the browser and the server.

Adding these 2 lines in AppKernel.php solved the problem