#hitesh1995_error

1 messages ¡ Page 1 of 1 (latest)

jaunty solsticeBOT
#

👋 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/1302929242723586051

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

narrow herald
#

hi there!

fierce rain
#

Hi, request ID is req_MXpHuQK4uGskd0

narrow herald
#

there's no errors on that request

fierce rain
#

ok, let me try

#

Hi, for the value of parameter STPAPIClient.shared.stripeAccount, do i have to pass the connect id of the destination account in to which payment will be transferred?

narrow herald
#

do i have to pass the connect id of the destination account
correct

fierce rain
#

I did set the account id and now I am getting this error while presenting payment sheet.

Error Domain=com.stripe.lib Code=50 "There was an unexpected error -- try again in a few seconds" UserInfo={NSLocalizedDescription=There was an unexpected error -- try again in a few seconds, com.stripe.lib:ErrorParameterKey=clientDefaultPaymentMethod, com.stripe.lib:ErrorMessageKey=No such PaymentMethod: 'pm_1QEqgaFbOwMhIcpir7WF8mFj'; OAuth key or Stripe-Account header was used but API request was provided with a platform-owned payment method ID. Please ensure that the provided payment method matches the specified account., com.stripe.lib:StripeRequestIDKey=req_roGlS5SiTvXO2O, com.stripe.lib:StripeErrorCodeKey=resource_missing, com.stripe.lib:StripeErrorTypeKey=invalid_request_error}

narrow herald
#

Stripe-Account header was used but API request was provided with a platform-owned payment method ID
well I'm confused. in the request you shared earlier you were doing a Direct Charge, so in this case you needed to use the Stripe-Account header.+
but based on the new error message, you are not using a Direct Charge?

#

so can you clarify exactly what you are trying to do?

fierce rain
#

It will basically hold the amount for certain time and capture it later. there could be partial refund as well.

narrow herald
#

so you are creating/confirming a PaymentIntent with a hold? and is this for a connected account? If so, it's a Direct Charge, Destination Charge, or Separate Charges & Transfers?

fierce rain
#

Yes, creating PaymentIntent with a hold. and it is for a connected account. It will be a destination charge.

narrow herald
#

if it's a Destination Charges then no need to use the Stripe-Account header

fierce rain
#

if i don't use Stripe-Account header i face No such payment_itent error.

narrow herald
#

can you share the PaymentIntent ID with this issue?

fierce rain
#

Here is the PaymentIntent ID : pi_3QHNIUG8Thp5LtcO1IRDVIV0

narrow herald
#

nope, that's a Direct Charge

#

this PaymentIntent as created with the Stripe-Account header

fierce rain
#

my bad. i misunderstood the difference between direct charge and destination charge. My app requires payment to be transferred to the connected account of the seller.

narrow herald
#

My app requires payment to be transferred to the connected account of the seller.
that could be either a Direct Charge, Destination Charge, or Separate Charges & Transfers. I recommend learning the differences here: https://docs.stripe.com/connect/charges

#

once you picked, you need to be consistent. for example if you chose Direct Charge, then:

  • all object involved (PaymentIntent, PaymentMethod, Customer, etc) will live on the connected account
  • so you'll need to use the Stripe-Acocunt header on both the backend and frontend
jaunty solsticeBOT
fierce rain
#

Hi, i got confirmed that we are using destination charge.

alpine pollen
#

?

dry snow
#

sounds good, what is your current question/issue?

alpine pollen
#

I faced issue regarding No such payment_itent error.

this is my payment intent id :- pi_3QHNIUG8Thp5LtcO1IRDVIV0

#

And we are using destination charge

dry snow
#

when do you get that error, when using what code? do you have a request ID req_xxx for the error?

alpine pollen
#

Yes let me check.

#

Request id :- req_MGJEIUBVfEQH3r

#

So can account id is required to pass in header for that?

#

as earlier we are making create intent inside connect account.