Not all payments in `AdyenCheckout` sessions `onComplete` are/will be completed

[johanehinger]

Adyen Sessions onComplete will sometimes have payments with a result code other then Authorised.

For example the Swish payment method will sometimes trigger the onComplete with the result code Received. This is a intermediate result code and could end up not being a successful payment.

      <AdyenCheckout
        config={checkoutConfiguration(configuration)}
        session={session}
        // Sometimes `onComplete` is called with a intermediate result code that could end up being a failed payment.
        onComplete={didComplete}
        onError={didFail}
      >

To Reproduce

Steps to reproduce the behavior:

1. Try and pay with Swish
2. Sometimes payments trigger the onComplete with Received result code instead of Authorised and sometimes they will end up with Cancelled as the final state.

Expected behavior

onComplete should only happen if a payment is completed.

Additional context

This feels like a race condition?

[descorp]

Hey @johanehinger

Thanks for reaching out!

That behavior is expected for Open Banking and some local payment methods. You can find more details in the Adyen Docs.

Generally, webhooks are the ultimate source of truth for the transaction state. Depending on the payment method, finalization can take anywhere from miliseconds to hours, so your payment system and UI must be prepared to handle "pending" statuses.

---

Are you making GET 'sessions/{sessionId}?sessionResult=${sessionResult}`call?
In some cases it might provide definitive answer in real time.

[johanehinger]

Thank you for a quick response, we have one way to check the status for payments via our own backend, but your provided method looks a lot faster. Thank you we will implement that!