How can I know if /pay/webhooks/stripe is routed to app/webhooks/my_checkout_completed_processor.rb

[mices]

Because the processing in my_checkout_completed_processor.rb doesn't seem to be taking place

[rakeshutekar]

Short version: it isn't routed to that file, and it won't be by filename alone. Pay doesn't auto discover processors from app/webhooks/ based on their name.

Here's what actually happens on /pay/webhooks/stripe: pay's own Pay::Webhooks::StripeController receives the request, verifies the Stripe signature, and then only hands the event to listeners that have explicitly subscribed to that event type. If nothing is subscribed, the event is simply dropped, which is exactly the silence you're seeing.

So the missing piece is the subscribe call:

# config/initializers/pay.rb
Pay::Webhooks.configure do |events|
  events.subscribe "stripe.checkout.session.completed", MyCheckoutCompletedProcessor.new
end

A few things worth checking, since any one of them gives you the same "nothing happens" symptom (these all come straight from pay's StripeController):

1. Event name has to be the prefixed one, stripe.checkout.session.completed, not just checkout.session.completed. Pay namespaces every event by processor.
2. Test mode events are gated. queue_event only fires for livemode events unless you set Pay::Stripe.webhook_receive_test_events = true. If you're testing with Stripe in test mode, your event is skipped silently without that.
3. Signing secret. If STRIPE_SIGNING_SECRET is missing or wrong, signature verification fails and the controller returns 400 before anything is queued.
4. Background worker. Events are processed asynchronously via Pay::Webhooks::ProcessJob, so if your queue adapter isn't :inline and there's no worker running, the job just sits there and your listener never runs.
5. Delivery. Confirm Stripe is really hitting the URL. The Stripe dashboard shows every attempt and the response code for /pay/webhooks/stripe.

Add the subscribe call first. If it's still quiet after that, item 2 (the test mode flag) is the one that catches most people.

[rakeshutekar]

Good progress. Now that you're past the signature error, I think you're closer than it looks, and you probably don't need that custom processor at all.

First, the payment record itself. You don't have to create it. Pay already ships a handler for this exact event, Pay::Stripe::Webhooks::CheckoutSessionCompleted, and it's subscribed by default. When the event arrives it takes the session's payment_intent, retrieves its latest charge, and syncs that into a Pay::Charge for you (that's the payment record). And because payment_processor.checkout sets customer: to your Pay customer, the charge gets linked to the right owner automatically. So the built in handler is what creates the payment, MyCheckoutCompletedProcessor isn't needed for that part.

Which means if no charge is showing up, the event almost certainly isn't reaching your app, and that lines up exactly with the Stripe message you pasted. "Set up a local listener, use the Stripe CLI, switch to a sandbox" is Stripe's way of saying it cannot POST a webhook to localhost. Your endpoint is only reachable from your own machine, so the dashboard has nowhere to deliver it.

For local development the fix is the Stripe CLI:

stripe login
stripe listen --forward-to localhost:3000/pay/webhooks/stripe

That prints a signing secret that looks like whsec_.... Use that value as your Stripe signing secret while developing, it's a different secret from any endpoint you create in the dashboard. Also set Pay::Stripe.webhook_receive_test_events = true in your pay initializer, otherwise Pay skips test mode events.

Then, and this is the part that trips people up, actually complete a checkout with a test card (4242 4242 4242 4242) through your own checkout session while stripe listen is running. A real checkout produces a real payment intent and charge, which is what Pay syncs into a Pay::Charge. If you use stripe trigger checkout.session.completed instead, that's a synthetic event with no real charge behind it, so Pay has nothing to sync and no record appears, which looks broken even though it isn't.

Quick way to see which hop is failing:

1. The stripe listen window should show checkout.session.completed being forwarded and a 200 coming back.
2. Pay::Charge.count should go up by one after the checkout completes.
3. If the listen window shows the event but Pay::Charge doesn't move, that's when the test mode flag or the signing secret is the thing to recheck.

For production it's the same idea without the CLI: deploy to a public https URL and add https://yourdomain/pay/webhooks/stripe as the webhook endpoint in the Stripe dashboard, using that endpoint's own signing secret.

[mices]

The metadata in the pay_charges table is in json format which means I won't be able to do simple associations so I wanna proceed to troubleshoot why my Payment isn't being created

[mices]

Did all that As far as I can see I'm now in live mode Still no change

[mices]

This is from my Live view in Stripe Dashboard:
Set up a local listener and use the Stripe CLI to simulate Stripe events in your local environment.
Switch to a sandbox to set up a local listener

[mices]

Got past the error but it doesn't create a Payment