#anrighiwr_api
1 messages ยท Page 1 of 1 (latest)
๐ 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/1351958930577686661
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi ๐
That is not possible. Each Subscription will create it's own Invoice and each Invoice will have it's own Payment Intent.
But can you clarify that you want to build? Does it make sense to bill customers regularly for donations and tips?
Also could you not just use two Subscription Items?
i need that the two subscriptions are independent from one another
Do they have separate billing cycles?
my use case is:
- donation subscription should be transfered to a company connected account
- tip subscription should remain on the platform balance
they have the same billing cycle, but you should be able to deactivate just the tip, without editing the donation sub
So this is a Connect integration? You know you can split up those funds to transfer only some of the funds.
yes we tried with transfer_percent, but we would like to keep the application_fee creation
You can use application_fee_percent instead https://docs.stripe.com/api/subscriptions/create#create_subscription-application_fee_percent
but we have two cases:
- a user who just makes a donation, without tip (15โฌ)
- a user who makes donation + tip (15+2)
we want in both case that the connect account sees the same fee deducted - using application_fee_percent they would see two different amounts
in a past thread, another moderator said it was possible: #1351876047976661052 message
but as you can see from the req_id i shared, we tried that and it is not working
In that case you save the Payment Method first, using a setup intent and the charge the saved payment method for each Invoice
The request you shared is sending a Payment Method that then triggers 3DS.
so what should be the flow?
- frontend creates a confirmation token
- backend creates a setup intent
- frontend confirms (?) setup intent
- backend creates and confirm 2 subscriptions
Yes, you need to confirm the setup intent to save this payment method to the customer. Is there a reason you are using confirmation tokens? Do you want to inspect the payment method first?
we implemented them to show saved payment methods to the user
That isn't directly relevant AFAIK. You can re-display payment methods saved directly with a Setup Intent as well.
Sorry, AFAIK = As Far As I Know
it was when we implemented it, it was in a beta stage
Ah. Well, regardless you would need to confirm the Setup Intent. And you should see 3DS being triggered when you attempt to confirm the Setup Intent (if required by the issuing bank).
can you share me a docs how to configure a setup intent?
Here is our canonical integration guide for Setup Intents: https://docs.stripe.com/payments/save-and-reuse
thanks