#osamayawar_api
covert ospreyBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1437662000183513189
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
young harbor
Hello! I just want to acknowledge the question. I'm working on some other threads but will get to you as soon as I can.
hi @cursive bronze, thanks for waiting. So the payment intent with "Out of band payment for invoice" is the unexpected, right?
If yes, could you share with me the PaymentIntent ID please?
young harbor
Hmm..this looks like a Payment Record
cursive bronze
pi_3SQDulCDh0iRDKQB04jCi5dr
So this PaymentIntentID is what we expect but the other payment which says "Out of band" do not have an intent id
Here is the payment record if for that payment: pr_65TZbsIAIgxcL0yUg2M41CDh0iRDKQBFI0
young harbor
Got it, let me take a look..
Okay so it looks like the out of band payment being referred to is associated to this invoice: K6NRAZLD-0001. Use this link to view the invoice in your Dashboard: https://dashboard.stripe.com/acct_1FIZMWCDh0iRDKQB/invoices/in_1SQDutCDh0iRDKQB8IELpy3L
As for why this invoice was created — it was created by your server: https://dashboard.stripe.com/acct_1FIZMWCDh0iRDKQB/logs/req_jCkyrvNW6qGcpw
And later finalized, and marked as paid out of band by your server:
- Finalized: https://dashboard.stripe.com/acct_1FIZMWCDh0iRDKQB/logs/req_39SkBo6q5Xm4zh
- Marking paid out of band: https://dashboard.stripe.com/acct_1FIZMWCDh0iRDKQB/logs/req_MBx3lYUyItMmkZ
cursive bronze
When you say our server, you mean our API's triggered it?
cursive bronze
So how come then the first payment was done with Payment Intent?
If you see, this customer has only one invoice, but two payments of the same amount. One with PaymentIntentID and other Out Of Band, we are now worried if the payment was made twice? If yes, why and how?
young harbor
pi_3SQDulCDh0iRDKQB04jCi5dr is unrelated to pr_65TZbsIAIgxcL0yUg2M41CDh0iRDKQBFI0
pr_65TZbsIAIgxcL0yUg2M41CDh0iRDKQBFI0 is related to this cancelled payment intent instead: https://dashboard.stripe.com/acct_1FIZMWCDh0iRDKQB/payments/pi_3SQDuuCDh0iRDKQB0t43GbCc
young harbor
Essentially, when this invoice: K6NRAZLD-0001 was created, pi_3SQDuuCDh0iRDKQB0t43GbCc was created to collect payment for the invoice. But the payment intent is cancelled because the invoice is marked as paid out of band, therefore you see pr_65TZbsIAIgxcL0yUg2M41CDh0iRDKQBFI0, as a record of the out-of-band payment.
cursive bronze
I can share two more clients who were charged, then a payment was canceled and then another payment of Out of band was created
young harbor
From what I can see
your integration is creating separate Invoices and standalone Payment Intent to collect payments - I do not know if they are related to each other.
cursive bronze
I'll have to double check that
young harbor
pi_3SQDulCDh0iRDKQB04jCi5dr is an example of a standalone PaymentIntent - we can verify it by viewing it in the Dashboard, and you'll notice its not connected to any Stripe Invoices.
young harbor
so if standalone PaymentIntents are not expected in your checkout flow, you'd need to check why your setup is creating these PaymentIntents.