Email to Ivan Pavlovic 16/10/2017

Bula Sanjay,

The device has been shipped to you on 18/10/2017. DHL Track 3099647865.Please find attached documents for device configuration.

The device PIN is 0410.

Regards
Sanjeet

Email from Ivan Pavlovic

Hi Sanjay,

Yes it is, root URL is https://vsdc.staging.vms.frcs.org.fj/ . If you want to access online documentation and auto generate client library go to https://vsdc.staging.vms.frcs.org.fj/swagger and use some of the tools available on https://swagger.io/open-source-integrations/

Both URLs requires client authentication using digital certificate so make sure to have smart card with you.

Optionally, you can install VMSRCAStaging.cer to Trusted Root and VMSICA1Staging.cer to the Intermediate CA store on your machine to make those authorities trusted and avoid warnings in browser. Certificates are in attached zip file.

Regards,

Ivan

Email from ivan.pavlovic@dti.rs

Dear Sanjay,

Here is the answer to your questions

• I am not sure what do you refer to rearding Web Based API. All APIs (exposed by web service V-SDC and those exposed by E-SDC device)are documented in the Technical Guidelines for POS developers published on http://www.frcs.org.fj/vat-monitoring-system-vms/ You can find message formats, endpoint addresses and explanations for each command described in the document
• Yes, you can use Postman. We are also using Postman to test E-SDC internally
• If you want to connect to V-SDC you do not need any hardware but permanent internet connection is required.
• If you want to connect POS to E-SDC at this moment you have to use Raspberry Pi device (with smart card and smart card reader) received from FRCS. Later on, FRCS will provide web service to POS vendors that simulates E-SDC devices at which point Raspberry Pi devices will be deprecated. Due the ongoing work with FRCS

You can find latest Technical Instructions on http://www.frcs.org.fj/vat-monitoring-system-vms/

Peni, please make sure latest DTI E-SDC user Manuel is delivered to Link Technologies

Regards,

Ivan

Meeting with Milo, Sanjeet and Sanjay at 8AM AEST.

Meeting Notes

VSDC Operations

1. Smartcard  is required to be able to access API
2. We tested the Smartcard and was able to successfully call the API
3. VSDC API URL: https://vsdc.staging.vms.frcs.org.fj/swagger
4. Smartcard PIN 0410
5. Sample JSON on API is incorrect. Use this one:{"DateAndTimeOfIssue": "2017-08-25T13:28:02.433Z","Cashier": "null","BD": "1234","BuyerCostCenterId": null,"IT": 0,"TT": 0,"PaymentType": 0,"InvoiceNumber": "27082017-2","ReferentDocumentNumber": "T56U11W6-12345678-12","Options": {"OmitTextualRepresentation": "0","OmitQRCodeGen": "1"},"Items": [{"GTIN": null,"Name": "Hleb","Quantity": 1,"Discount": 2,"Labels": ["A"],"TotalAmount": 5}]}
6. Invalid pin (3 times) will make the card unusable
7. Sanjeet to organize the PFX certificate and test this on his machine before passing it on to development

ESDC Operations

1. ESDC needs firmware update before it can be used. Sanjeet to provide details
2. Configure ESDC using instructions provided
3. Access ESDC vis HTTP://IPAddress/API/Method

Link Development will build SDC integration in version 8.2 expected to release in DEC 2017.

Bula Sanjay,

I have received new smart card and have tested. PFX Certificates received successfully. New Smart card will be shipped to you today via DHL.

Regards
Sanjeet

Completed the following development:

1. Created Web Service Access methods
2. Added call to sign Invoice
3. Added code to sign returns
4. Added Failover support
5. Added ability cache PIN for smartcard
6. Added two configuration options, FRCATAXIntegration.Enable and FRCATaxIntegration.SmartcardPIN

Next Step:

1. QR code
2. UAT with Sanjeet
3. Documentation

Development work for VSDC integration has been completed.

Notes:

1. Settings for VSDC are shown in Figure 1 below. 
2. The serial number of the certificate is located in the "Personal Certificate Store" as shown in figure 2. The certificate should not contain any spaces before, after or in-between the number.
3. Certificates are machine specific
4. IF VSDC is enabled and ESDC is enabled, VSDC will take preference

This update will be available on 8.2 for testing.

Figure 1 - Station configuration for VSDC

Figure 2 - Serial Number for Certificate

After UAT round 1 we found that the Tax Labels were being passed to the SDC incorrectly. To resolve the issue, we need to configure the LinkSOFT Tax codes as shown in figure 1 below. 

When the Tax integration is active, the Linksoft TAX Code (TAXIN) is transformed to FRCS Tax Codes (A,E and F) as shown in the Detail line of the Tax setup.

Note: If Invalid tax codes are entered, the tax integration will fail with a "BAD REQUEST" message from the Tax Integration system.

The update will be available in BETA2

Figure 1 - LinkSOFT Tax Code Setup

Documentation updated on the case.

Documentation updated under POS -- Technical Reference -- VMS - V-SDC