черный властелин

[runic summit]

Can you share the pi_xxx IDs?

[runic summit]

Can you please paste them

[gleaming herald]

pi_3LuY3HLF7fb18ELu1D6ZGDeV

pi_3LuY3ELF7fb18ELu1DYuecnQ

[runic summit]

These aren't duplicate charges, but unique individual payments created by your integration:

• https://dashboard.stripe.com/test/logs/req_mf23r7JxcKrtiG
• https://dashboard.stripe.com/test/logs/req_JyDgIcaJjTY36I

My guess is this was unintentional, but something in your integration fired multiple requests when I guess you were only expecting one

[gleaming herald]

youre right

[runic summit]

So depending on how you create those requests , you need to debug what the issue is. Perhaps the buy button handler fired multiple times (do you disable it after click?)

[gleaming herald]

i create these requests using node-cron, but i i dont know why i receive two individual payments

[runic summit]

I guess something in your logic there isn't preventing duplicates as you expect

[gleaming herald]

can you give me advice, how to do that?

[runic summit]

You need to work through your code and debug the issue. I'd start by checking the usersList variable which seemingly determines whether or not you create a payment

That must be returning a length when you expect it to be empty

So work back from there, check the filteredDateAccounts – are you passing the correct params? I've no idea what this does as its your own private API

My guess is it may be a race condition

[gleaming herald]

all working correct locally, on localhost:3000, or on vercel

but after deploying on the vps, it startes duplicating request, something like that

[runic summit]

I'm not sure what to suggest unfortunately! As far as Stripe is concerned, these are unique API requests and we treat them as such

[gleaming herald]

ok,thx