Change Details

See the saga of contribution_tracking_id 56015715: On the payments cluster, the auth&capture times out: TransactionTimedOut. We send a payment_init message with 'failed' payments_final_status, and the payments_init consumer deletes the pending db entry. Apparently, that DOESN'T mean it's been failed / canceled. We ALSO get a listener notification that says the auth is declined, for reason 'TransactionTimedOut'. That seems to be misleading, because the next day we get another listener notification saying the capture has succeeded. We try to record the successful capture, and that sends a failmail because the donor details are gone from the pending db. We should probably be optimistic, and send the payments_init message with 'pending' payments_final_status while showing the donor the Thank You page.

See the saga of contribution_tracking_id 56015715: On the payments cluster, the auth&capture times out: TransactionTimedOut. We send a payment_init message with 'failed' payments_final_status, and the payments_init consumer deletes the pending db entry. Apparently, that DOESN'T mean it's been failed / canceled. We ALSO get a listener notification that says the auth is declined, for reason 'TransactionTimedOut'. That seems to be misleading, because the next day we get another listener notification saying the capture has succeeded. We try to record the successful capture, and that sends a failmail because the donor details are gone from the pending db. We should either be optimistic (send the payments_init message with 'pending' payments_final_status while showing the donor the Thank You page) or make sure the order is canceled / closed.

See the saga of contribution_tracking_id 56015715: On the payments cluster, the auth&capture times out: TransactionTimedOut. We send a payment_init message with 'failed' payments_final_status, and the payments_init consumer deletes the pending db entry. Apparently, that DOESN'T mean it's been failed / canceled. We ALSO get a listener notification that says the auth is declined, for reason 'TransactionTimedOut'. That seems to be misleading, because the next day we get another listener notification saying the capture has succeeded. We try to record the successful capture, and that sends a failmail because the donor details are gone from the pending db. We should probablyeither be optimistic, and (send the payments_init message with 'pending' payments_final_status while showing the donor the Thank You page) or make sure the order is canceled / closed.