Blockchyp Terminal Errors Troubleshoot Guide

Blockchyp Terminal Errors Troubleshoot Guide

1. Error: Unknown Terminal

The “Unknown Terminal” error appears when attempting to process a payment at checkout and RepairDesk POS is unable to recognize the assigned BlockChyp terminal.

This issue is usually configuration-related and may occur due to:

  • Previously enabled Multi-Terminal Support that is no longer required
  • Mismatch between cash registers and assigned terminals
  • Employee logged into an incorrect register or an inactive shift
  • Terminal name inconsistency across registers

Resolution Steps

1

Verify Multi-Terminal Support Configuration

If you previously used multiple terminals but are now operating with a single terminal:

  • Navigate to:
    Integration > Payments > RD Payments > Advanced Configuration
  • Review the Multi-Terminal Support setting
  • Ensure that:
  • All cash registers are mapped to the same terminal name
  • The terminal name is consistent across all registers

In multi-register environments with only one physical terminal, all registers must reference the same terminal to avoid payment failures.

2

Verify Cash Register & Employee Shift

  • Confirm which employee profile is currently logged in
  • Verify that the employee has started a register shift
  • Ensure the employee is logged into the correct cash register
  • If required, end the current shift and restart it under the correct register

Incorrect register or shift assignment can prevent RepairDesk from sending the payment request to the terminal, resulting in an “Unknown Terminal” error.

2. Terminal Error: Unable to connect with device, please check device network status

This error typically occurs during repair ticket creation or invoice checkout when signature collection is enabled in RD Pay advanced settings, but the terminal is offline or disconnected from the BlockChyp portal.

Terminal error screenshot

RepairDesk attempts to communicate with the terminal to capture a signature. If the terminal is unreachable, the process fails and blocks the workflow.

Resolution Options

1

Restore Terminal Connectivity

  • Perform standard No Route to Terminal troubleshooting:
  • Confirm the terminal is online in the BlockChyp portal
  • Restart the terminal
  • Verify network connectivity (Ethernet)
  • Once the terminal is online, proceed with ticket creation or checkout and collect signatures normally
2

Disable Signature Collection

If the transaction does not require a signature or the terminal cannot be brought online immediately:

  • Navigate to:
    Integration > Payments > RD Payments > Advanced Configuration
  • Disable signature requirements for:
  • Device Check-in / Check-out
  • Accessories Sale
  • Trade-in

Disabling these options allows ticket creation or checkout to proceed without requiring terminal communication.

3. Terminal Issue: Payment request not sent to terminal

The POS displays a “Processing Payment” screen, but no payment prompt appears on the terminal.

1

Confirm Terminal Online Status

  • Log into the BlockChyp dashboard
  • Verify that the terminal status is Online
  • If offline, restore connectivity before proceeding
2

Clear POS Console Errors

  • Navigate to Checkout > RD Payment
  • Right-click anywhere on the screen
  • Open Console from inspect tool
Console screenshot
  • In the Console window:
  • Clear existing error messages using the circle icon within the bar
  • Check the Network tab for failed or blocked requests and clear them as well.
Network tab screenshot
  • Retry the payment after clearing errors
3

Restart the Terminal

  • Press the reset button located at the back of the terminal
  • Allow the terminal to fully reboot
  • Retry the payment from RepairDesk

4. Terminal Error: Cloud Relay Terminal Reset

Cloud Relay Terminal Reset screenshot

This error typically appears when the checkout process is not completed successfully. RepairDesk received a Cloud Relay Terminal Reset error, which typically indicates an issue with the terminal’s internet connection or a problem on BlockChyp’s end. When this error occurs, RepairDesk attempts to recover the transaction; however, BlockChyp continues to return the same error.

In most cases, the transaction is approved on BlockChyp but not on the RepairDesk side. And if that’s the case, we can record the payment offline in RD using offline payment methods.

5. Deposit Amount Refund Issue

In some cases, a customer may decide not to proceed with a repair after paying a deposit. When this happens, the main repair invoice remains unpaid, and the refund option is not available on the deposit invoice. This prevents the deposit from being refunded directly and may cause confusion during the refund process.

Resolution Options

1

Refund Through RepairDesk (Recommended)

  1. Mark the main repair invoice as Paid.
  2. Open the invoice and initiate a refund.
  3. The deposit will appear as a line item on the invoice.
  4. Refund the deposit amount as a partial refund, similar to standard refund handling.
2

