#navin_sharma

1 messages · Page 1 of 1 (latest)

prisma smeltBOT
jaunty portal
#

hello! we'd prefer to start a new thread, can you share what's the issue/problem you're currently facing?

keen tundra
#

ok

#

my use case bit different, ive inegrated for crowdfunding platform here campaigns admin or owner are connected account and the person who came to donate are customers..

But when we create customer on Payment account . we are getting customer not found error.

jaunty portal
#

The error message you pasted mentioned Invalid value for elements(): clientSecret should be a client secret of the form ${id}secret${secret}. You specified: . - have you checked (logged) what you're passing in as the clientSecret?

keen tundra
#

yeah i've getting correct clientSecret

jaunty portal
#

can you share the code snippet where you're logging this value and the output

keen tundra
#

ok

#

LHS is where i'm consoling and RHS i'm using key

prisma smeltBOT
remote coral
#

It's not the API key (sk_xxx) but the client_secret of the Payment/Setup Intent: pi_abc_secret_xyz

keen tundra
#

Yes forget about variable name i'm passing client secret only from payment Intent
pi_3N*************************************************B6sI

remote coral
#

Clearly the value you're passing is not what you think it is. Can you share the ID (req_xxx) of the failing API request? https://support.stripe.com/questions/finding-the-id-for-an-api-request

keen tundra
#

And from logs there is no error found

#

Here is my id ===>req_Yi5LJVj3mZXJow

#

showing 200ok

remote coral
#

That's because that's not the request that is throwing the error

keen tundra
#

yes

#

its from frontend

remote coral
#

What's the actual output of result.data.body?

keen tundra
#

here in element throwing error

keen tundra
remote coral
#

Yes, but stripeKey is set to whatever result.data.body is (which is seemingly not a PI client_secret)

keen tundra
#

check here logging stripeKey which is client_secret

#

only i've changed variable name

remote coral
#

Then I suspect that something is malforming the value somewhere in your application. I'd recommend trying to hardcode the clientSecret param with that client_secret initially, then work backwards from there

keen tundra
#

ok leme check

#

And it make take sometime from my end MY REQUEST IS PLS DONT CLOSE THE THREAD

remote coral
#

Ok, sure

mighty mauve
#

@keen tundra still there?