#TheMajor
1 messages · Page 1 of 1 (latest)
Hi there. Let's chat in here
Oh, hey
I was wondering if could get some tips from any stripe dev or someone else about one of the endpoints
What's your question?
In the payment intent endpoint, if i try to process a 3DS authorized cc I also need to send a return_url field in the endpoint, which is good for us
But, when stripe redirects back to my application, it doesnt send us the payment status
This info is not in the query or in the body of the req
I was wondering if there are any ways to get the payment status through this url
Because I can't show a success page or fail page if I don't know what actually happened after the authentication
It's been a while since I looked at this, but I believe we send some query params. Can you check to see what's sent in the url?
sure
Ah we list them here: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements#web-submit-payment
Payment intent is one of them
and client secret
If you scroll down in that section of the docs, you can see how to retrieve the PI with the client secret and inspect the status
Nope that's it
Sure. What is it?
I have another question about customer Ids
So a little bit of context
We are a payment microsservice using stripe as payment provider
That being said we don't have customer data in our dbs. We have only payment data
So for certain payments(Bank transfer for example) we are creating empty customerIds only to process the payment intent and not storing this info during the process
If customer wants to create a new transaction with bank transfer for example, we just create another customerId and generate a new payment intent with that new empty customerId
On our side this doesnt seem like a big problem, since we can track customer data across other services
But we wonder if stripe has any advices against that
stripe = stripe developers
That's fine, but why not just store the customer id?
We are not structured to operate with that kind of info. We are using some other payment providers and stripe would be the only one using this
Also we understood that in a conceptual level, it wouldn't make sense to keep an information about the customer in a payment document(Which is essentially the only collection we have)
But, thank you, man
You guys are awesome