Example Scenario

A complete walkthrough of a festival cup deposit flow.

Setup

An organizer creates a configuration for the "Summer Festival" organization with two container categories:

Category	Deposit	Expiration
0.5L Cup	500 HUF	48 hours
0.3L Cup	300 HUF	48 hours

Products are mapped: beer uses the 0.5L cup, wine uses the 0.3L cup.

1. Guest Orders Drinks

A guest orders 2 beers and 1 wine. The POS creates a transaction:

POST /v1/integrations/hybrid-revo-token-transactions

[
  { "productId": "beer_500ml", "quantity": 2 },
  { "productId": "wine_300ml", "quantity": 1 }
]

The system responds with a transaction code and a short code (e.g. 7KQ2ZP). The guest receives:

• 2x 0.5L Cup + 1x 0.3L Cup
• Total deposit charged: 1,300 HUF (2 x 500 + 1 x 300)
• Transaction code printed on receipt as a QR code, with the short code next to it

Organization & Place Name

The organization name and place (business unit) name displayed on the receipt come from the /v1/integrations/me endpoint.

For up-to-date logo assets, brandbook, and other design resources, see the Brand Assets folder.

2. Guest Returns Next Day

The guest returns with 2 large cups. The operator scans the QR code -- or, if it is unreadable, types in the short code 7KQ2ZP -- and previews. Either one goes in the {code} path parameter:

GET /v1/integrations/hybrid-revo-token-transactions/{code}/preview

[
  { "category": { "id": "cat_001", "depositGross": 500, ... }, "activeItemCount": 2 },
  { "category": { "id": "cat_002", "depositGross": 300, ... }, "activeItemCount": 1 }
]

The operator validates the return of 2x 0.5L cups:

POST /v1/integrations/hybrid-revo-token-transactions/{code}/validate

[
  { "hybridRevoTokenCategoryId": "cat_001", "quantity": 2 }
]

Result: Guest receives 1,000 HUF refund (2 x 500). The 0.3L cup remains active until the 48-hour window expires.

3. Expiration

The guest never returns the 0.3L cup. After 48 hours, the system automatically sets the item to EXPIRED status. The 300 HUF deposit is forfeited.

Final State