paypal / paypal-js Goto Github PK

I have two paypal accounts. One appears to be working fine while the other just loads indefinitely.

If I look at the paypal API logs, I see there is a 403 at the timestamp I was trying to load the app.

🌍 Environment

5.0.332

The code for both apps are the same, only the clientId differs.

import React, { useState, useEffect } from 'react'
import { loadScript } from "@paypal/paypal-js"

const PayPal = () => {
  const { getRequest } = useQuery()

  useEffect(() => {
    loadScript({ "client-id": clientId, vault: true, intent: 'subscription' }).then((paypal) => {
      console.log(paypal)
      paypal.Buttons({
        style: { layout: 'horizontal' },
        createSubscription: createPayPalSubscription,
        onApprove: payPalSubscriptionApproved
      }).render("#paypal-button-container").catch((error) => {
        console.error("failed to render the PayPal Buttons", error);
      })
    }).catch((error) => {
      console.error("failed to load the PayPal JS SDK script", error);
    })
  }, [])

  const createPayPalSubscription = (data, actions) => {
    // this plan ID is from paypal subscriptions.
    return actions.subscription.create({
      'plan_id': planId
    })
  }

  const payPalSubscriptionApproved = (data, actions) => { /* do stuff */ }

  return <>pp dirct <div id="paypal-button-container" /></>
}

export default PayPal

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency @playwright/test to v1.37.1
• chore(deps): update dependency @types/node to v20.5.1
• chore(deps): update dependency tslib to v2.6.2
• chore(deps): update vitest monorepo to v0.34.2 (@vitest/coverage-v8, vitest)
• chore(deps): update dependency @rollup/plugin-node-resolve to v15.2.0
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

🚀 Feature Proposal

Add a new public function called appendScript(options) that would be used for reloading the JS SDK script. This new option would use the previous script options and would only override the new ones passed in.

Motivation

Currently loadScript(options) can be used to:

1. initially load the JS SDK
2. reload the JS SDK when parameters change (ex: changing the currency)

The problem with this approach is loadScript(options) will always replace all the options previously used.

There are "website builder" use cases where they might not know all the previous options used to load the JS SDK script. They would prefer to append to the existing options rather than replace them.

Example

loadScript({
    'client-id': 'sb',
    'components': 'buttons',
    'disable-funding': 'card',
    'merchant-id': '12345',
    'data-partner-attribution-id': '678910',
})
    .then(() => {
        renderButtons();
    });


// assume this `appendScript()` function is called later on in the code base to load the messages component
// it doesn't know about params like "merchant-id" or "data-partner-attribution-id" but still wants to use them when reloading the script  
appendScript({ components: 'buttons,messages' })
    then(() => {
        renderMessages();
        // we still need to render buttons again since reloading the JS SDK will destroy all components on the page
        renderButtons();
    });

🐞 Describe the Bug

When the paypay button has been rendered into the document, a quick click cannot arouse the pop-up window, and the button is in the focused state (as shown in the figure below). When the button is clicked for the second time, the state is successfully aroused

🔬 Minimal Reproduction

Nothing

😕 Actual Behavior

Nothing

🤔 Expected Behavior

Nothing

🌍 Environment

• Node.js/npm: v14.17.0 / 6.14.13
• OS: - win10 x64
• Browser: - Chrome 104.0.0.0

➕ Additional Context

🐞 Describe the Bug

Inline CC validation fails silently.

onError is not called when inline credit card form validation fails. The console has an error message, but it's not communicated, leaving our clients clueless about

🔬 Minimal Reproduction

https://paypal-staging.invoicesimple.com/checkout/BwUXs9i6dU

Use the following CC details:
4242...
405 Lexington Ave, New York, NY United States
ZIP code: 101174 << Enter this invalid ZIP code

😕 Actual Behavior

Nothing's happening. There's a console error from some paypal internal library:

ppxo_inline_guest_unhandled_error

