#tristanoneil-charge-pending

1 messages · Page 1 of 1 (latest)

stoic cypress
#

@tidal shard do you have more details? In which context?

tidal shard
#

a BACS payment initiated through a stripe checkout session

stoic cypress
#

So it's not fired immediately because we need to wait a few days I think before we can debit the account

#

you would listen to checkout.session.completed events and then wait for the payment_intent.succeeded event later when it succeeds

tidal shard
#

Hmm the test API implies that it is ... for instance 90012345 the charge.pending event is fired almost immediately even though the charge is not processed until 3 minutes after the session has been completed.

stoic cypress
#

It's possible, I personally would not rely on when is charge_pending sent because that shouldn't matter to your code

#

what matters is the state of the Checkout Session until it completes and then the status of the PaymentIntent itself

#

Does that make sense?

#

I think you're right though and I was wrong, for BACS we debit immediately we don't need to wait so the charge is pending early. For ACSS Debit (same in Canada) we have to wait 3 days to debit

tidal shard
#

Kind of, in our case we're trying to sync data about the charge before it's finalized so using the charge.pending event comes in handy if we can rely on it.

#

Specifically we want to sync the charge_id

#

The use case is persisting data in our general ledger when the user initiated payment rather than when the payment was completed.

#

... and we remove the data at a later time if the payment failed.

stoic cypress
#

why not store the PaymentIntent id pi_123 instead?

tidal shard
#

That's a possibility ... it's mostly for consistently since we store charge_id for our other payment methods. That requires talking to stake holders 😆

#

Anyway, thanks!