monshery - storing payment id | Stripe Developers | Page 1

gaunt pawn Mar 10, 2022, 4:01 PM

#

Can you explain exactly what it is you need help with here? Things you said makes sense, but I'm not sure what guidance you're seeking or what problem you're having

neon merlin Mar 10, 2022, 4:02 PM

#

Since we dont want to have duplicate fulfilment we update-lock transaction row, that means that if webhook is too quick it wont be able to access that transaction as its in a lock

#

Due to the above issue i am thinking of removing webhooks for payments
and simply upon success request, i would repeatedly do
const paymentIntent = await stripe.paymentIntents.retrieve(intentId);
and check if status is success

gaunt pawn Mar 10, 2022, 4:03 PM

#

Perhaps you could set this up in your database with generated keys that you use as metadata or idempotency keys and map to that rather than the payment intent id you might not know yet

#

That would be my suggestion

neon merlin Mar 10, 2022, 4:03 PM

#

Hmm

gaunt pawn Mar 10, 2022, 4:03 PM

#

key on your own ID in metadata

neon merlin Mar 10, 2022, 4:03 PM

#

I see what you mean

gaunt pawn Mar 10, 2022, 4:03 PM

#

generate it ahead of time

neon merlin Mar 10, 2022, 4:03 PM

#

Like temp item

#

with UUID or something

gaunt pawn Mar 10, 2022, 4:03 PM

#

yep

neon merlin Mar 10, 2022, 4:03 PM

#

hmm

gaunt pawn Mar 10, 2022, 4:04 PM

#

metadata: { monshery_id: 'payment_1234'}
which will be in the webhook events

neon merlin Mar 10, 2022, 4:04 PM

#

Yea i already do that

#

but with the transaction ID

#

so then in the webhook i look up the transaction ID

#

The issue is

#

if somehow a user made a successful purchase

#

but the webhook for some odd reason didnt work

#

we wont have a way an easy way to track the intentId

#

Will sort of result in"lost in the system" transaction

#

we will have to somehow query stripe for all paymentIntents with metadata: {transactionId: 'xxx'}

#

What i am contemplating doing is, when i do
const paymentIntent = await stripe.paymentIntents.retrieve(intentId);

and when i get a successful response i do a interval that do:
const paymentIntent = await stripe.paymentIntents.retrieve(intentId);

every like 1 second to check for paymentIntent.status === 'success'

#

what do you think ?

#

Hello ?

gaunt pawn Mar 10, 2022, 4:19 PM

#

hey there sorry hopping around

#

No why would you need this?

#

You create the payment intent with the custom id in metadata

#

then when you get PI events, you look at the metadata for your own id, not the PI id

#

and look up that way, then save the PI id if you don't have it already

#

Is there a gap somewhere that doesn't cover that you can explain?

neon merlin Mar 10, 2022, 4:28 PM

#

yea there's a gap

#

So if the webhook didnt work for some reason

#

and i dont have the paymentIntentId

#

I will have to query stripe for the ID i set in meta

gaunt pawn Mar 10, 2022, 4:42 PM

#

Where do you need that ID though?

#

You'd get the payment intent ID in the response

#

And you can set it in your db then if not yet set

neon merlin Mar 10, 2022, 4:47 PM

#

Nevermind i was trying to solve something i shouldnt

#

If after 1 h i dont get a response from stripe/webhook. i will just let the client know to talk to our support

#

as its extremely unusual

gaunt pawn Mar 10, 2022, 4:53 PM

#

That's fair - but i think for any case where the ID was relevant you should be able to access it

gaunt pawn Mar 10, 2022, 5:12 PM

#

Are you all set here then?

#monshery - storing payment id