{
  "handledErrors": [
    {
      "billingAddress": {
        "contentKey": "fieldErrors.postalCodeInvalid",
        "field": "postalCode"
      }
    }
  ],
  "unhandledErrors": [],
  "inline_guest_version": "2.12.8",
  "timestamp": 1626133611140,
  "windowID": "d4ef436b46",
  "pageID": "19427c4852",
  "referer": "www.sandbox.paypal.com",
  "host": "www.sandbox.paypal.com",
  "path": "/smart/card-fields",
  "env": "sandbox",
  "country": "CA",
  "lang": "en",
  "uid": "uid_e90d1db9c5_mjm6mjg6ndc",
  "ver": "2.12.8"
}

🤔 Expected Behavior

There should be an informative error message displayed and onError should be called

🌍 Environment

• Node.js/npm: n/A
• OS: n/A
• Browser: Chrome / Firefox

➕ Additional Context

Might be related https://github.com/paypal/paypal-checkout-components/issues/1550

We have been partnering via PayPal Commerce Platform for high-volume invoice payments processing, and this one causes a real issue for real customers in production systems.

It's kind of crazy that the issue is taking so long to resolve, considering the impact.

It would be great to use GitHub Actions for CI instead of travis. To resolve this issue, complete the following:

• replace the travis.yml file with a github action workflow that runs linting, tests, and the build. I think it would be just like the github action recently added to react-paypal-js: paypal/react-paypal-js#33
• replace the travis ci badge in the readme with a github actions badge

🐞 Describe the Bug

A clear and concise description of what the bug is.

🔬 Minimal Reproduction

Describe steps to reproduce. If possible, please, share a link with a minimal reproduction.

😕 Actual Behavior

A clear and concise description of what is happening. Please include console logs during the time of the issue, especially error messages.

🤔 Expected Behavior

A clear and concise description of what you expected to happen.

🌍 Environment

• Node.js/npm: -
• OS: -
• Browser: -

➕ Additional Context

Add any other context about the problem here.

Hi, I just got a Notification, that I should review the PR on the DefinitelyTyped repo and it removes the @paypal/paypal-js typings.
I just wanted to make sure, that it's correct^^ As far as I understand, paypal-js now bundles it's own typings, right?

For reference: DefinitelyTyped/DefinitelyTyped#53216

🚀 Feature Proposal

It would be convenient to have the functionality to set amount for Donation button via Donation SDK. Now configuration of amount available only from portal.

Motivation

In some system user has already predefined amount for donate and he should set amount the second time inside the PayPal Popup

Example

It could be like an option amount:

🚀 Feature Proposal

A clear and concise description of what the feature is.

Motivation

Please outline the motivation for the proposal.

Example

Please provide an example for how this feature would be used.

🐞 Describe the Bug

Cannot read properties of undefined (reading 'render') in React js

🔬 Minimal Reproduction

Here is the code sandbox : https://codesandbox.io/s/react-paypal-with-paypal-paypal-js-package-z2xlnr?file=/src/App.js

😕 Actual Behavior

When I place clientId to get paypal up and running, I got an error message on console

🤔 Expected Behavior

It should be able to recognise render and behave as expected

🌍 Environment

• Node.js/npm: - 16.17.0 LTS
• OS: - Windows 10
• Browser: - Chrome

➕ Additional Context

I've got the same issue with @paypal/react-paypal-js npm package where React skipped hostedFields for card fields

here is screenshot of the error:

🚀 Feature Proposal

Order capture also contains phone number.

Motivation

The form requires the submission of a phone number, amongst other fields of personal information. It would require another form to get phone number, which is bad for UX.

Example

onApprove: async function(data, actions) {
    const orderInfo = await actions.order.capture()
    //orderInfo.payer.phone_number or orderInfo.purchase_units[0].shipping.phone_number
}

🚀 An easy way to test failed transaction. Right now it seems not to be possible?

Basically the answer to this question: https://stackoverflow.com/questions/73150831/how-to-test-failed-transactions-with-the-paypal-js-sdk

Motivation

Testing failed payment paths is crucial to any integration. It is not understandable, that there appears to be no easy way to do it with paypal.

Example

It should be something very straight foreward:

1. Login to a sandbox test account
2. Use a certain card
3. get 100% an error corresponding to live errors

🚀 Feature Proposal

