The YCS Fiscal allows you to process IVU Loto transactions with ease and simpliity, just with a few lines of code. Here's a quick documentation of how to utilize the YCS Fiscal library.
\nStep #1: Download the .DLL
\nDownload the library here
Step #2: Include the library in your project
\nOnce you've downloaded the .dll, you'll need to include it on your project.
Step #3: How to get the control get the control code with 3 examples
using YCS_Fiscal; // Add Namespace\n\n// Variables and Objects //\nYCSFiscal fiscal; // YCS Fiscal DLL Object\nstring posID = \"0\"; // POS ID Assigned by YCS\n\npublic class YourClass\n{\n public YourClass()\n {\n // Instantiate the YCS Fiscal object with your assigned POS ID //\n fiscal = new YCSFiscal(posID);\n }\n\n private void ExampleMethod1()\n {\n // Generate a new fiscal print //\n fiscal.generateNewFiscalPrint();\n \n // Store the generated Fiscal Print //\n string fiscalLine1 = \"CONTROL: \" + fiscal.FiscalPrintLine1;\n string fiscalLine2 = fiscal.FiscalPrintLine2;\n string fiscalLine3 = fiscal.FiscalPrintLine3;\n \n // Print fiscalLine1, 2 and 3 on your receipt //\n printReceipt(fiscalLine1, fiscalLine2, fiscalLine3);\n \n // Store Submit Token with the control code //\n storeTransDetails(fiscal.fiscalToken, fiscalLine1);\n }\n \n private void ExampleMethod2()\n {\n // Generate a new fiscal print //\n fiscal.generateNewFiscalPrint();\n \n // Store the generated Fiscal Print //\n string fiscalFooter = $\"CONTROL: {FiscalPrintLine1}\\n{FiscalPrintLine2}\\n{FiscalPrintLine3}\\n\";\n \n // Print fiscalFooter on your receipt //\n printReceipt(fiscalFooter);\n \n // Store Submit Token with the control code //\n storeTransDetails(fiscal.fiscalToken, fiscalLine1);\n }\n \n private void ExampleMethod3()\n {\n // Generate a new fiscal print //\n fiscal.generateNewFiscalPrint();\n \n // Store the generated Fiscal Print //\n string fiscalFooter = string.Format(\"CONTROL: {0}{3}{1}{3}{2}{3}\", FiscalPrintLine1, FiscalPrintLine2, FiscalPrintLine3, Environment.NewLine);\n \n // or\n //string fiscalFooter = string.Format(\"CONTROL: {0}\\n{1}\\n{2}\\n\", FiscalPrintLine1, FiscalPrintLine2, FiscalPrintLine3);\n \n // Print fiscalFooter on your receipt //\n printReceipt(fiscalFooter);\n \n // Store Submit Token with the control code //\n storeTransDetails(fiscal.fiscalToken, fiscalLine1);\n }\n}\n\nStep #4: Transaction Signature and details
\nNow that you've generated and printed the control code, you must save the control code FiscalPrintLine1 and the transaction signature fiscalToken for when you report it via our web api. Read the API POST call, to understand how to send us your sale report.
Recomendations
\nExamples of allowed control code alignments:
\n\n|‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾|\n| RECEIPT HEADER TEXT |\n| DATE/TIME |\n| STORE INFO |\n| |\n| ------------------------- |\n| |\n| Item $1.00 |\n| Item $1.00 |\n| Item $1.00 |\n| |\n| Subtotal: $3.00 |\n| |\n| ------------------------- |\n| Store Promotion Text |\n| |\n| CONTROL: XXXXX-XXXXX |\n| YC |\n| Processed by YCS PR Corp. |\n| |\n|_______________________________|\n\n|‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾|\n| RECEIPT HEADER TEXT |\n| DATE/TIME |\n| STORE INFO |\n| |\n| ------------------------- |\n| |\n| Item $1.00 |\n| Item $1.00 |\n| Item $1.00 |\n| |\n| Subtotal: $3.00 |\n| |\n| ------------------------- |\n| Store Promotion Text |\n| |\n| CONTROL: XXXXX-XXXXX |\n| YC |\n| Processed by YCS PR Corp. |\n| |\n|_______________________________|\n\nExamples of unallowed control code alignments:
\n\n|‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾|\n| RECEIPT HEADER TEXT |\n| DATE/TIME |\n| STORE INFO |\n| |\n| ------------------------- |\n| |\n| Item $1.00 |\n| Item $1.00 |\n| Item $1.00 |\n| |\n| Subtotal: $3.00 |\n| |\n| ------------------------- |\n| Store Promotion Text |\n| |\n| CONTROL: XXXXX-XXXXX |\n| YC |\n| Processed by YCS PR Corp. |\n| |\n|_______________________________|\n\n|‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾|\n| RECEIPT HEADER TEXT |\n| DATE/TIME |\n| STORE INFO |\n| |\n| ------------------------- |\n| |\n| Item $1.00 |\n| Item $1.00 |\n| Item $1.00 |\n| |\n| Subtotal: $3.00 |\n| |\n| ------------------------- |\n| Store Promotion Text |\n| |\n| CONTROL: XXXXX-XXXXX |\n| YC |\n| Processed by YCS PR Corp. |\n| |\n|_______________________________|\n\nYCS Fiscal Offline is an API oriented for the implementation of Hacienda of Puerto Rico regulations. YCS Fiscal Offline API let you submit sales through an HTTPS request and retrieve a unique Fiscal number to be printer in the POS receipts.
\nSubmited sales are posted every day to \"Hacienda Dept\" automatically by YCS. The developers have the responsability to print the \"Fiscal Code\" to inform the customer receiving the receipt, it is a legal sale receipt and then report the transaction to \"Hacienda Dept\" via our API.
\nAllowed HTTPs requests:
\n\n\nPOST : To upload sale information
\n
Description Of Usual Server Responses:
\n\n\n200 OK - the request was successful (some API calls may return 201 instead).
\n
\n201 Created - the request was successful and a resource was created.
\n204 No Content - the request was successful but there is no representation to return (i.e. the response is empty).
\n400 Bad Request - the request could not be understood or was missing required parameters.
\n401 Unauthorized - authentication failed or user doesn't have permissions for requested operation.
\n403 Forbidden - access denied.
\n404 Not Found - resource was not found.405 Method Not Allowed - requested method is not supported for resource.
IVUSale class
\n\nUsed on:
\n\n
Response class
\n\nUsed on:
\n\n
PRINTING specifications
Hacienda of Puerto Rico mandates that the fiscal control number must be inserted on the bottom portion of every receipt. Make note that it should only be printed on sales receipt that paid taxes and it should not be printed on reprints of the original copy and/or refunds or voids.
\nYou must insert the following lines at the end of the receipt.
\nCONTROL: XXXXX-XXXXX \nYC\nProcessed by YCS PR Corp.\n*** Important notes:
\n\n\nControl code can only be printed on sales receipts that paid taxes.\nReprints cannot print the Fiscal code.\nThe control code must always be printed on the bottom portion of the receipts.\nYou must always print the control code utilizing the format provided by Hacienda.\nDO NOT repeat the fiscal control number on two separate receipts. The code can only be printer ONCE.
\n
Going LIVE
Once testing is complete, copies of the receipts should be send to YCS for approval. \nYCS will provide a production URL to complete the integration.
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[{"content":"DLL Library Documentation","slug":"dll-library-documentation"},{"content":"Web API Documentation","slug":"web-api-documentation"},{"content":"Classes Definitions","slug":"classes-definitions"},{"content":"IMPORTANT","slug":"important"}],"owner":"6395545","collectionId":"79d1b9ed-c769-4e9c-ba9e-b25741a97dc7","publishedId":"S1ENwxh7","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"EF5B25"},"publishDate":"2019-06-28T13:27:03.000Z"},"item":[{"name":"Submit Transaction","id":"e90d58a8-cda0-441f-b07b-01b19680626c","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","name":"Content-Type","type":"text","value":"application/json"}],"body":{"mode":"raw","raw":"{\r\n \"posID\": 33,\r\n \"ycsToken\": \"tcatest\",\r\n \"time\": \"12:01:00\",\r\n \"amount\": 1,\r\n \"munTax\": 0,\r\n \"stTax\": 0,\r\n \"control\": \"XXXXX-XXXXX\",\r\n \"tender\": \"CASH\",\r\n \"dob\": \"01-01-2019\",\r\n \"transType\": \"DB\",\r\n \"fiscalToken\": \"aAA4ADYAYwBUAFUASQBzAGEAbwBYAFYAOQBiADgATwBtAEcATQBaAGIAZwA9AD0A\"\r\n}"},"url":"http://service.ycsapi.net/api/IVU","description":"Submit Transaction allows you to upload the reported sales via the Fiscal TransUploader API. You're able to upload the following type of transactions:
\nPOST JSON Parameters (See IVUSale class in the documnetation)
OUTPUT Parameters (See Response class in the documentation)
JSON Response Example
\n{\n \"Result\": 0,\n \"Message\": \"OK\"\n}\nError Messages Index Table
\nYou can see more examples on the api documentation.
\n