Transaction status

Suggest Edits

DigiTax Queueing system

DigiTax provides the following:

  • Asynchronous functionality that automatically retries eTIMS
  • Get notifications on transaction statuses via Callback URLs
  • Throttling traffic between the businesses throughput and eTIMS

These functionality is possible due to the DigiTax Queueing system.

📘

You don't run the risk of double-entry

Every transaction that interacts with eTIMS is first off entered into the DigiTax Queueing system to mitigate against possible eTIMS intermittency and downtime or slow response rate.

The different transaction statuses and what they mean

Since transactions are first off entered into the DigiTax Queueing system, we give you the following statuses. This is what they mean.

Transaction statuses

StatusMeaningAction
queuedDigiTax Queueing system is queued after trying to reach eTIMSCheck in later. If you set up Callback URLs, we'll post to your system when the eTIMS sync is done.
un_queuedDigiTax Queueing system is unqueued after trying to reach eTIMSCheck in later. If you set up Callback URLs , we'll post to your system when the eTIMS sync is done.
in_progressDigiTax Queueing system is in progress after trying to reach eTIMSCheck in later
completedeTIMS has received and accepted the transaction and we have the final dataFor ITEM: You can now create a sale with this item
For SALE: You have the etims_url hence can generate the QR code.
failedeTIMS rejected the transactionPlease initiate another transaction.
pausedDigiTax Queueing system is paused after trying to reach eTIMS. The queue will be unpaused in the backgroundCheck in later. If you set up Callback URLs , we'll post to your system when the eTIMS sync is done
submittedeTIMS has received and accepted the transaction however we do not have the final data from their system. Though this is unlikely, we have a work around to get the data.If you don't have an etims_url kindly initiate a chat with us when this happens.

Updated 2 months ago