4. Wait for confirmation/screening

GET /api/v1/checkout/:uuid/wait

After a successful payment and the IPN processed by the merchant, the order will be confirmed. But this is an asynchronous process, and this endpoint will return the status of it.
Example of response:

{
  "action": "show_on_hold"
}

Action	Description	Additional Fields
`finish`	The order has been confirmed and the checkout can be finished.	return_url (optional)
`show_conflict`	After sending the IPN, the merchant responded with HTTP 409 or 410.
`show_on_hold`	The order is on hold.	return_url
`wait_for_screening`	The order is in screening process. It has the extra param `expires_in`.	expires_in (seconds)
`resume_after_screening`	The screening process has been resolved or expired. The identification should be updated again to know the new status.
`wait_for_confirmation`	The order has not been confirmed yet. Keep waiting.
`wait_for_on_hold`	The on hold state has not been confirmed yet from the merchant. Keep waiting.
`alt_payment`	Selected credit agreement has been rejected, but Sequra offers and alternative payment method	title, messages, credit_agreements, forced_credit_agreement_index, errors
`wait_for_id_verification`	ID verification in progress	session_url, status (STARTED, VERIFIED, FAILED, ERROR), message
`show_identification_form`	Identification form with optional validation errors	errors (optional)
`require_payment`	Payment required	iframe_url, amount, reusable_cards
`require_validate_otp`	OTP validation required, to show the form to capture the OTP
`show_error`	Error occurred
`reject`	Order rejected

Special metadata on some actions

{
  "action": "finish",
  "return_url": "..."
}

Webhook events

Receiving actions via webhook

Instead of polling the /wait endpoint, you can receive identification action updates as webhook events. When enabled, seQura sends a POST request with a JSON payload to your configured events_webhook URL on every order state change.

Payload example

  {
    "event": "identification_action",
    "action": "wait_for_id_verification",
    "session_url": "https://magic.veriff.me/...",
    "status": "STARTED",
    "message": "",
    "order_ref": "order-uuid",
    "order_ref_1": "merchant-ref-1",
    "order_ref_2": "merchant-ref-2"
  }

The payload includes the same action and additional fields as the polling endpoint response, plus standard order references and any merchant-configured webhook parameters.

To enable this feature, contact the seQura integration team to activate the send_action_events_in_identification option for your merchant account.