Refund Through BlockChyp Portal

  1. Log in to the BlockChyp Portal.
  2. Locate the original deposit transaction.
  3. Process the refund directly from BlockChyp.
  4. Record the refund offline in RepairDesk for reconciliation purposes.
  5. Share the refund transaction ID with the customer so they can track the refund with their bank if required.

6. Batch Deposit Not Received

A batch deposit for a specific date (for example, the previous day) has not been received in your bank account.

Initial Verification

To investigate this issue, the batch status must be verified from the BlockChyp Portal.

Steps to Review Batch Details

  1. Log in to the BlockChyp Portal
  2. Search and open your account
  3. Navigate to Batch History
  4. Locate the batch for the reported date
  5. Review the Deposit column and batch status

How to Interpret the Batch Status

  • Deposit Amount Displayed
  • If an amount appears under the Deposit column within Batch History, the batch has been successfully submitted for settlement by BlockChyp.
  • In this case, the delay is typically related to the bank processing time (Federal Bank holiday, etc).
  • Unconfirmed / No Deposit Amount
  • If the batch shows an Unconfirmed status or no amount under the Deposit column, the batch has not yet been deposited.
  • This may indicate that the batch is still open or pending confirmation.
Batch history screenshot

Next Steps

  • If the batch is deposited:
  • The delay might be due to any bank or local holiday. If there is no holiday, wait till the end of the day and the deposit should be there.
  • If the batch is unconfirmed or missing:
  • If the batch status is unconfirmed for a day or two, we can raise the case with the BlockChyp team to check for any deposit related issues.

7. Settlement Hold – Amount Not Received / Partial Batch Received

In some cases, you may receive only a partial batch deposit, or that a portion of the expected settlement amount is missing from their bank account. This typically occurs when a settlement hold has been placed on one or more transactions within the batch.

A settlement hold is usually triggered when you process a single transaction that exceeds the approved High Ticket Amount provided during the account onboarding and application process. When this happens, the transaction is temporarily withheld for risk review, while the remaining eligible transactions in the batch are settled as usual—resulting in a partial deposit.

How to Check for a Settlement Hold

  1. Log in to the BlockChyp Portal
  2. Navigate to: Merchant Tools > Settlement Hold
  3. Review the list of held transactions
  4. Verify:
  • Transaction amount
  • Hold status
  • Date and reason for the hold

What Happens Next

  • When a settlement hold is placed, the BlockChyp Risk Team typically sends an email directly to you.
  • The email requests supporting documentation to verify the legitimacy of the transaction (for example, invoice, customer authorization, proof of service).
  • Once the required documents are submitted and reviewed:
  • The hold is released
  • The withheld amount is submitted for settlement
  • Funds are deposited into the your bank account in a subsequent batch

FAQ

How do I rectify No Route to Terminal Error?
Terminal Errors Troubleshoot

1. Error: No Route to Terminal



If you’re encountering the ‘No Route to Terminal” error, follow these troubleshooting steps to resolve the issue.


  1. Check Terminal Status: Login to your BlockChyp account and verify whether the terminal is online or offline.

    1. If Offline: This indicates an issue with the internet connection. Establish a stable internet connection.

    2. If Online:



  2. Restart the Terminal: Unplug the terminal for 5 to 10 seconds, then plug it back in and check if the issue persists.

  3. Reset the Terminal: Turn the terminal upside down and press the reset button. Once reset, log back into your dashboard and verify if the terminal is online.

  4. Restart the Router: Restart your router and check if it resolves the problem. You can also try switching to a different Ethernet port to ensure there is no connection issue.

  5. Check the Terminal’s Internet Connection: To verify the terminal is receiving an IP address:

    1. Hold the magnifying glass button on the terminal keypad for 3 seconds until it beeps, then press it twice quickly.

    2. Navigate to Setup > System Config > Network > Next > Wired > Next >Ethernet> DHCP.

    3. The terminal will display either an IP address or show "Failed to enable DHCP, disconnected." If disconnected, try switching Ethernet ports to see if the connection improves.

By following these steps, you should be able to resolve the "No Route to Terminal" error. If the issue persists, please contact RepairDesk Support for further assistance.


How do I rectify Terminal not found Error?

Ensure that the terminal name in your BlockChyp account exactly matches the terminal name configured in RepairDesk. If there is any discrepancy between the two, the system will display the "Terminal Not Found" error.

To resolve this, verify and update the terminal names so they are identical in both systems.

If the issue persists, please contact RepairDesk Support for further assistance.

3. Error: SERV not allowed

This error occurs when the customer’s bank has a limitation that prevents refunds from being processed.

The customer should contact their bank to request the removal of the restriction. Once lifted, the refund will be processed, and the customer will typically receive it within 3 to 5 working days, depending on their bank's processing time.

