01 Product Overview
DynamixPOS is a web-based Point of Sale (POS) and retail management system that fiscalises sales exclusively through the Fiji Revenue & Customs Service (FRCS) VSDC (Virtual Sales Data Controller) in real time.
DynamixPOS is an online, VSDC-only solution. Every completed transaction is transmitted electronically to the FRCS VSDC over a secure mutual-TLS (mTLS) connection. The VSDC returns an official fiscal invoice number, a digital signature, a verification URL, a verification QR code, and a complete fiscal journal, all of which are stored against the transaction and printed on the customer receipt. No hardware SDC or local E-SDC is used.
Key capabilities
- Real-time fiscalisation of Sale and Refund invoices through the FRCS VSDC API.
- Compliant 80mm thermal fiscal receipts that reproduce the FRCS journal verbatim with a scannable QR code.
- VAT handling with FRCS tax labels (A = 9%, B = 0%, D = 15%, G = 12.5%).
- Full retail management: inventory, products, categories, brands, customers, suppliers, purchases, and reporting.
- Role-based access control and encrypted certificate storage.
02 System Architecture
DynamixPOS fiscalises exclusively through the FRCS VSDC (Virtual Sales Data Controller). It is an online-only solution: the application connects directly to the FRCS VSDC over the public internet via a secure mTLS API connection. DynamixPOS does not use, require, or support any hardware SDC device or local E-SDC appliance — all fiscalisation is performed by the FRCS VSDC service.
┌───────────────────────────────────────────┐
│ POS Terminal │
│ (Browser: Chrome / Edge) │
│ ┌──────────┐ ┌──────────────────┐ │
│ │ POS UI │ HTTP │ DynamixPOS App │ │
│ │ (browser)│◄─────►│ (PHP / Apache) │ │
│ └──────────┘ └────────┬─────────┘ │
│ │ MySQL │
│ ┌──────▼──────┐ │
│ │ Database │ │
│ └─────────────┘ │
└───────────────────────────────────────────┘
│
│ HTTPS + mTLS (PFX cert + PAC header)
▼
┌────────────────────────────┐
│ FRCS VSDC │
│ vsdc.vms.frcs.org.fj │
│ POST /api/v3/invoices │
└────────────────────────────┘
| Layer | Technology |
|---|---|
| Application framework | PHP (CodeIgniter MVC) |
| Database | MySQL / MariaDB |
| Front end | HTML5, CSS, JavaScript, jQuery |
| Web server | Apache / Nginx |
| FRCS transport | HTTPS REST, mutual TLS, HTTP/1.1 |
| Fiscalisation model | Online VSDC (real-time at point of sale) |
03 Fiscal Configuration
This one-time step connects DynamixPOS to the FRCS VSDC. Perform it as an Administrator.
- Open Settings → Certificate Settings.
- Enter the API URL (VSDC endpoint).
- Enter the PAC code issued by FRCS.
- Upload the PFX / P12 certificate file.
- Enter the certificate password.
- Save. The system validates that all four items are present before fiscalising.
| Setting (db_sitesettings) | Meaning |
|---|---|
pfx_url | VSDC API endpoint URL |
pfx_pac | PAC value sent as the pac request header |
pfx_certificate | Relative path to the uploaded PFX/P12 file |
pfx_password | PFX/P12 password |
04 How Fiscalisation Works
DynamixPOS is an online VSDC solution. Each transaction is fiscalised in real time at the moment it is completed:
- The operator completes a sale (or refund) in the POS.
- The transaction is saved locally with a POS invoice number.
- DynamixPOS builds the fiscal payload and sends it to the FRCS VSDC over mTLS.
- The VSDC returns the fiscal data: SDC invoice number, invoice counter, digital signature, verification URL, verification QR code, and the fiscal journal.
- The fiscal data is stored against the transaction and the receipt is printed.
05 Supported Invoice Types
DynamixPOS supports the following FRCS invoice type / transaction type combinations. Each is generated from a specific screen or action in the application.
| Invoice | InvoiceType | TransactionType | Where generated |
|---|---|---|---|
| Normal Sale | NORMAL | SALE | POS checkout |
| Normal Sale (with buyer) | NORMAL | SALE | POS checkout with a named customer |
| Normal Refund | NORMAL | REFUND | Sales Return against a normal sale |
| Normal Refund (with buyer) | NORMAL | REFUND | Sales Return (named customer) |
| Advance Sale | ADVANCE | SALE | POS → "Advance" button (credit sale) |
| Advance Refund | ADVANCE | REFUND | Sales Return against an advance sale |
| Proforma Sale | PROFORMA | SALE | Quotation → "Proforma Sale" |
| Proforma Refund | PROFORMA | REFUND | Quotation → "Proforma Refund" |
| Copy Sale | COPY | SALE | Sales list → reprint POS invoice |
| Copy Refund | COPY | REFUND | Sales Return list → "Copy Refund" |
BuyerId, satisfying the "with buyer identification" requirement. Proforma documents are, by FRCS definition, non-fiscal and the journal is marked accordingly.06 Daily Operations
Making a normal sale
- Open the POS screen.
- Add items by scanning a barcode or searching by name/SKU.
- Select the customer (or use the default walk-in).
- Click Pay / Checkout and choose the payment method(s) — Cash, Card, Cheque, or Other (split payments allowed).
- Confirm. The sale fiscalises automatically and the fiscal receipt opens for printing.
Advance (credit) sale
- Select a named customer (required — credit cannot be issued to walk-in).
- Add items.
- Click the Advance button. The sale is saved with zero payment; the amount is posted to the customer ledger as credit and fiscalised as an Advance Sale.
Proforma (quotation)
- Create a quotation.
- From the quotation list, choose Proforma Sale to fiscalise and print it as a proforma document.
07 Refunds & Returns
In this system a Sales Return (business action) produces a Refund (FRCS transaction type). A refund must always reference the original fiscalised sale.
Workflow
- Open the Sales Return screen and search for the original sale.
- Only fiscalised sales can be selected for return.
- Choose a full or partial return and adjust quantities.
- Save. The refund fiscalises automatically, referencing the original sale's SDC invoice number and date/time.
Validations
- The original sale must exist and be fiscalised.
- The original fiscal invoice number and date/time must exist.
- Returned quantity cannot exceed the quantity originally sold.
- Duplicate (already fully returned) sales are blocked.
08 Fiscal Receipt Format
The receipt prints on 80mm thermal paper and contains, in order:
- The fiscal journal exactly as returned by the VSDC (business name, TIN, location, address, cashier, items with tax labels, totals, tax breakdown, SDC time, SDC invoice number, and invoice counter).
- The scannable verification QR code, printed before the "END OF FISCAL INVOICE" line.
- The END OF FISCAL INVOICE banner.
============ FISCAL INVOICE ============
2901664754
Business Name Pte Ltd
Location Name
Address, Suva, Fiji
Cashier: Sunil
Buyer: 1
--------------NORMAL SALE---------------
Items
========================================
Name Price Qty. Total
Shampoo (A)
10.00 10 100.00
----------------------------------------
Total Purchase: 100.00
========================================
Label Name Rate Tax
A VAT 9.00% 8.26
----------------------------------------
Total Tax: 8.26
========================================
SDC Time: 29/06/2026 11:08:26 pm
SDC Invoice No: 92V24F6D-Y8WELYO0-8
Invoice Counter: 8/8NS
========================================
[ verification QR code ]
======== END OF FISCAL INVOICE =========
A customer or auditor can scan the QR code, or open the verification URL, to confirm the invoice against FRCS records.
09 Tax Labels (VAT)
The VSDC calculates VAT from the tax label on each item. DynamixPOS uses the FRCS Fiji labels:
| Label | Rate | Meaning |
|---|---|---|
A | 9% | Standard VAT |
B | 0% | Zero-rated / exempt |
D | 15% | — |
G | 12.5% | — |
The label is resolved from the item's tax name (if it is a valid label letter) or from the numeric tax rate. It prints beside each item and is summarised in the tax breakdown.
10 VSDC API Reference
Endpoint
POST https://vsdc.sandbox.vms.frcs.org.fj/api/v3/invoices
(production host issued by FRCS)
Authentication
| Mechanism | Detail |
|---|---|
| mTLS client certificate | PFX / P12 (PKCS#12) + password |
| PAC header | pac: <PAC> |
| HTTP version | HTTP/1.1 |
| TLS | Peer + host verification enabled |
Request body (Normal Sale)
{
"DateAndTimeOfIssue": null,
"Cashier": "Sunil",
"BuyerId": "1",
"BuyerCostCenterId": "1",
"InvoiceType": "NORMAL",
"TransactionType": "SALE",
"Payment": [ { "Amount": 100, "PaymentType": 1 } ],
"InvoiceNumber": "SL160",
"ReferentDocumentNumber": "",
"ReferentDocumentDT": null,
"Options": {},
"Items": [
{ "gtin": "11111111", "name": "Shampoo",
"quantity": 10, "labels": ["A"],
"unitPrice": 10, "totalAmount": 100 }
]
}
Payment type codes
| Code | Method |
|---|---|
| 1 | Cash |
| 2 | Card |
| 3 | Cheque |
| 4 | Other |
Response (HTTP 200)
{
"invoiceNumber": "92V24F6D-Y8WELYO0-8",
"invoiceCounter": "8/8NS",
"sdcDateTime": "2026-06-29T23:08:26+12:00",
"verificationUrl": "https://...",
"verificationQRCode": "R0lGODlh...",
"journal": "============ FISCAL INVOICE ...",
"signature": "...",
"signedBy": "Y8WELYO0",
"encryptedInternalData": "...",
"tin": "2901664754",
"businessName": "...",
"locationName": "...",
"address": "...",
"mrc": "99-3800-Y8WELYO0",
"taxItems": [ { "label":"A","rate":9.00,"amount":8.26,"categoryName":"VAT" } ]
}
ReferentDocumentNumber (the original SDC invoice number) and ReferentDocumentDT (original SDC date/time) are mandatory and reference the original sale — not the local invoice number.11 Data Stored per Transaction
For every sale and refund, DynamixPOS stores the fiscal data returned by the VSDC. This is the record an auditor inspects:
- Local invoice number and transaction date
- Cashier (username) and customer
- Items, quantities, prices, and tax labels
- SDC fiscal invoice number and invoice counter
- SDC date/time
- Verification URL and verification QR code
- Digital signature and encrypted internal data
- Full fiscal journal and MRC (Machine Registration Code)
- Fiscal status (success / failure)
- For refunds: the original sale's SDC invoice number and date/time
This data is retained and cannot be edited by cashiers; it forms the audit trail.
12 Audit — Local & Remote
Local audit (on-site)
- Log in with reporting/return access (Supervisor or Administrator).
- Open the Sales or Sales Return list — each row shows the invoice number, date, cashier, amount, and fiscal status.
- Open any transaction's fiscal print/preview to inspect the stored journal, SDC invoice number, counter, date/time, QR, and verification URL exactly as issued by the VSDC.
- Scan the QR or open the verification URL to confirm authenticity against FRCS on the spot.
Remote audit (FRCS server-side)
Because DynamixPOS is an online VSDC, every fiscalised transaction reaches FRCS in real time at point of sale. No manual export is required for routine remote audit.
- The verification URL / QR confirms a specific invoice against the FRCS record remotely.
- The SDC invoice number, invoice counter, and signature are the reference keys FRCS uses to locate the transaction server-side.
- Any transaction that did not reach FRCS shows a failed fiscal status locally and must be re-fiscalised.
13 Security
| Area | Control |
|---|---|
| Authentication | Per-user username/password login |
| Authorisation | Role-based permissions per feature/action |
| FRCS transport | Mutual TLS with client certificate; TLS verification enabled |
| Certificate storage | PFX kept in a non-public directory; direct access blocked |
| Input handling | Input sanitisation / XSS filtering on request data |
| Database safety | Framework query builder / parameterised queries |
| Audit integrity | Fiscal fields written from the VSDC response; not editable by operators |
14 Roles & Access
| Role | Can do |
|---|---|
| Cashier | Log in, create sales, take payments, print receipts |
| Supervisor | All cashier actions + process refunds/returns, reprint invoices |
| Administrator | All of the above + settings, certificate/PAC configuration, user management |
Each cashier must use a unique login — the cashier username is printed on every fiscal invoice and is used for accountability during an audit.
15 Troubleshooting
| Symptom | Cause | Resolution |
|---|---|---|
| No fiscal invoice number / no QR on receipt | VSDC did not fiscalise | Check internet; confirm certificate/PAC in settings; retry |
| "VMS: PFX certificate not uploaded" | Fiscal settings incomplete | Complete Certificate Settings |
| "Original sale is not fiscalised" on return | Refunding a non-fiscalised sale | Only fiscalised sales can be refunded |
| "Returned quantity exceeds sold quantity" | Return quantity too high | Reduce return quantity |
| HTTP 401 / 403 from VSDC | PAC invalid or certificate not authorised | Verify PAC; re-issue certificate with FRCS |
| SSL / certificate errors | CA bundle or OpenSSL issue | Update curl.cainfo; ensure OpenSSL 1.1+ |
16 Glossary
| Term | Meaning |
|---|---|
| FRCS | Fiji Revenue & Customs Service |
| VMS | Verification Management System |
| VSDC | Virtual Sales Data Controller — the FRCS online fiscalisation service used exclusively by DynamixPOS |
| E-SDC | Electronic Sales Data Controller (hardware/local appliance model) — not used by DynamixPOS |
| PAC | Point of Access Code (API header credential) |
| PFX / P12 | PKCS#12 client certificate used for mTLS |
| SDC Invoice Number | Unique fiscal invoice number issued by the VSDC |
| Invoice Counter | Sequential counter issued by the VSDC (e.g. 8/8NS) |
| MRC | Machine Registration Code |
| Journal | Complete plain-text fiscal receipt returned by the VSDC |
| Refund | FRCS transaction type produced by a Sales Return |
| Proforma | Non-fiscal preliminary document (quotation) |