#theofenol_invoice-connect
harsh trenchBOT
👋 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/1303452634312605726
📝 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.
- theofenol_docs, 1 day ago, 31 messages
fossil lichen
Hi! I am currently using Invoices with Direct Charges and always creating a new customer instance. As advised, I would like to change to Destination Charges. I am wondering if there would be any problem if I am not saving the customers and I am always creating a new customer instance.
Moreover, what would be the correct API call for the invoice?
wintry mason
Hi there 👋 yes, you can create multiple Customer objects that have the same email.
There is no default deduplication on those.
fossil lichen
const invoice = await stripe.invoices.create({
customer: customer.id,
auto_advance: false,
application_fee_amount: req.finerFee,
payment_settings: {
payment_method_types: ['card'],
},
},
{
stripeAccount: req.connectedAccountId,
});
this is my current call
i assume it would become something like this:
const invoice = await stripe.invoices.create({
customer: customer.id,
auto_advance: false,
application_fee_amount: req.finerFee,
payment_settings: {
payment_method_types: ['card'],
},
},
transfer_data: { destination: connectedAccountId });
harsh trenchBOT
theofenol_invoice-connect
fossil lichen
would this be correct? my platform will keep req.finerFee and the rest will go to my connected account?
Where will the stripe fee be taken from?
wintry mason
Yup, that looks right! But let me know if you run into errors while testing that.
Destination Charge flows assess Stripe fees on the Platform account:
https://docs.stripe.com/connect/charges#stripe-fees
fossil lichen
and one last question, is it possible to get only the receipt?
I noticed there is a hosted invoice url which shows also the invoice
There are 2 buttons, one for the invoice and one for the receipt. I am curious if it would be possible to get just the receipt
Or this will be sent automatically if I turn on the customer email feature from my dashboard?
My ideal scenario would be to extract a hosted url of the receipt only and include that in the validation email that I will send to the customers
wintry mason
I don't think you can get that directly from the Invoice object, but believe you should be able to find it on a related object once the Invoice has been paid.
From the Invoice you can find the related Payment Intent:
https://docs.stripe.com/api/invoices/object#invoice_object-payment_intent
then use the latest_charge field on the intent to find the related Charge object:
https://docs.stripe.com/api/payment_intents/object#payment_intent_object-latest_charge
Then the Charge object has a receipt_url field where you can view the receipt:
https://docs.stripe.com/api/charges/object#charge_object-receipt_url
I believe the emails you're referring to send an Invoice for payments related to Invoices, but I would recommend double checking that with our Support team:
https://support.stripe.com/?contact=true
They're more familiar with the prebuilt email behavior than we are here in this forum.
fossil lichen
thanks!