Juno Portal: Transaction statuses

Overview

A single payment in the Juno Portal can generate several events over its lifetime — for example an authorisation followed later by a capture, or a refund. The Portal uses a consistent set of rules to work out each transaction's status from these events, but status can remain temporary while later events are still arriving, regardless of the order they arrive in. This article explains what each status means and why a status can briefly differ from what you see in your PMS.

Applies to

Product	Juno Portal
Feature	Transactions — status
Audience	All Juno Portal users

What you'll achieve

You'll know what each transaction status means, why a status might temporarily differ between the Portal and your PMS, and when a status that looks wrong is actually expected.

Before you start

Open the transaction's lifecycle view if you want to see the individual events behind a status, rather than relying on the status alone.

What each status means

Completed	The payment has been captured or settled as a completed payment event.
Authorised	The card was approved and an authorisation hold may exist, but the payment has not yet been completed.
Partially Refunded	A portion of the captured amount has been returned to the cardholder.
Fully Refunded	The full captured amount has been returned to the cardholder.
Voided	The authorisation was cancelled before completion.
Unknown	There's not yet enough event data to determine a status. This typically resolves automatically as further events arrive from your payment provider.

Why a status may differ from your PMS

Events from your payment provider don't always arrive in the order they occurred — a refund event can reach the Portal before the corresponding capture event. The Portal applies consistent precedence rules to work out status regardless of arrival order: a void takes precedence over a refund, and a refund over a capture. Status can remain temporary while events are still arriving, so it may briefly differ between systems; it typically settles once every event has arrived.

A transaction still shows Authorised after check-out

If a transaction shows as Authorised after the guest has departed, the capture event may still be in transit from the gateway, or the pre-authorisation hold may not yet have been released. If the status remains Authorised beyond the expected settlement window for your acquirer, contact 934 Support with the transaction ID and date.

Expected result

You can read any transaction's status with confidence, and recognise when a mismatch with your PMS is a normal, temporary timing effect rather than an error.

Need more help?

If a status remains Authorised beyond your acquirer's expected settlement window, or a status otherwise looks wrong after all events should have arrived, contact 934 Support through Help & Support in the Portal or at support@weare934.com with the transaction ID and date. Don't send full card numbers, login credentials, or other sensitive account details by email or chat.

Related to