The Sale Reference ID is a data that can be passed on and transfer transferred from an Nexo Payment request incoming from the Sale Terminal. In order to display such data to incoming request.
METHOD 1:
Following the recent demand, the Sale Reference ID is now accessible directly in the :
public byte[] preparedReversalData;
if reversal request contains SaleReferenceIDpublic byte[] preparedPaymentData;
if payment request contains SaleReferenceID
The Sale Reference ID is then checked in Arkoslib and sent to Amanacq if present.
So nothing is required on your side.
METHOD 2:
To display such data in the message response from Arkos, this one need needs to be added to the Aquired Acquirer Proprietary Data directory.
...
To do so, the following block of code has been implemented and added in to the Arkos Pay Application:
Code Block | ||
---|---|---|
| ||
public static PaymentParams createFromRetail(NexoRequest req) { PaymentParams params = new PaymentParams(); if (req instanceof PaymentRequest) { PaymentRequest paymentReq = (PaymentRequest) req; String saleReferenceID = paymentReq.SaleReferenceID; params.paramTree = TlvTree.FromRaw(paymentReq.preparedPaymentData); TlvTree acquirerProprietaryData = params.paramTree.AddChild(0xFFBF2FParams.ACQUIRER_PROPRIETARY_DATA); acquirerProprietaryData.SetAscii(0xDFCF01Params.SALE_REFERENCE_ID,saleReferenceID); ... } else if (req instanceof ReversalRequest) { ... } } else { ... } ... } |
The Retail Module (ASL) is accused of receiving the Payment XML file request where the Sale Reference ID is located in parses the payment request and sets paymentReq.SaleReferenceID
with the saleReferenceID
from the XML. This one is then passed in ArksoPay through saleReferenceID
for it to get set, afterwards, in the ACQUIRER_PROPRIETARY_DATA
directoryfield can be then accessed through the merchant app side and is set into acquirer proprietary data.
The previously given script will provide you with details of the implementation made for the addition of the Sale Reference ID attribute in the ACQUIRER_PROPRIETARY_DATA
directory. This one will be then be appearing appear in the Message Request Response from Nexo Retail (i.e: Accepted Authorization Request response).
...
An example of the ACQUIRER_PROPRIETARY_DATA
can be found in the folliwing snipped following snip of the directory:
Code Block |
---|
, 0xFFBF2F: [ 0xDFCF01: 41726b6f7353616c653432 , 0xFFDF02: [ 0xFF01: [ 0xC1: 4864722f496e6974675074792f4964 , 0xC2: 4d4f4e4559323032305645474124 ] ] , 0xDFBF01: 303030303030303030323336 , 0xFFBF05: [ 0xFFFF6A: [ 0xDF01: 01 , 0xDFBF03: 44656661756c74206265686176696f72 , 0xDFBF04: 4e6f2074657374206361736520747269676765726564 ] ] ] |