@capacitor-community/stripe-terminal TokenProvider - Allow Callback To Handle Http Token Fetch Request about stripe HOT 4 CLOSED

Released: https://github.com/capacitor-community/stripe/releases/tag/v5.4.5
Docs: https://github.com/capacitor-community/stripe/tree/v5.4.5/packages/terminal#set-string-token

Please try this.

from stripe.

I see. It is certainly preferable to make the request on the web and pass it as a string, considering the granting of Headers, etc. But If StripeTerminal.Initialize have that method, it is undesirable because a wrapper Class is required.

Currently considering:

StripeTerminal.addListener(TerminalEventsEnum.RequestedConnectionToken, async () => {
  const token = await getToken();  // Users Method
  StripeTerminal.setConnectionToken({token});
});

from stripe.

Thanks for the issue. Interesting suggestion, what problem do you hope to solve by this?
Do you want to change the API request destination in the middle of a request? Or do you want to do error handling?

from stripe.

I also would like this feature.

The ideal case would be that StripeTerminal.Initialize has an option fetchConnectionToken: () => Promise<string> where the returning string is the token. Then this token is used to initialize the StripeTerminal package.

This way we can delegate our own http-client layer so we can add headers, data, etc that our backend server endpoint may require.

from stripe.