#junaid_abbasi999

1 messages · Page 1 of 1 (latest)

silk lakeBOT
#

Hello! We'll be with you shortly. 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.

edgy bridge
#

hi, can you expand on that? what receipt, and how are you using Connect(Direct or Destination charges?)

dire lichen
#

I am talkin about the receipt that is sent to account when I use paymentIntent.charge. and I am doing destination charges

naive dagger
#

What do you mean by "use paymentIntent.charge." exactly?

dire lichen
#

I am talking about when i create a charge using an api and if it's successfull.... the customer gets a receipt.

dire lichen
naive dagger
dire lichen
#

connect account = destination attribute i mention while creating the chargs

naive dagger
#

That's different.

#

Could you please share the PaymentIntent ID pi_xxx?

dire lichen
#

I don't have nay yet I am just in test phase, and right now i don't have access to stripe dashboard

naive dagger
#

How are you creating charges?

dire lichen
#

const paymentIntent = await stripe.paymentIntents.create({
amount: amount,
currency: "cad",
confirm: true,
customer: customerId,
payment_method: paymentMethodId,
off_session: true,
receipt_email: receipt_email,
transfer_data: {
destination: destination,
},
application_fee_amount: applicationFee,
receipt_email: receipt_email,
description: description,
metadata: metadata,
});
return paymentIntent;

naive dagger
#

paymentIntent variable will have an ID, that's what I was asking for.

#

You need to add the on_behalf_of parameter in your request, as in the article that I shared.

#

Please read it carefully and let me know if anything is not working as expected.

dire lichen
#

Yes I got that.... thanks.... and other thing I can only mention the on_behalf_of parameter while I am creating the paymentIntent as mentioned in the api..... but my usecase is I don't know the on_behalf_of when i am creating the paymentIntent..... I know about it when I am capturing it.... Can I update the on_behalf_of before capturing, because I don't see on_behalf_off optional parameter in this api https://stripe.com/docs/api/payment_intents/update

naive dagger
#

I don't think it's possible. What you can do instead, is cancel the PaymentIntent that holds the funds, and create and capture a new one that has on_behalf_of

dire lichen
#

No i can't do that because I am capturing the hold if the actual payment fails for some reason..... and if payment is successfull then I am releasing the hold

naive dagger
#

I don't think I understand. Are you creating 2 PaymentIntents already?