dasad

[grand coral]

Hi there!

1. transfer_group: can't be updated or set
   Not sure, what makes you think this?
2. payment is automatically captured we can't make a hold
   Correct
3. we can't use PayPal
   Not sure about this, you could contact Stripe support https://support.stripe.com/contact
4. save card function is not available (https://stripe.com/docs/payments/save-and-reuse), so we can't store the card for future purchases
   If you use subscription, the card is automatically saved on the customer, so you can reuse the card for other payments

b. what the drawbacks of using the https://stripe.com/docs/payments/save-and-reuse approach for handling subscriptions are?
Yes you can create your own subscription logic, but it's extremely complex to do correctly. That's why we recommend to use Stripe Subscriptions (but not that there is additional fees to use Subscriptions)

c. which is your best practice for handling a subscription? (based on the fact that we are using a https://stripe.com/docs/connect with custom implementation)
We recommend creating Subscriptions, and the simplest way is to use Checkout Sessions. And yes this works with Connect.

[safe yoke]

👋 taking over for my colleague. Let me know if there's any follow-up Qs I can answer!

[dense compass]

Hi @grand coral @safe yoke thank you for your quick response:

1. transfer_group: can't be updated or set

Not sure, what makes you think this?

If I try to update it, it gives an error:

INFO Request to Stripe API method=post num_retries=0 path=/v1/payment_intents/pi_3MMTvkGx6YYDitgj08HcH0CG
ERRO Stripe API error status=400 error_message="Some of the parameters you provided (transfer_group) cannot be used when modifying a PaymentIntent that was created by an invoice. You can try again without those parameters." error_type=invalid_request_error idempotency_key=0c4a97a0-ba20-4f5f-9f72-c978145ddeb8 request_id=req_DXlowwgmc57pcb
INFO Response from Stripe API api_version=2019-12-03 elapsed=0.39897153101628646 idempotency_key=0c4a97a0-ba20-4f5f-9f72-c978145ddeb8 method=post path=/v1/payment_intents/pi_3MMTvkGx6YYDitgj08HcH0CG request_id=req_DXlowwgmc57pcb status=400
Stripe::InvalidRequestError: (Status 400) (Request req_DXlowwgmc57pcb) Some of the parameters you provided (transfer_group) cannot be used when modifying a PaymentIntent that was created by an invoice. You can try again without those parameters.

2. ok
3. ok will do
4. ok we need to better check this

b. what the drawbacks of using the https://stripe.com/docs/payments/save-and-reuse approach for handling subscriptions are?

Yes you can create your own subscription logic, but it's extremely complex to do correctly. That's why we recommend to use Stripe Subscriptions (but not that there is additional fees to use Subscriptions)
Is the complexity of coding or card/payment behavior? In other terms, from a customer perspective, are there differences in the implementations?

c. which is your best practice for handling a subscription? (based on the fact that we are using a https://stripe.com/docs/connect with custom implementation)

We recommend creating Subscriptions, and the simplest way is to use Checkout Sessions. And yes this works with Connect.
We are not using the Stripe checkout we have implemented our own checkout by using only the server and js APIs, so I think for us this is not a good solution.

[safe yoke]

Is the complexity of coding or card/payment behavior? In other terms, from a customer perspective, are there differences in the implementations?
It's basically coding/infrastructure complexity since you need to have a scheduler and other services to create the invoices, payments, receipts, etc.

We are not using the Stripe checkout we have implemented our own checkout by using only the server and js APIs, so I think for us this is not a good solution.
When using Stripe Subscriptions, we create invoices automatically for you. we have a couple of options of how you can handle payments, these are called collection_methods. In case of a send_invoice, each cycle we send the customer an email with the invoice and a url that they can visit to make the payment, but that's not what you're expecting from what I understood. The other option is called charge_automatically, where you first need to collect the Payment Method(PM) and we will use that for paying subsequent invoices

in order to do that, you should create a Subscription by using payment_settings.save_default_payment_method with a value of on_subscription and expanding on latest_invoice.payment_intent. Once you do that, you get the latest_invoice.payment_intent.client_secret to your frontend and use it with Stripe Elements to collect the PM. Once confirmed this PM will be used to pay the subsequent invoices