Am-Payment | Stripe Developers | Page 1

hybrid kite Jun 6, 2022, 5:01 AM

#

Hi there, can you copy and paste the PaymentIntent ID here?

rough bear Jun 6, 2022, 5:03 AM

#

Payment intent: pi_3L7GdhGdSNBHdMPn1dZhsXM9
Status: requires_payment_method
Client secret: pi_3L7GdhGdSNBHdMPn1dZhsXM9_secret_CiQ4SqLogtegf21zkrlUeO0Xo

#

📎 webhook.json

#

and here is the webhook implemented from backend side ,

hybrid kite Jun 6, 2022, 5:08 AM

#

OK, so you just created a PaymentIntent. The response is 200 and I don't see an error here.

rough bear Jun 6, 2022, 5:10 AM

#

Right from app side , we are getting error

hybrid kite Jun 6, 2022, 5:11 AM

#

The app says the paymentIntent is invalid?

rough bear Jun 6, 2022, 5:11 AM

#

and the reason is i am not sending account id for that specific payment

hybrid kite Jun 6, 2022, 5:11 AM

#

If so, can you check if you are using the live mode publishable key at the mobile app?

rough bear Jun 6, 2022, 5:11 AM

#

coz there are more than one account id connected to this payment intent

hybrid kite Jun 6, 2022, 5:12 AM

#

Ok, pi_3L7GdhGdSNBHdMPn1dZhsXM9 is a direct charge, so you need to pass the connected account's ID to StripeAccountId when initialize the iOS SDK.

rough bear Jun 6, 2022, 5:12 AM

#

Screen_Shot_2022-06-06_at_8.12.41_AM.png

hybrid kite Jun 6, 2022, 5:13 AM

#

You can still use the platform's publishable key

rough bear Jun 6, 2022, 5:13 AM

#

yea i am using it

#

so in that. payment intent there is only one accounnt connected for getting payment right ? @hybrid kite

hybrid kite Jun 6, 2022, 5:14 AM

#

Can you show me the code on how you initialize the iOS SDK?

#

Check if you have set STPAPIClient.shared.publishableKey = Platform's test publishable key and STPAPIClient.shared.stripeAccount = connected account ID.

rough bear Jun 6, 2022, 5:24 AM

#

the app is React native app

#

i have publishable key set always

hybrid kite Jun 6, 2022, 5:25 AM

#

Are you using <StripeProvider> ?

rough bear Jun 6, 2022, 5:25 AM

#

for stripe accoount id , if it is a shared payment (gonna distribute to more than one account)as i talked with support before , they said if it is not direct do not sent any accout id

#

yes

hybrid kite Jun 6, 2022, 5:27 AM

#

<StripeProvider
      stripeAccountId='{connected account ID}'
      publishableKey={Platform's test publishable key}

#

Adding stripeAccountId to StripeProvider should solve your problem.

#

I don't quite get what you mean by shared payment, are you talking about destination charge?

rough bear Jun 6, 2022, 5:29 AM

#

https://stripe.com/docs/connect/charges-transfers

Creating separate charges and transfers

With Connect, you can make charges on your platform account on behalf of connected accounts, perform transfers separately, and retain funds in the process.

#

as you can see there can be more than one destination here

rough bear Jun 6, 2022, 5:30 AM

#

hybrid kite Adding `stripeAccountId` to StripeProvider should solve your problem.

that is exaclty what i am doing , that account id param is dynamically set to what backend send to me , coz the payment can be done to different account ids

hybrid kite Jun 6, 2022, 5:30 AM

#

Can you check if you are passing the correct accountId?

rough bear Jun 6, 2022, 5:31 AM

#

as it is a destinatioin charge and there are more than one account connected , i am not sending account

#

id params at all

#

last time i spoke with support. they said of there are more than one accounnt connected there is no need to send it

hybrid kite Jun 6, 2022, 5:31 AM

#

But you passed a stripeAccountId when creating the PaymentIntent

rough bear Jun 6, 2022, 5:32 AM

#

is that possible not sending account id while creating separate charges ?

hybrid kite Jun 6, 2022, 5:32 AM

#

If you want to perform a destination charge, then you shouldn't specify a stripeAccount header when creating the paymentIntent

rough bear Jun 6, 2022, 5:33 AM

#

o i see , so from the backend , while creating a destination charge no account id should be sent , right ?

hybrid kite Jun 6, 2022, 5:34 AM

#

Yes you are right

#

And neither should you pass an accountId at mobile end.

rough bear Jun 6, 2022, 5:36 AM

#

it is already not being sent from mobile app

hybrid kite Jun 6, 2022, 5:36 AM

#

In summary, for Direct Charges -> you need to pass the Stripe-Account ID in both backend and frontend
for Destination charges or Separate charges and transfers -> You don't need to pass the Stripe-Account ID.

rough bear Jun 6, 2022, 5:36 AM

#

got you point , gonna check it and if there were any issue gonna share it

#

thanks

#Am-Payment