andywells-customeremail

[sly citrus]

@potent hamlet it's generally not required no(but a couple of payment methods do need an email, like SEPA Debit). It's a good practise though so you have a way to contact the customer later in case of refunds/chargebacks.

[potent hamlet]

gotcha, if we're only setting the payment_method_type to "card" is this OK then?

also: is it necessary to cancel payment intents? e.g. if a user starts making a payment, quits the browser and then re-tries, we'll create a new intent. is it expected we update the old intent and cancel it?

[sly citrus]

it's not required a technical level no, all you really need is the amount/currency, and the card details of number/expiry/CVC, everything else can be optional. But we would recommend you collect as much info as is reasonable for you (balanced against what you think might put customers off and harm your conversion) as it all helps to prevent fraud https://stripe.com/docs/disputes/prevention/best-practices (like if a customer gives you a sharklasers email address or you see multiple payments from different countries but the same email address, it all helps give some context on what might be fraud or not)

you don't need to cancel PaymentIntents nope, you can just ignore them and create a new one if the customer refreshes the page etc like the case you describe

[potent hamlet]

awesome: for context, we're capturing the email on our side but don't want to send to Stripe because we can't control the customer's platform settings

we're using a standard connected direct charges integration

and want to send confirmation emails to payers ourselves

so i think this is the only option? is that correct?

[sly citrus]

I suppose that's fair enough! but it makes you completely reponsible for the customer support for example