Amadis

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

In this section:

Definition

A Reservation service is 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.

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

  • Optionally, one or several update reservations when the condition of the reservation is changing,

  • A completion after the consumption or delivery to complete the payment transaction with the actual amount.

Reference Documents

  • nexo Card Payment Message Usage Guide

  • nexo-FAST Specifications

  • nexo Retailer Specifications

Processing

Initial Reservation

The corresponding nexo-Fast service is “PRE-AUTH”.

The Acceptor shall initiate an initial reservation including:

  • SaleReferenceID, the sale identifier for the whole reservation transaction,

The Acceptor may include (optionally):

  • RequestedAmount: this is the estimated amount of the purchase to reserve,

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

//

Connected POI

If the reservation originates from a Sale System, the Acceptor shall also include:

  • SaleTransactionID

The Acceptor requests an authorization the Acquirer by sending an AcceptorAuthorisationRequest. The Acquirer may indicate a specific reference to the reservation in the RecepientTransactionID field in the response.

Update Reservation

The corresponding nexo-Fast service is “UPDATE PRE-AUTH”.

The Acceptor shall initiate an update reservation including:

  • SaleReferenceID, the sale identifier for the whole reservation transaction, used for the initial reservation,

  • RequestedAmount: the new estimated amount of the purchase,

The Acceptor may include (optionally):

  • RequestedValidityDate: the new estimated time period of the purchase,

Connected POI

If the reservation originates from a Sale System, the Acceptor shall also include:

  • SaleTransactionID

The Acceptor requests an authorization the Acquirer by sending an AcceptorAuthorisationRequest. The Acquirer may indicate a specific reference to the reservation in the RecepientTransactionID field (it should be same value used for the initial reservation).

Toujours online

Update Reservation avec recherche

Completion

The corresponding nexo-Fast service is “PAYMENT COMPLETION”.

The Acceptor shall initiate an update reservation including:

  • SaleReferenceID, the sale identifier for the whole reservation transaction, used for the initial reservation,

  • RequestedAmount: the actual amount of the purchase,

Connected POI

If the reservation originates from a Sale System, the Acceptor shall also include:

  • SaleTransactionID

The Acceptor may an authorization the Acquirer by sending an AcceptorAuthorisationRequest.

An CompletionAdvice is sent to the Acquirer to indicate the completion of the reservation.

Completion Reservation avec recherche

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)

RECOMMENDATION:

  • The transaction amount shall be set before processing of the Reservation Service is entered.

Message Examples

nexo Retailers V3 Sale to POI messages

 Initial Reservation (PaymentRequest)
<?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

  • No labels