#JohnM-payments
1 messages · Page 1 of 1 (latest)
pi_3LX9pSHFDCZvO5mL1kfe4IdD
I see the balance transaction in the console, but the call in the java SDK does not appear to be returning it
ChargeCollection chargeCollection = paymentIntent.getCharges();
charges.get(0).getBalanceTransaction() is null
only 1 item in collection
You're not getting it back from your Java creation reqeust because Bank Account payments have an initial "processing" state before the payment is fully successful (we consider it to be "delayed notification payment method"). That's why we say you need to listen for the Payment Intent events so you know when it's finally failed or successful (see https://stripe.com/docs/payments/ach-debit/accept-a-payment?platform=web&ui=API#web-confirm-paymentintent-succeeded)
so, why does it work on credit card payments ?
Beacuse credit cards are NOT a delayed notification payment method - we know whether it's failed or successful immediately
I am transitioning from the legacy charge api's to the payment intent .... and the charge API supported a balance transaction immediatly
Legacy ACH had the same issue though - it was still a delayed notification type and wouldn't send a charge.succeeded notification until days later
I got a balance transaction as part of the charge object created. It gave me the fees' associated with the charge, as well as the estimated date of settlement. It had nothing to do with completion or failure of payment.
I still see the balance transaction in the console...