+++ PAGE UNDER CONSTRUCTION +++
Info |
---|
Dear customer, Please note that:
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.
Reference Documents
The complete catalog of official ISO 20022 CAPE messages, including the Message Definition Reports (MDR) and XML Schemas, is available on the ISO 20022 official Web site (http://www.
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.
Nexo Acquirer Data Fields
No show without a transaction log iso20022.org) All other CAPE or nexo related information can be found by visiting the nexo Web site (http://www.nexo-standards.org).
Nexo specification for No-Show service can be found in documents :
nexoFAST Part. 1 version 3.3, section 6.2.10 (No-Show)
Nexo IS version 5.0, section 5.2.2 (No-Show Service)
Processing
The merchant can start a No Show transaction using a reservation Tx. reference or with Moto Manual Entry. No show will result in two acquirer exchanges: Authorisation and completion.
No Show With Tx. Reference With Tx. log | Not supported currently
|
No Show With Tx. reference Whitout Tx. log | In Authorisation online request
|
...
| |
No Show With MoTo Manual Entry | In Authorisation online request
|
Enable No-Show Service
To enable the No-Show Service:
Define a No-Show service entry in the Service Settings Table (E4).
'DF01' = '0x13' - NO-SHOW
'05' : UPDATE PRE-AUTH
'06' : PAYMENT COMPLETION
Add the No-Show Service in the list of configured service in Terminal Data (E1) using:
'DF13' - Configured Services[2, 4] = 1b (No-Show)
or'DF67' - Configured Services Extended[2, 4] = 1b (No-Show)
Optionally, activate the transaction log in Terminal Data (E1) using:
'DF13' - Terminal Settings [3, 4] = 1b (Retrieve Pre-Auth from Tx. log)
Arkos API
See Amadis Developers' Guide page on No-Show Service for more information.
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. So Nexo Specification (Figure 58: No-Show Specific Processing) has been modified as following:
...