Configuring device specific payment processor settings

When you set your payment processor settings on the back office, this applies to all of your EPOS devices.


If you need different EPOS devices to use different payment processor settings, you can edit the settings on each device individually. 


This could be used to set one device to use a completely different processor. For example, you may use Dojo to process the majority of your payments, but would like to use Zettle by PayPal on your Mini EPOS devices to take advantage of Tap to Pay.


Or, each device could use the same payment processor, but with different settings. For example, one EPOS device could be configured to use a Tabology Reader, and another to connect to a standard Zettle by PayPal Reader.


To set Device specific payment processor settings, go into your Back office and select Setup > EPOS from the left hand navigation.



From the tab row in EPOS settings, click Payment integration.



Scroll down to, Device specific payment processor settings.


Click the blue Edit icon at the end of the device row, to edit the payment processor settings.


Select the processor you would like this EPOS device to use.


Note: If you are using the same processor, but changing the settings, you will still need to select it here.



Fill in any required details and apply any settings you would like this device to use. For example, if using Zettle by PayPal, you can choose:

  • Use a Tabology Reader - A Tabology reader will be used for taking payments on this device
  • Prompt for tips - Any Zettle by PayPal readers connected to this device will prompt for tips



Finally, press Done to save your settings for this device.


Note: If you have set the device to use a Tabology Reader, you will now need to add your Tabology Reader.





Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article