Definition

A Reservation service is a transaction initiated by an Acceptor to make reservation of an estimated amount, for a certain time preceding the consumption of a service or delivery of goods and the actual payment. It consists in:

• An Initial Reservation for an estimated amount of the purchase and a period of time to perform
  the purchase,

• Optionally, one or several Update Reservation(s) when the condition of the reservation is changing,

• And finally, a Completion after the consumption or delivery to complete the payment transaction with the actual amount.

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.iso20022.org) All other CAPE or nexo related information can be found by visiting the nexo Web site (http://www.nexo-standards.org).

Processing

Configuration

Enable Reservation Service

To enable the Reservation Service:

1. Define the following services proprieties in the Service Settings Table (E4).

   1. '04' : PRE-AUTH

   2. '05' : UPDATE PRE-AUTH

   3. '06' : PAYMENT COMPLETION

2. Add the Pre-Authorisation Service in the list of configured service in Terminal Data (E1) using:

   1. 'DF13' - Configured Services[1, 5] = 1b (Pre-Authorisation) or

   2. 'DF67' - Configured Services Extended[1, 5] = 1b (Pre-Authorisation)

3. Add the Update Pre-Authorisation Service in the list of configured service in Terminal Data (E1) using:

   1. 'DF13' - Configured Services[1, 4] = 1b (Update Pre-Authorisation) or

   2. 'DF67' - Configured Services Extended[1, 4] = 1b (Update Pre-Authorisation)

4. Add the Payment Completion Service in the list of configured service in Terminal Data (E1) using:

   1. 'DF13' - Configured Services[1, 3] = 1b (Payment Completion) or

   2. 'DF67' - Configured Services Extended[1, 3] = 1b (Payment Completion)

Enable Reservation Service Cancellation

Cancellation of Pre-Authorisation

To allow the Cancellation of Pre-Authorization, set 'DF28' - Application Profile Settings(APS) for Cancellation [1, 6] = 1b (Cancellation of Pre-Authorisation)

Cancellation of Payment Completion

To allow the Cancellation of Payment Completion, set 'DF28' - Application Profile Settings(APS) for Cancellation [1, 5] = 1b (Cancellation of Payment Completion)

Reservation Validity Period Handling

For validity period handling, a configurable parameter Pre-Authorisation Validity Number of Days is optionally stored in the Application Profile and, if present, indicates the maximum validity period for a Pre-Authorisation and an Update Pre-Authorisation according to scheme rules.

If the Pre-Authorisation Validity Number of Days is not present, then a default value of '00 00' will be used, meaning that the Acceptor provides no estimated time period of the purchase to reserve.

Data Transmission

x

x

Message Examples

Connected POI

<?xml version="1.0" encoding="UTF-8"?>
<SaleToPOIRequest>
<MessageHeader MessageClass="Service" MessageCategory="Payment"
MessageType="Request" ServiceID="642" SaleID="SaleTermA"
POIID="POITerm1"/>
<PaymentRequest>
 <SaleData>
  <SaleTransactionID TransactionID="78747579" 
  TimeStamp="2021-01-10T23:08:42.4+01:00"/>
  <SaleReferenceID>59786354</SaleReferenceID>
 </SaleData>
 <PaymentTransaction>
  <AmountsReq Currency="EUR" RequestedAmount="500.00"/>
</PaymentTransaction>
<PaymentData PaymentType="FirstReservation"/>
</PaymentRequest>
</SaleToPOIRequest>

<?xml version="1.0" encoding="UTF-8"?>
<Document>
  <AccptrAuthstnReq>
    ***********************************************
    *               Header Section                *
    ***********************************************
    <AuthstnReq>
    ***********************************************
    *               Environment Section           *
    ***********************************************
    <Cntxt>
        <PmtCntxt>
          *****************************************
          *        Payment Context                *
          *****************************************
        </PmtCntxt>
        <SaleCntxt>
           <SaleId>SaleTermA</SaleId>
           <SaleRefNb>78747579</SaleRefNb>
        </SaleCntxt>
      </Cntxt>
      <Tx>
        <TxCaptr>false</TxCaptr>
        <TxTp>RESA</TxTp>
        ...
        <SaleRefId>59786354</SaleRefId>
        <TxId>
          <TxDtTm>2021-01-10T23:08:42.000+02:00</TxDtTm>
          <TxRef>00000016</TxRef>
        </TxId>
       ...
        <TxDtls>
          <Ccy>EUR</Ccy>
          <TtlAmt>500.00</TtlAmt>
          <AmtQlfr>ESTM</AmtQlfr>
          ...
        </TxDtls>
      </Tx>
    </AuthstnReq>
  </AccptrAuthstnReq>
</Document>

nexo Retailers V3 Sale to POI messages

(PAS SUPPORTÉ) RequestedValidityDate: the estimated time period of the purchase to reserve,

<?xml version="1.0" encoding="UTF-8"?>
<SaleToPOIRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="EpasSaleToPOIMessages.xsd">
<MessageHeader MessageClass="Service" MessageCategory="Payment" MessageType="Request" ServiceID="642" SaleID="SaleTermA" POIID="POITerm1"/>
<PaymentRequest>
 <SaleData>
  <SaleTransactionID TransactionID="579" TimeStamp="2021-01-10T23:08:42.4+01:00"/>
  <SaleReferenceID>12345678</SaleReferenceID>
 </SaleData>
 <PaymentTransaction>
  <AmountsReq Currency="EUR" RequestedAmount="104.11"/>
</PaymentTransaction>
<PaymentData PaymentType="FirstReservation"/>
</PaymentRequest>
</SaleToPOIRequest>

MerchantApp Considerations

Messages Flow