Skip to main content
Scrive logoeID Hub Documentation

Result Handling

Both URLs are set when creating a transaction and serve as the two ways your backend gets notified when a transaction finishes.

redirectUrl​

When the end-user completes or abandons the flow, the Hub redirects them to redirectUrl. Two query parameters are appended:

  • transaction_id — use this to look up the transaction result
  • success — true or false

This is how your frontend knows the user is done. From redirectUrl you query the transaction to get the full result.

callbackUrl​

An optional server-to-server notification. When a transaction reaches complete or failed, the Hub immediately POSTs to callbackUrl with a JSON body containing transactionId, status, and eventTime.

The callback arrives as soon as the transaction settles. Your backend does not need to wait for the user to reach redirectUrl. For production integrations, a callback is more reliable than polling.

Using both together​

redirectUrl and callbackUrl serve different roles and are typically used together. The callback lets your backend process the result the moment it is available. The redirect brings the user back to your UI so you can show them the outcome.