#syed-SetupFuturePayments
1 messages ยท Page 1 of 1 (latest)
Hello ๐ I"m stepping in. Can you share a request ID that returns the error message?
how can i grab the request ID? still a bit new to webdev ๐
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
thx will grab it now
I'm not too sure what's going on, but it looks like my request doesn't even hit Stripe's API. the latest log is from several hours ago
Okay. Sometimes it can take a little bit for them to show up but let's move to step 2. Can you print or log the params variable to show exactly what values are getting passed?
yeah, one second
I'm trying to get the params pulled up with a couple diff methods, but it doesn't seems to be working.
On our end I did some digging into the error message you are receiving and that isn't something that is thrown by our APIs or our Ruby client library.
Would that have to do with how you have configured the URL and pattern matching?
Like it's implicitly passing in an argument to the create function but your definition doesn't expect one?
oh hmmmmmmmmmm, that might be it
giving it a swing rn
seems to be the reverse error now
def create(money)
content_type 'application/json'
data = JSON.parse(request.body.read)
#payment_method_type = data['paymentMethodType']
currency = data['currency']
params = {
#payment_method_types: [payment_method_type],
amount: money.to_i * 100,
currency: currency,
payment_method: current_user.payment_method_id,
customer: current_user.stripe_customer_id,
confirm: true,
}
wait shoot, didn't update my view
would it be appropriate to close this thread? I'm still having issues, but I don't want to take up anybody's time since this isn't strictly stripe related
We can archive it if you don't come back with more questions after a while. Don't worry about it though. If you get your URL configuration to match the arguments being passed to the create() function and then have an issue with the Stripe API we will be here to help.