API Version 2018-06-19 By default, if a Smart Terminal Payment Request is sent while the Smart Terminal is currently processing a separate transaction, PayJunction will respond with a BUSY status.
NOTE: Use the SMARTTERMINAL_REQUEST webhook in order to receive the BUSY status. *Click here to read more about API Versions.
API Versions Prior to 2018-06-19 Setting the parameter to false will prevent the interruption of existing transactions.
How do I ensure that in-progress Smart Terminal transactions are not interrupted by new Payment Requests?
Setting the interruptBusyTerminal parameter to false will prevent the interruption of existing transactions.
| Name | Format | Description |
|---|---|---|
| interruptBusyTerminal | true | false |
Tells the API whether or not to interrupt an in-progress transaction on the requested Smart Terminal |
How do I know if a Smart Terminal is busy?
Webhook Integrations:
- Please see the API documentation for the SMARTTERMINAL_REQUEST webhook subscription.
Polling Integrations:
- 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?
- Wait until the current request is complete.
- Make sure the request is sent to the correct Smart Terminal.
How do I force a Smart Terminal out of a Busy state?
- Use the /smartterminals/{smartTerminalId}/main endpoint to force a Smart Terminal back to a ready state.
- As this will force any in-progress request to terminate, it is the responsibility of the integration platform to handle any interruption in state and workflow of the application when /smartterminals/{smartTerminalId}/main is used.
Who should I contact if I still have questions?
Please email us at support@payjunction.com or call us at 800-601-0230 x 3, Monday through Friday, 6 a.m. to 5 p.m. PT.