1 messages · Page 1 of 1 (latest)
If you don't use legacy integration then PaymentIntentId should be good to go
One paymentintent cannot have multiple charges(/transactions)?
It can, like multiple attempts, but it's still the same "intent"
meaning it still represent 1 transaction