This document describes how to set up and use POR Payments in Syrinx. The POR Payment App provides a single interface that has been incorporated into Syrinx which then allows taking card payments via a number of supported payment processors such as Stripe and EziDebit. Therefore, the process of taking a payment via the POR Payment App is the same, no matter which payment processor has been linked with the Syrinx system.

Topics included in this article

• Prerequisites

• Enabling POR Payments in Syrinx

• Adding Card Terminals to Syrinx

• Taking Payment in Syrinx

• Customers' Saved Payment Cards

Prerequisites

• The Syrinx version must be v4.40.3 or above.
    
• The Syrinx company database must be registered as a global database in order to access the POR Global API.
    
• The Global database entry must have an active license for “API Keys.”
    
• The customer should already have a user account set up with a payment processor that will be used with the POR Payment App. The customer also has the opportunity to register with the processor when linking it with the Global database, but this can be a lengthy process, and it is strongly recommended that this process be completed prior to linking the processor with the Global database.

Enabling POR Payments in Syrinx

At present, the POR Payments functionality in Syrinx is enabled via a hidden system option “EnableGlobalPayments” that must be enabled via a patch. Note that enabling POR Payments will disable SagePay (if this is already enabled).

Once enabled, there will now be a “POR Payments” tab in Syrinx SP Configuration\System Options\Accounts:

The “Endpoint URL” will be the address of the Global API:

• https://api.pointofrental.com/v1 

The “Payment App URL” should be the address used by Syrinx to access the POR Payment App:

• https://porpaymentapp.azurewebsites.net

The “Default Country Code” will be used if no countries have been set up in Syrinx and/or the customer making the payment doesn’t have a country set against their Syrinx customer record. The value should be a standard ISO code (e.g. GB for United Kingdom).
 

The “Save Card Details” option determines whether or not the system will save a token for the card which can be used for repeat or “Follow-On” payment payments. 
 

The “Enable Debug” check box should normally be disabled. If it is enabled, then when accessing the Payment App, a “developer tools” browser window will also be shown allowing access to console messages, etc., and any error messages raised will be more verbose.

 

Adding Card Terminals to Syrinx

If you have added card terminals via the “Configure Processors” process, you will also need to download their details into Syrinx itself. This is done via the “Card Machines” menu option in Syrinx SP Configuration\General Setup. When POR Payments is enabled, the behaviour of this form changes slightly. The “Add New” button is now shown as “Download” and pressing this button will connect to the Global API and retrieve the currently configured terminals, which will be shown on the form:

Should there be an issue with one of the “Card Machine” entries, that entry can be made non-current by selecting the card machine entry, pressing “Show Detail” to open the “Card Machine Details” screen and pressing the “Make Non-Current” button:

Once the card machine entry is no longer current, it can then be removed via the “Remove” button and then downloaded again to refresh its details in the Syrinx database.

Taking Payment in Syrinx

The taking of payments in Syrinx is essentially the same as previous payment implementations except the “POS / Web” button that would be shown (if SagePay was previously enabled) will now be titled “POR Pay”:

The “Take Payment” form allows you to select the Processor. This list will always show “POR Payment” which is the default, but may also list any terminals that have been imported into Syrinx from the Global API:

Depending on the processor picked and the type of payment, the below payment buttons will be enabled.

Manual Payment

"Manual Payment” will require the user to enter the card and customer address details on the screen (i.e., a Web payment). The address details will be filled in using the site address linked to the source document/invoice, but these values can be overridden if necessary.  Successful manual payments will save a token of the transaction against the card details which will then allow later payments using the “Auto Payment (Token)” option.  Unlike previous implementations, the system will automatically create a “Saved Card” entry against the customer for card information entered via this process and the user will not be prompted to perform this action.

Auto Payments

“Auto Payment (Token)” allows you to use previously saved card details to add payments to contracts/invoices or to credit previous payments taken via POR Payments.  Here, the user will be prompted to select the “Saved Card” details to use, and a “Follow-On” payment will then be created. In cases where a “Saved Card” is no longer valid for a customer, these can be removed from the “Saved Card” tab on the “Amend Customer” screen in Syrinx.

Refunds

Also note that for a credit raised against an invoice or a refund of a payment from a hire contract, the user will be required to pick the previous payment transaction they want to fully or partially credit and will not be able to credit more than the original payment transaction amount.  Also, the POR Payment App does not allow for the creation of a stand-alone credit as they must always be linked to a previous POR payment transaction.

Swipe

“Swipe” is enabled if the user picks a card terminal as the processor. The payment transaction must then be completed on the terminal itself.
 

The actual payment entry screens that will be displayed will differ by the card processor.  For example, when using Stripe the manual payment screen will look similar to the below:

And when using EziDebit, the manual payment screen will look similar to the below:

Customers' Saved Payment Cards

ℹ️Please note, Card details are tokenized and encrypted. So, the card details are not visible to the users.