Because components are an important query param and needed in a lot of scenarios (see: https://developer.paypal.com/sdk/js/reference/) we should include an example

Motivation

It will make it easier to use in practical examples

Example

Let's include components: "buttons, hosted-fields"

Babel/Rollup is not transpiling startsWith() which breaks in older browsers (es.string.starts-with { "chrome":"49", "edge":"18", "ie":"11" })

Possible solutions:

1. Wire up babel preset-env to dynamically include polyfills like this based on the browser support we target.
2. Manually include a polyfill for startsWith()
3. Don't use key.startsWith('data-') and instead use key.substring(0, 5) === 'data-'

One thing to keep in mind with options 1 and 2 is we want to keep the overall bundle size small. Including too many polyfills will bloat this micro-module. I also tested this out in browserstack in IE11. It techincally works if we provide a promise polyfill and don't use startsWith().

Thoughts on this?

When using Types PayPalNamespace paypal.Buttons onApprove Callbacks Parameter actions is of Type OnApproveActions. I should be able to call actions.restart() but OnApproveActions type is defined to use actions.order.restart() which leads to Error "actions.order.restart is not a function".

export type OnApproveActions = {
    order: {
        capture: () => Promise<OrderResponseBody>;
        authorize: () => Promise<OrderResponseBody>;
        redirect: (redirectURL: string) => void;
        restart: () => void;
    };
};

Should at least be

export type OnApproveActions = {
    order: {
        capture: () => Promise<OrderResponseBody>;
        authorize: () => Promise<OrderResponseBody>;
        redirect: (redirectURL: string) => void;
    };
    restart: () => void;
};

Perhaps all methods should not be listed under order, I did not check this yet.

🐞 Describe the Bug

According to https://developer.paypal.com/docs/api/orders/v2/#orders_authorize the authorization id can be found in the returned data but the PurchaseUnit type is missing the payments object.

😕 Actual Behavior

typescript reports an error when trying to access payments:

error TS2339: Property 'payments' does not exist on type 'PurchaseUnit'.

40     details.purchase_units[0].payments.authorizations[0].id,
                                 ~~~~~~~~

🤔 Expected Behavior

compilation works

🌍 Environment

• Node.js/npm: -
• OS: -
• Browser: -

Spam

🐞 Describe the Bug

There are several missing / incorrect types in Typescript definitions

🔬 Minimal Reproduction

• OnApproveActions is missing get and patch functions - needed to retrieve order data without capturing / authorizing
• Payer has an incorrect type for phone - the return value has a phone_type and national_number as a sub-property of phone_number object, but this library just has phone_number as a string: https://developer.paypal.com/docs/api/orders/v2/#definition-payer
• ShippingInfo does not include options, to pass shipping rates: https://developer.paypal.com/docs/checkout/standard/customize/shipping-options/

😕 Actual Behavior

Typescript throws warnings that types are incorrect, but the defined types leads to errors in the browser and missing functionality

🤔 Expected Behavior

Types should match the interfaces outlined in documentation

🌍 Environment

• Typescript v4

🚀 Feature Proposal

A clear and concise description of what the feature is.

Motivation

Please outline the motivation for the proposal.

Example

Please provide an example for how this feature would be used.

Should we mention that the script is loaded async when opting out of defer?

🐞 Describe the Bug

Must be a recent SDK update that broke the existing PayPal Message component. It's looking for an 'account' property that doesn't exist for existing implementation.

TypeError: String.prototype.startsWith called on null or undefined
    at startsWith (<anonymous>)
    at Object.decorate (VM175 js:1)
    at VM175 js:1
    at Vr (VM175 js:1)
    at VM175 js:1
    at Object.Je [as setProps] (VM175 js:1)
    at Object.e [as init] (VM175 js:1)
    at t (VM175 js:1)
    at Na (VM175 js:1)
    at ka (VM175 js:1)

🔬 Minimal Reproduction

You can view the error on this react component example
https://paypal.github.io/react-paypal-js/?path=/docs/example-paypalmessages--default

😕 Actual Behavior

Paypal messages does not work

🤔 Expected Behavior

PayPal messages should work

🌍 Environment

• Node.js/npm: -
• OS: -
• Browser: -

➕ Additional Context

Add any other context about the problem here.

Hi,

I just started using this package and looking at the documentation I cannot find anything about passing a hosted_button_id which is required when implementing a Donate button from PayPal.
I would appreciate it if anyone could help me with any idea/link about this.

🐞 Describe the Bug

The return type from HostedFields.render() does not include the on() function to access field event subscription. It must by type-casted as "any" to avoid typescript errors.

🔬 Minimal Reproduction

In the .then callback from a HostedFields.render() function, try to access the .on() function:

loadScript({
...
}).then(
  (paypal) => {
    paypal.HostedFields.render({
      ...
    }).then(
      (cardFields) => {
          cardFields.on('validityChange', (event) => { ... });
      }
    )
  }
)

throws an "method on() does not exist on type HostedFieldsHandler" error

...
.then(
  (cardFields) => {
    (cardFields as any).on('validityChange', (event) => { ... });
  }
)

subscribes to the event just fine.

😕 Actual Behavior

The interface is missing declarations for the .on() subscription method.

🤔 Expected Behavior

The interface includes all method calls available through the Paypal API

🌍 Environment

• Node.js/npm: - 6.14.15
• OS: - Ubuntu 20.04.5
• Browser: - Chrome

➕ Additional Context

While not a critical breaking issues, as it's easily worked around, it was definitely a source of confusion.

🚀 Feature Proposal

Export a lower level function for loading any js script. This can be used to provide an easy way to load the partner.js script used for onboarding sellers. https://developer.paypal.com/docs/platforms/seller-onboarding/before-payment/#3-add-sign-up-link-to-your-site

Motivation

It would be nice if this paypal-js library could be their single solution to script loading.

Example

import { loadScript, loadCustomScript } from "@paypal/paypal-js";

// new loadCustomScript function for loading any url
loadCustomScript({ 
    url: "https://www.paypal.com/webapps/merchantboarding/js/lib/lightbox/partner.js",
    attributes: {
      id: "paypal-partner-js"
    }
 })
  .then(() => {
    console.log('partner script successfully loaded');
  })
  .catch(err => {
    console.log('failed to load partner script', err);
  });
/*
  <!-- the following html is still required for this partner integration -->
  <a data-paypal-button="true" href="<Action-URL>&displayMode=minibrowser" target="PPFrame">Sign up for PayPal</a>
*/

Additional info

The JS SDK script and the partners.js script can load independently. If the developer does want to wait for both to finish before something, then Promise.all could be used to know when both are complete.

java.net.sockettimeoutexception:www.google.org

Hi team, we are wrapping up v1 of paypal-js and our goal is to figure out the best dynamic script loading technique to use. This issue has been created to get feedback and come to a group decision on which approach to use.

Here is a link to the specific code in paypal-js that dynamically inserts the JS SDK into the page: https://github.com/paypal/paypal-js/blob/main/src/utils.js#L21.

Note that defer and async behave differently when using them on a script tag (<script src="foo" async>) directly vs using them when dynamically inserting a script (const newScript = document.createElement('script'); newScript.defer = true;). Our use case is focused on dynamic script insertion.

Here's a list of options to choose from:

1. Do not set defer or async when dynamically loading the script. Let the browser do it's default behavior when dynamically loading a script. Note that this is the approach stripe-js takes.
2. Set defer to true and async to false when dynamically loading the script.
3. Set defer to false and async to true when dynamically loading the script.
4. Set both async and defer to true when dynamically loading the script.

We have this demo for showcasing these different use cases: https://github.com/gregjopa/dynamic-script-loading-demo. Please comment and let us know your thoughts. Also, please share any demos you create to test this out.

Short Question: How to add headers to show all the buttons and what headers to add?

There is a link to paypal that shows what to do: link.
It says to add data-csp-nonce="xyz-123" on the script.
How could this be accomplished here?
Could you provide documentation for this on the readme?

Note: I tried addding data-csp-nonce="xyz-123" to the header and loadscript from your package but no result.

Query: loadScript({ 'client-id': 'sb' });

Attribute: loadScript({ 'client-id': 'sb', 'data-csp-nonce': 'asdf' });

Options: loadScript({ 'client-id': 'sb', 'data-csp-nonce': 'asdf', defer: true });

Link to available query params (https://developer.paypal.com/docs/checkout/reference/customize-sdk/#query-parameters) and attributes (https://developer.paypal.com/docs/checkout/reference/customize-sdk/#script-parameters).

If this is already possibe with a few minor tweaks, I do apologise.

🚀 Feature Proposal

Reload script on paypal button click so that a new currency can be passed correctly to the sdk

Motivation

It is very awkward to have more than one paypal button on a page which goes to a checkout for different currencies.
This error is a cummon occurance without tedious workarounds:

Expected currency from order api call to be GBP, got AUD. Please ensure you are passing currency=AUD to the sdk url

This thread highlights the issue:
https://github.com/paypal/paypal-checkout-components/issues/1180

Example

https://www.paypal.com/signin?v=1&utm_source=unp&utm_medium=email&utm_campaign=RT000255&utm_unptid=4320a500-a135-11ec-b6de-98039b1aff49&ppid=RT000255&cnac=US&rsta=en_US%28en-US%29&cust=HAUXBDQ3GM9DN&unptid=4320a500-a135-11ec-b6de-98039b1aff49&calc=f383119118fd4&unp_tpcid=DLogNotification&page=main%3Aemail%3ART000255&pgrp=main%3Aemail&e=cl&mchn=em&s=ci&mail=sys&appVersion=1.79.0&xt=104038

🐞 Describe the Bug

A clear and concise description of what the bug is.

🔬 Minimal Reproduction

Describe steps to reproduce. If possible, please, share a link with a minimal reproduction.

😕 Actual Behavior

A clear and concise description of what is happening. Please include console logs during the time of the issue, especially error messages.

🤔 Expected Behavior

A clear and concise description of what you expected to happen.

🌍 Environment

• Node.js/npm: -
• OS: -
• Browser: -

➕ Additional Context

Add any other context about the problem here.

🐞 Describe the Bug

From today, the Paypal JS script has stopped to work, the call fails with this error: net::ERR_ABORTED 400

This is the request URL that my site made: https://www.paypal.com/sdk/js?client-id=MY_CLIENT_ID&vault=true&intent=subscription

The script stopped working today, until yesterday it worked.

I have tryed to cancel cookie and cache but the problem is not solved.

🌍 Environment

• Node.js/npm: -
• OS: Windows 11
• Browser: Chrome

https://www.paypal.com/signin?v=1&utm_source=unp&utm_medium=email&utm_campaign=RT000255&utm_unptid=4320a500-a135-11ec-b6de-98039b1aff49&ppid=RT000255&cnac=US&rsta=en_US%28en-US%29&cust=HAUXBDQ3GM9DN&unptid=4320a500-a135-11ec-b6de-98039b1aff49&calc=f383119118fd4&unp_tpcid=DLogNotification&page=main%3Aemail%3ART000255&pgrp=main%3Aemail&e=cl&mchn=em&s=ci&mail=sys&appVersion=1.79.0&xt=104038

🐞 Describe the Bug

The current PayPalMessagesComponentOptions does not match the documentation found in the sdk docs.

🔬 Minimal Reproduction

Compare current type to the docs.

😕 Actual Behavior

Current type is missing options mentioned in the docs.

🤔 Expected Behavior

To be able to reference options present in the docs.

🌍 Environment

N/A

➕ Additional Context

🐞 Describe the Bug

The props of style in interface PayPalMessagesComponentOptions is missing.

🔬 Minimal Reproduction

Running the following code:

try {
    paypal = await loadScript({
        'client-id': 'YOUR_CLIENT_ID',
       '"data-client-token': 'YOUR_CLIENT_TOKEN',
    });
  } catch (error) {
    console.error('failed to load the PayPal JS SDK script', error);
  }

  if (paypal) {
    const options = {
        logo: {
            type: 'primary',
            position: 'left',
        },
        text: {
            color: 'black',
            align: 'left',
            size: 12
        },
    };
    try {
      await paypal.Messages(options).render('YOUR_MESSAGE_CONTAINER_ID');
    } catch (error) {
      console.error('failed to render the PayPal Buttons', error);
    }
  }

😕 Actual Behavior

By following the instruction from Customize Pay Later messages
I tried typing the code above, but Typescript says:

messages.d.ts(4, 5): The expected type comes from property 'style' which is declared here on type 'PayPalMessagesComponentOptions'

🤔 Expected Behavior

Error TS2332(typing error) shouldn't happen.

🌍 Environment

• Node.js/npm: - 16.13.2/8.1.2
• OS: - Windows 10 Home build 19042.1466
• Browser: - Chrome/Edge

When I use vue, the example is

paypal.Buttons.driver("vue", Vue)

At this time, I cannot use style to set its style.

🐞 Describe the Bug

Hi There. I'm trying to integrate PayPal smart button into my service on the angular framework.
I've got 403 permission denied issues moving from sandbox to a live environment.
(Same code works well in sandbox mode.)

To do that I just

1. Created a live app at dev dashboard
2. Switch my client-id to the new one.

here are my code

loadScript({
        intent: 'capture',
        'client-id': environment.paypalConfig.clientId,
        currency: this.app.getCurrencyISOCodeStr(),
        debug: true
      }).then((paypal) => {
        this.isLoading = false;
        const order = {
          purchase_units: [
            {
              amount: {
                currency_code: this.app.getCurrencyISOCodeStr(),
                value: this.amount.toFixed(2)
              }
            }
          ]
        };
        paypal
          .Buttons({
            fundingSource: 'paypal',
            createOrder(data, actions) {
              return actions.order.create(order);
            },

and the error is below.

{"name":"NOT_AUTHORIZED","details":[{"issue":"PERMISSION_DENIED","description":"You do not have permission to access or perform operations on this resource."}],"message":"Authorization failed due to insufficient permissions.","debug_id":"f24387243d3d6","links":[{"href":"https://developer.paypal.com/docs/api/orders/v2/#error-PERMISSION_DENIED","rel":"information_link"}]}

Am I miss something?

This project isn't written in TypeScript, but many TypeScript users would like to use published typings. For this issue, create TypeScript typings that cover the exported functions, and contribute it back to DefinitelyTyped!

This issue is great for someone who wants to learn more about TypeScript!

🚀 Feature Proposal

A clear and concise description of what the feature is.

Motivation

Please outline the motivation for the proposal.

Example

Please provide an example for how this feature would be used.

🐞 Describe the Bug

As per this article the onShippingChange() method should take in two parameters (data and actions) and return actions. In this library, however, it takes in no parameters and returns void (source);

➕ Additional Context

This is a very minor issue and I have managed to get around it with a ts-ignore, but I figured I would let you guys know about it. I can submit a pull request to modify buttons.d.ts but I want to make sure this is the only file that requires changes.

I do not think this is a bug of this specific library but for the script:
https://www.paypal.com/sdk/js
however I did not find any place to submit this bug.

🐞 Describe the Bug

The normal behavior for the smart buttons is :
none of them forces of the users to create an account
"Debit or Credit Card" button opens the form in the same page

however when you specify a locale outside of US for example es_MX
all of the buttons will open a modal and will force the user to create an account

🔬 Minimal Reproduction

go to:
https://developer.paypal.com/demo/checkout/#/pattern/server

test the behavior without changing anything.
notice that buttons won't force you to create an account and
"Debit or Credit Card" button opens the form in the same page

now change the script src to
<script src="https://www.paypal.com/sdk/js?client-id=sb&currency=USD&locale=es_MX"></script>

😕 Actual Behavior

all buttons force the user to create an account
"Debit or Credit Card" opens in a modal.

🤔 Expected Behavior

Using different locales shouldn't force the user to create a Paypal account (this is the most important one)
Debit or credit card button should open within the page (like when no locale is specified or a US locale)

🌍 Environment

• Node.js/npm: -
• OS: -
• Browser: -

➕ Additional Context

Add any other context about the problem here.

I am trying to add the Venmo button by setting 'enable-funding': 'venmo' but the Venmo button does not appear. I can get others like eps and ideal but venmo does not. I am using USD for currency. Is there something else I am missing to allow the venmo button?

As a side note, right now I only need the Venmo button but if I wanted to have both Venmo and Ideal is there a way I could do that with this package?

Here is the loadScript I am trying to use:
loadScript({
'client-id': paypalClientId,
'disable-funding': 'credit',
'enable-funding': 'venmo',
'vault': false,
'merchant-id': this.clientInfo.paypal_email,
'currency': this.invoice.currSymbol,
})

and the currSymbol is USD in this case.

🐞 Describe the Bug

OnApproveOrderActions.order only have the capture function
but is missing the get function
line:
https://github.com/paypal/paypal-js/blob/main/types/components/buttons.d.ts#L32

🌍 Environment

• Node.js/npm: -
• OS: -
• Browser: -

➕ Additional Context

Add any other context about the problem here.

🚀 Feature Proposal

Support multiple shipping options as described here: https://developer.paypal.com/docs/business/checkout/configure-payments/shipping-options/

Motivation

Allowing the user to choose between multiple shipping options improve the ux for express checkout.

Extra note: I could not find how this is done in the Order API documentation here: https://developer.paypal.com/docs/api/orders/v2/

🐞 Describe the Bug

The onCLick is not Working Before the createOrder on Android and iOS Devices (before the "createOrder" method).
Works Fine in Desktop.

🔬 Minimal Reproduction

1.- Make a Button with onClick method
2.- In desktop works fine (before the "createOrder" method)
3.- In mobile devices the function execute after the createOrder method.

This behavior is reproducible with the Developer tools in Chrome on Desktop (simulate the mobile devices)

🌍 Environment

• OS: macOs Catalinda
• Browser: - Chrome on Desktop, Safari and Chrome on Mobile Devices

🚀 Feature Proposal

Could you add data-merchant-id support?

Motivation

Without this script option support, we couldn't utilize to create multi seller order.
Direct js inclusion looks like this

<script src="https://www.paypal.com/sdk/js?client-id=Client-ID&merchant-id=*" data-merchant-id="MERCHANT_ID_1,MERCHANT_ID_2"></script>

Example

loadScript({ 'client-id': 'YOUR_CLIENT_ID', 'merchant-id': '*', 'data-merchant-id': 'MERCHANT_ID_1,MERCHANT_ID_2' });

🐞 Describe the Bug

i'm getting errors with message: TOKEN_FAILURE when trying create order with subscription.
Previously everything works well.
I've also tried to create subscription from postman api and visit APPROVE link but got error message on sandbox.paypal.com
'Things don't appear to be working at the moment. Please try again later.'
I've also created a subscription button in paypal editor and tried put piece of code to codepen and got same error(TOKEN_FAILURE)

🔬 Minimal Reproduction

create account in sandbox, create product, create plan with this product, copy code and paste in codepen
https://codepen.io/Artem122/pen/vYrOeqZ

🌍 Environment

• Node.js/npm: - 18
• OS: - macOS
• Browser: - Chrome

🐞 Describe the Bug

I am using return_url to bring user to a new page after order is completed.
It is simply not working

🔬 Minimal Reproduction

 paypal.Buttons({
        style: {
            "layout": "horizontal",
            "shape" : "rect",
            "tagline": "false",
            "label" : "checkout",
        } ,
        createOrder: function (data, actions) {
            // Set up the transaction
            return actions.order.create({
                application_context: {
                    brand_name: "Demo Shop",
                    shipping_preference: "NO_SHIPPING",
                    return_url: '<?= (isset($_SERVER['HTTPS']) ? "https://" : "http://").   $_SERVER['HTTP_HOST'] . "/order-ok.php" ?>',
                    user_action: "PAY_NOW",
                },
                purchase_units: [{
                    referenmce_id: "mirkos_<?=time()?>",
                    description: "Ordine #bla bla 12",
                    soft_descriptor: "Soft_#<?=time()?>",
                    amount: {
                        value: '0.04'
                    }
                }]
            });
        },


    })
    .render('#paypal-button-container');

😕 Actual Behavior

User can pay, but simply the popup disappear

🤔 Expected Behavior

After paying, I expected popup will close and the browser redirected user to a new page

🌍 Environment

• Node.js/npm: - node v.14.19.1
• OS: - indifferent, both windows and debian 10
• Browser: - indifferent

➕ Additional Context

Nothing to add for me, now