Follow

SMARTTERMINAL_REQUEST and SMARTTERMINAL_TRANSACTION Webhook Differences

There are two similar webhook event types which can be subscribed to in order to receive updates when transactions are processed on the Smart Terminal:

  • SMARTTERMINAL_TRANSACTION
  • SMARTTERMINAL_REQUEST

While either (or both) can be subscribed to, they serve two distinct purposes.

SMARTTERMINAL_TRANSACTION

This event type is only sent once during a Smart Terminal transaction, after authorization of the payment has been completed. This is best used for transaction logging applications. An example of this would be an application that passively records transactions and saves the data into a database or external service, such as Quickbooks or Salesforce.

The SMARTTERMINAL_TRANSACTION event type is only sent when transactions are approved. This event type will not be transmitted if the transaction is declined.

SMARTTERMINAL_REQUESTS

For examples of the data sent to the subscriber for the SMARTTERMINAL_REQUESTS event type, please see the SMARTTERMINAL_REQUEST Webhook API document

This event type has been designed for integrators who wish to provide a better experience in their UI when processing cards. Instead of only sending a single notification when a transaction has been approved on the Smart Terminal, this event type sends notifications to indicate the Smart Terminal is still being connected to (CONNECTING), already in use and thus unavailable (BUSY), transaction in progress (IN_PROGRESS), and finally when the transaction has been completed (COMPLETE).

IMPORTANT NOTE:
This Webhook is part of changes supporting the migration to busy state.