[Feature Request] Using stripe-node outside of Node.js (e.g. Cloudflare Workers or Deno)

[brillout]

I'm trying to setup a Stripe service as a serverless function using the Cloudflare Workers platform.

But the stripe-node package seems to depend on Node.js APIs. Is it possible to use a subset of stripe-node's functionalities for Cloudflare Workers?

Is supporting Cloudlfare Workers something you are interested in? Using Stripe in a no-cold-start serverless environment would be quite lovely.

Would it be possible to extract the business logic that is agnostic to Node.js and expose it to users? So that we can use all kinds of platforms beyond Node.js, such as the Deno or Cloudflare Workers. It could be a new package, e.g. stripe-js.

Thanks for what you are doing at Stripe, it's such a lovely product.

Related tickets: #871 #773.

[richardm-stripe]

Hi @brillout! Thanks for the feature request.

Cloudflare or Deno isn't something we've investigated in depth yet but it would be interesting to learn more. You might be able to help us out a little bit by elaborating a little bit about your use case -- how you would interact with with Stripe from a Cloudflare worker and what value this would unlock for you.

We did a little bit of work towards decoupling the library from the 'child_process' API in #775, which we were just using incidentally. If I understand correctly, I think in order to meet your need we would need to decouple from the 'http' Node API as well, that we use in StripeResource, and we are unfortunately quite far from today.

[brillout]

Hi @richardm-stripe !

I want to be able to accept donations with credit cards on https://www.clocktab.com/ and https://www.timer-tab.com/. These two website are static/serverless; I don't need to maintain any server which is super convenient. I'd like to keep the serverless architecture.

I could use AWS lambda instead and that would just work. But I'm intrigued by the Cloudflare Workers Webassembly approach and avoiding cold start would be a neat thing. So my use case is not crucial; I'm just checking out options.

Wouldn't it be possible to "simply" (I don't know the details here) to expose functions that take an object holding the HTTP request url, path, headers, and body in a platform agnostic format and likewise return a platform independent object holding the HTTP response headers and payload? You could then expose these platform independent functions as well as expose Node.js, Cloudflare, and Deno wrappers.

[kristianfreeman]

Hey @richardm-stripe @brillout — I'm on the Workers team 👋

I'm super interested in helping this land! I've been playing around with the Stripe API inside of Workers and it seems like the http API is particularly the issue. Interestingly, I'm able to do some stuff that doesn't require requests (e.g. validating webhook signatures), but as soon as I try to make a request, it errors out! Ideally, the Stripe SDK could use fetch (it's provided by default in the Workers environment), though I understand that's easier said than done. Let me know how I can help!

[dplewis]

Can we allow Fetch to be passed into configuration for custom implementation that matches WebAPI spec?

Something like

const stripe = require('stripe')('<KEY>', { Fetch: myCustomWebAPIfetch }]

goshippo/shippo-node-client#50

[richardm-stripe]

Hi all, we'd be excited about adding support for fetch, but don't have immediate plans to prioritize the implementation; however if anybody is interested in putting together a proof-of-concept, that could be a lot of help.

What I'm envisioning is that instead of calling http.request/https.request and using the req object directly as we do here, we would configure an httpClient property on the stripe client that implemented a similar interface, and permit the user to provide their own implementation of that interface & configure the Stripe client to use it.

[brand-on-fire]

We'd like to be able to onboard Stripe Connect users via CloudFlare workers - is something like that currently possible? We'd prefer not to host the connect/payment functionality and have some way of ensuring uptime...

[maxnordlund]

I see two ways to do this:

1. Use http in node and https://github.com/browserify/http-browserify in the browser/Workers
2. Use fetch in the browser/Workers and polyfill it in node using https://github.com/node-fetch/node-fetch

While I personally would prefer the latter as it means first class support in the browser, the first might be easier to pull off without refactoring too much. What do you think?

[mdingena]

Following this thread because I'm trying to setup https://stripe.com/docs/billing/subscriptions/checkout in Cloudflare Workers and bumping into this exact issue.

I can't configure Webpack to target: 'node' because Workers require a 'webworker' target.

Not targeting 'node' means Webpack complains with:

WARNING in ./node_modules/stripe/lib/utils.js 17:9-38
Module not found: Error: Can't resolve 'child_process' in '/<path-to-repo>/node_modules/stripe/lib'
 @ ./node_modules/stripe/lib/stripe.js 28:14-32
 @ ./src/index.js 12:13-30

But targeting 'node' means workers-preview < dist/worker.js explodes with:

Uncaught ReferenceError: require is not defined
    at Object.http (worker.js:5218)
    at __webpack_require__ (worker.js:5269)
    at Object../node_modules/stripe/lib/StripeResource.js (worker.js:1157)
...etc

I would absolutely love a solution for this because it means I don't have to spin up an expensive server just to host my payment integration. My app is completely serverless otherwise.

[leesus]

Interestingly, I'm able to do some stuff that doesn't require requests (e.g. validating webhook signatures)

Sorry to hijack this issue, but @signalnerve do you mind sharing how you are validating signatures (or more specifically, how you are getting the raw request body)? I get No signatures found matching the expected signature for payload. Are you passing the raw request body you received from Stripe? no matter which request method I use in my worker (.text(), .json(), .arrayBuffer() and converting to string etc).

[MaxOrelus]

+1

I too would love to see this implemented. I'm running up on the same situation, where I'm trying to create a session and I get an error from the Stripe API indicating that it cannot read property "protocol" of undefined.

[rysolv-bot]

apowerful1 has contributed $70.00 to this issue on Rysolv.

The total bounty is now $70.00. Solve this issue on Rysolv to earn this bounty.

[kristianfreeman]

Interestingly, I'm able to do some stuff that doesn't require requests (e.g. validating webhook signatures)

Sorry to hijack this issue, but @signalnerve do you mind sharing how you are validating signatures (or more specifically, how you are getting the raw request body)? I get No signatures found matching the expected signature for payload. Are you passing the raw request body you received from Stripe? no matter which request method I use in my worker (.text(), .json(), .arrayBuffer() and converting to string etc).

https://github.com/cloudflare/ecommerce-bundles-workers-example/blob/main/api/src/handlers/webhook.ts#L142-L151 :)

[rhaksw]

I would absolutely love a solution for this because it means I don't have to spin up an expensive server just to host my payment integration. My app is completely serverless otherwise.

I'd love a Cloudflare solution too. @mdingena fyi you can currently do this for free with Netlify's Lambda integration. I followed this guide when implementing donations on reveddit.com. If Stripe worked with workers I would look at moving deployment from Netlify to Cloudflare. The site currently uses Cloudflare DNS and Netlify for deployment.

[lgs]

+1 Stripe on Cloudflare workers

[rysolv-bot]

An anonymous user has contributed $10.00 to this issue on Rysolv.

The total bounty is now $80.00. Solve this issue on Rysolv to earn this bounty.