#bachir
1 messages · Page 1 of 1 (latest)
Hi there, based on the doc (https://stripe.dev/stripe-terminal-ios/docs/Classes/SCPPaymentIntentParameters.html#/c:objc(cs)SCPPaymentIntentParameters(py)transferDataDestination), you specify the transfer_data[amount] at capture time.
Hey Jack, I have capture_method set to automatic so I do not call capturePaymentIntent explicitly. Do you think I'll have to change that ?
I do call confirmPaymentIntent once the payment method is properly collected, could it be passed at that point ? (I don't see it in the docs)
Hmm, it looks like there's no way to specify a transfer_data[amount] when creating a PaymentIntent. You might want to use application_fee_amount instead
I'd rather not use application_fee_amount because we already use transfer_data[amount] in other payment flows, it would get confusing for us. Do I just separate PI creation and capture in this case ?
I suppose that could work, you could pass https://stripe.com/docs/api/payment_intents/capture#capture_payment_intent-transfer_data-amount at capture time from the backend
incidentally the reason Terminal doesn't support this option is because in theory application_fee_amount is better since it leads to clearer reporting by explicitly creating ApplicationFee objects etc
I see thanks - We do not use the application_fee_amount because we process payments for non-profits, those payments can optionally contain tips for our platform, but technically we do not take any application fee on the payment made to the non-profit.