Testing for Busy or Offline Smart Terminal

PayJunction introduced a feature that prevents incorrect charges on in-progress transactions. Based on customer feedback, we are making this the default behavior moving forward to ensure the integrity of transactions.

Terminals will no longer be interrupted as of June 5, 2018.

Migration Path

We have introduced the following parameter for you to transition your application.

Name Format Description
interruptBusyTerminal true | false

Tells the API whether or not to interrupt an in-progress transaction on the requested Smart Terminal

Prior to June 5, 2018: Default value is true.

After June 5, 2018: All requests will be treated as false and the parameter will be removed.

Setting the parameter to false will prevent the interruption of existing transactions.

FAQs Regarding the Migration Path

How do I know if a Smart Terminal is busy?

Webhook Integrations: 

We introduced a new webhook that provides detailed status updates for transaction requests. Please see the API documentation for the SMARTTERMINAL_REQUEST webhook subscription.

Polling Integrations:

We introduced a busy status for polling requests. For details on the request and response formats when using the Polling API, please see the GET /smartterminals/requests/{requestPaymentId} API documentation.

What should I do if a Smart Terminal is busy?

  1. Wait until the current request is complete.
  2. Make sure the request is sent to the correct Smart Terminal.

Who should I contact if I still have questions?

Please email us at or call us at 800-601-0230 x 3, Monday through Friday, 6 a.m. to 5 p.m. PT.