ironbeard

[summer sphinx]

You could use the card element twice if you wanted to. The element is obviously not persistent across sessions, so you'd have to make the 2 charges simultaneously, but it could be done.

[iron marlin]

Hmm, could you explain a little more?

As in, just make the POST to the server twice, once for the Subscription and once for the Saas, getting back two client secrets and then calling confirmCardPayment once for each secret?

[summer sphinx]

Exactly. You'd just want to do some operations once (e/g/ creating the Payment Method and Customer) and then do other operations twice on the client-side (e.g. charging the card with the client secret)

[iron marlin]

(or I guess, it would only require a single POST to the server, then create two Subscriptions and send back two client secrets if relevant)

Cool cool, I think I'll try to implement that.

Somewhat related, how do I specify the "info" line that shows up in the customer's bank account? I want to make sure one says "[Company Name] Newsletter" and the other mentions the SaaS

[summer sphinx]

Definitely!

You're looking for statement_descriptor_suffix: https://stripe.com/docs/account/statement-descriptors#dynamic

[iron marlin]

Great, thanks!

Is there a way to see what the default would be if not using the suffix dynamically?

[summer sphinx]

You set the default in the Stripe Dashboard: https://dashboard.stripe.com/settings/public