Uniticket

📘

Limited to a certain acquirer in Spain

👍

Available soon

Uniticket is a ticket vending system in Spain. Merchants using this system can send the ticket booing fee and number of tickets along with the payment request to our gateway.

Supported messages

The extension is supported for nexo protocol in the following messages:

Number of tickets

Add one SaleItm occurrence under Tx/TxDtls.

PdctCd and PdctAmt are mandatory in the nexo SaleItm structure. For Uniticket, the Gateway interprets the combination AddtlPdctCd=Tickets and UnitOfMeasr=PIEC as the ticket unit of measure and forwards the value as tickets to the downstreaming applications. PdctQty contains the corresponding ticket count.

Booking fee

Declare the booking fee in DtldAmt/Fees under the same transaction details.

If more than one Fees entry has the exact label BookingFee, the Gateway adds their amounts and processes the sum as the ticket-booking fee. Entries with a different label are not treated as a Uniticket booking fee.

Presence values: m = mandatory, c = conditional, o = optional.

Amount rules

• TxDtls/TtlAmt must include the booking fee.
• TxDtls/DtldAmt/AmtGoodsAndSvcs should contain the goods-and-services amount before the separately declared booking fee.
• The total amount and its detailed components must reconcile. An inconsistent breakdown is rejected as an invalid amount.
• All Uniticket amount components must be expressed in the merchant currency.
• The booking-fee extension is not applied when the cardholder has accepted Dynamic Currency Conversion (DCC), or to a decremental preauthorization.

Request example

The following fragment represents two tickets with a total ticket price of EUR 100.00 and a booking fee of EUR 5.00:

<TxDtls>
  <Ccy>EUR</Ccy>
  <TtlAmt>105.00</TtlAmt>
  <DtldAmt>
    <AmtGoodsAndSvcs>100.00</AmtGoodsAndSvcs>
    <Fees>
      <Amt>5.00</Amt>
      <Labl>BookingFee</Labl>
    </Fees>
  </DtldAmt>
  <SaleItm>
    <PdctCd>Uniticket</PdctCd>
    <AddtlPdctCd>Tickets</AddtlPdctCd>
    <UnitOfMeasr>PIEC</UnitOfMeasr>
    <PdctQty>2</PdctQty>
    <PdctAmt>100.00</PdctAmt>
  </SaleItm>
</TxDtls>

Include this fragment in the normal transaction body for the applicable nexo message and version. All other mandatory message fields remain unchanged.

Response behavior

The Gateway returns the standard response for the submitted authorization request or completion advice. The extension does not add Uniticket-specific response elements.

👍

Integration checklist

• Send PdctCd as Uniticket.
• Send AddtlPdctCd exactly as Tickets.
• Send UnitOfMeasr exactly as PIEC.
• Supply both PdctQty and PdctAmt for every Uniticket sale item.
• Use the exact, case-sensitive fee label BookingFee.
• Include the booking fee in TtlAmt and ensure that the detailed amounts reconcile.
• Do not use the booking-fee extension for accepted-DCC or decremental-preauthorization transactions.