Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel1
outlinefalse
stylenone
typeflat
printabletrue
Info

Ticket transfers are at the core of the TIXNGO experience—they’re what make secure, digital ticketing truly flexible and user-centric. With V4, we've reimagined the transfer process from the ground up, introducing a more robust and transparent framework. This new foundation brings greater consistency, improved control, and enhanced clarity for both spectators and organizers, while preserving the secure and trusted principles that define TIXNGO.

New concept: “Transfer Group”

...

  • 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 Transfer Level computation

As of TIXNGO V3, the number of transfers allowed for a ticket is determined by the combination of its :

  • The transfer level (i.e., the number of successful transfers already completed)

...

  • The transfer limit,

...

  • defined in the Ticket Usage Rule (also

...

  • known as the "Maximum number of transfers allowed").

By default, after injection, the a ticket’s transfer level is 0.

Transfer Level and New Transfer Counters in TIXNGO V4

To enhance visibility and understanding of transfer behavior on a ticket is 0 (zero).single ticket, the V4 ticket model maintains the transfer level and introduces two new dedicated counters:

  • forwardTransfers — Total number of Forward transfers successfully completed

  • backwardTransfers — Total number of Backward transfers successfully completed

Forward transfer

Context: Spectator A wants to transfer his ticket to Spectator B.

...

  • The current owner becomes Spectator B.

  • The previous owner becomes Spectator A.

  • The initial owner remains unchanged.

  • The transfer level is 1.

  • The forwardTransfers count is 1.

  • The backwardTransfers count is 0.

Backward transfer

Context: Spectator B wants to return his ticket to Spectator A.

...

  • The current owner becomes Spectator A.

  • The previous owner becomes Spectator B.

  • The initial owner remains unchanged.

  • The forwardTransfers count is 1.

  • The backwardTransfers count is 1.

  • The transfer level update depends on the “Transfer backward” setting defined in the Ticket Usage Rule.

Transfer backwardSetting

Description

Transfer Level Change

Example

NEUTRAL

The backward transfer does not count toward the transfer limit.

No change

1 → 1

DECREASE

The backward transfer restores the transfer level to its state prior to the last forward transfer.

−1

1 → 0

INCREASE

The backward transfer counts as a new transfer, like any other transfer.

+1

1 → 2

Consistent behavior for transfer acceptance

With TIXNGO V4, the existing setting to enable or disable transfer acceptance has been retained.
The key change from V3 is that transfer acceptance now applies to all transfer directions—both forward and backward.

When the setting is enabled:

  • For FORWARD transfers (Spectator A → Spectator B), Spectator B must accept the transfer (as in V3).

  • For BACKWARD transfers (Spectator B → Spectator A), Spectator A must now accept the transfer (new in V4).