If the issue persists, please contact RepairDesk Support for further assistance.


How do I rectify iFrame Error?
If you are unable to process a transaction using the Virtual Terminal option in RepairDesk, follow these troubleshooting steps:

  1. Try Using Incognito Mode: Open an incognito window, log in to your account, and attempt to process the transaction using the Virtual Terminal.

  2. Reconfigure the Virtual Terminal: If the issue persists, reconfigure the Virtual Terminal by following these steps:

    1. Log in to your BlockChyp account.

    2. From the Dashboard, select "API Credentials" and then click on "Tokenization Keys."

    3. Generate a new API key and copy it.

    4. In your RepairDesk account, click on the nine dots at the top right of the screen and select the "Integrations" tab.

    5. Find the "RepairDesk Payments" tab and click "Connected" beneath it.

    6. Select the "Advanced Configuration" tab.

    7. Scroll down to the field beneath "Enable Virtual Terminal", paste the copied key, and save the changes.

    8. Try to process the transaction again.



  3. If the Problem Continues: Your IP address might be blocked. If so, please contact RepairDesk Support for further assistance. In the meantime, you can use the Email Invoice option to charge the customer.



How do I rectify Service Alert / Service Required Error?
If you encounter this error message, it means the terminal is worn out and needs to be replaced.
  • Within One Year of Purchase: Contact RepairDesk Support for assistance with replacing the terminal.

  • After One Year: You may be eligible for a promo code to receive a discounted terminal price. Contact RepairDesk Support to check eligibility.
How to record a transaction if payment has gone on BlockChyp and not on RepairDesk?
While the customer's card information is sent to the BlockChyp server, there are occasional instances where the captured payment information does not return to RepairDesk POS. In this case the transaction the invoice is still marked as ‘Unpaid’ in RepairDesk.
For resolution, you should wait for 6-12 hours for the transaction to be recorded. Our automated system identifies the payments and attempts to associate it with the corresponding invoice. You can identify these transactions by checking the payment notes on the invoice, which will indicate that the payment was automatically logged by the system.


What happens if the payment is still not recorded after the mentioned wait time?
In this case, you will need to manually record a transaction using the “Offline Credit Card” payment method. For reference, you can include the last 4 digits of the card number.


How to refund ‘Tip’?
To refund a tip, follow these steps,


  1. Go to the top bar and select the "Repairs" dropdown menu.

  2. Choose "Manage Invoices" and locate the desired invoice.

  3. Open the invoice, scroll down, and find the Revert button next to the tip amount.

  4. Click the Revert button and use the Refund option that appears to process the tip refund.


If the issue persists, please contact RepairDesk Support for further assistance.


What if Refund is processed by RepairDesk but not received by the Customer?
This can occur if the RepairDesk User selects the wrong payment method instead of RepairDesk Pay. Refunds for card transactions can only be processed using the same payment method initially used to charge the customer (RepairDesk Pay).

To resolve this, ensure that the same payment method is selected for the refund as was used for the initial charge. Only Refunds processed using RepairDesk Pay will reflect correctly.

If the issue persists, please contact RepairDesk Support for further assistance.


What if an Invoice paid using RD Pay is marked as ‘Overpaid’?
To resolve this issue, follow these steps to verify the transaction
  1. Log in to your BlockChyp portal.

  2. Locate the transaction in question (If the transaction is from previous days, check the batch history under the Merchant Tools drop down option).

  3. Verify whether the transaction amount is correct or if an overcharge occurred.

    1. If the issue appears on both BlockChyp and RepairDesk - Refund the extra amount charged using RepairDesk Pay to resolve the issue.

    2. If the issue is only on RepairDesk Invoice - A glitch may have caused the customer to see a double charge or overcharge on their invoice. Update the invoice by deleting the extra transaction or adjusting the overcharged amount through the "Manage Invoices" option.

How to connect wireless terminal with Wifi?
To connect your wireless terminal with Wifi, follow these steps,

  1. Navigate to your terminal’s keypad.

  2. Locate the three-line button.

  3. Press the three-line button for 3 to 5 seconds until you hear a beep, Press the button twice quickly.

  4. Select "Setup" and click "Next."

  5. Select "System Config" and click "Next."

  6. Select "Network" and click "Next."

  7. Select "Enable HTTPS" and click "Next."

  8. Select "WLAN" and click "Next."

  9. Select "DHCP."

  10. Choose your store’s WiFi from the list of available options.

  11. Enter your credentials to connect to your store’s WiFi.