Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

+++ PAGE UNDER CONSTRUCTION +++

Info

Dear customer,

Please note that:

  • No-Show service with transaction log is not supported currently.

  • Arkos allows additional features that are not documented in the nexoFAST 3.2 documentation. One of these features is it to allow No-Show transaction without transaction log.

For more information, you can reach to our team.

Definition

No-Show is a service that allows the card acceptor to charge the cardholder's account if a cardholder fails to cancel or use a reservation for car hire or a room rental.

Arkos allows additional features that are not documented in the nexoFAST 3.2 documentation. One of these features is it to allow No-Show transaction without looking for the transaction in the transaction log.

This is essential for terminal that are configure to do pre-auth without transaction log.

Reference Documents

  • Nexo Acquirer

Processing

The merchant can start a No Show transaction using a reservation reference or with manual entry of Card data information. No showwill result in two acquirer exchanges: Authorisation and completion.

  • If No-Show is started unsing a reservation reference, the original transaction can be retrieved from the transaction log if configured, and an authorisation request is sent online to acquirer. If the transaction log is not configured, Card element will not contain either ProtectedCardData or PlainCardData since no card data is available

  • If No-Show is started using manual entry, an authorisation request is sent online to acquirer. Card element will contain either ProtectedCardData or PlainCardData

No Show using a reservation reference with transaction log

Not supported currently

No Show using a reservation reference whitout transaction log

 

No SHOW using card manual entry

 

 

Configuration

 

Arkos API

Sequence Diagrams

Modifications to No-Show Specific Processing

No-Show Specific Processing needs to take into account the Terminal Settings in order to bypass retrieving information for Tx. log. This is quite similar to how it is done for cancellation and pre-auth completion.

Nexo Acquirer Data Fields

No show without a transaction log will result in two acquirer exchanges: Authorisation and completion.

Card element will not contain either ProtectedCardData or PlainCardData since no card data is available.