Try it for Free

Getting Started on Tyro (AUS only)

Interested in learning more about Tyro?

Complete this form and someone from the team at Tyro will be in touch.

For any Tyro inquiries call 1300 966 639 (this service is available 24/7)

In this article:

Connecting Power Diary to a Tyro Terminal

Before connecting your terminal to Power Diary you’ll need to ensure that it has been activated by Tyro.

You’ll need to connect your Power Diary account to your Tyro terminal to begin submitting claims and processing payments using Power Diary and your Tyro terminal. You can connect Power Diary to your terminal by following the steps below.

  1. Log into your Power Diary account and go to Settings Integrations Tyro Settings. If not already done, toggle the slider to enable Tyro. 
  2. On the terminal, go to Menu → Configuration Integrated EFTPOS Pair with POS.
  3. Select the Pair with POS option.
  4. The terminal should then display a Merchant ID (MID) and a Terminal ID (TID). Enter these into the relevant fields in Power Diary.

  5. In Power Diary, click Commence Pairing
  6. Press the Start option on your terminal. 

And that should be it! If all went to plan you should see a modal indicating that the pairing was successful. Feel free to close this and begin using your terminal

TIP 💡 - you could use any terminal at any location, but you would need to pair the terminal each time (terminal info is stored locally in the browser)

Configuring the Multi-Merchant Functionality

Power Diary users can be configured with a Tyro merchant ID so that payments are made directly into a specific bank account. This is useful in situations where you want payments to be deposited directly into varying bank accounts (as opposed to just one central bank account). Follow the steps below to add a merchant ID to a user:

  1. Go to Settings  Integrations → Tyro Settings
  2. Select Merchants from the menu.
  3. Click + Add Merchants.
  4. Complete the form and click ✔ Save
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.