...
We've introduced a new internal concept called 'Transfer Group' when a transfer is initiated. This concept enables TIXNGO to organize and process tickets transfer more intuitively, leading to:
Enhanced transfer performances
Improved Wallet user experience by simplifying the display of tickets and transfers on mobile, starting with grouping and ordering on transfer-related screens
New concept: “Transfer Direction”
We’ve introduced a new internal concept called ‘Transfer Direction’, together with the ‘Transfer Backward’ setting in the V4 Usage Rule, to improve transfer level computation and simplify related mobile processes (e.g. Return Ticket, Edit Transfer Recipient).
Transfer Direction supports two values:
FORWARD – when a ticket is transferred from Spectator A to Spectator B.
BACKWARD – when a ticket is transferred back from Spectator B to Spectator A, either via the "Return to sender" button or by manually entering the original sender’s email and re-initiating the transfer.
New concept: Indi
A
A
Transfer Level computation
As of TIXNGO V3, the number of transfers allowed for a ticket is determined by the combination of its transfer level (i.e. the number of successful transfers already completed) and the transfer limit, which is defined in the Ticket Usage Rule (also referred to as the "Maximum number of transfers allowed").
By default, after injection, the transfer level of a ticket is 0 (zero).
Forward transfer
Context: Spectator A want to transfer his ticket to Spectator B.
His ticket is newly injected and its the transfer level is 0 and its transfer limit at 3 via the Usage Rule applied.
Because the transfer level (0) is below the transfer limit (3), the transfer can be initiated.
Once accepted by Spectator B accepted the transfer: