How to configure billing details
Inugo will configure billing details on your behalf.
Process
Log into the customer management portal and select billing in the left menu.
Select add billing details.
Add company info. These details will show on the parker’s receipt.
Payment Provider will be Payment Express.
Enter the payment provider detail per the below table.
Customise the accepted card types.
Set the convenience fees applicable to monetised transactions.
Configure if a card fee is applied to all monetised transactions and set the fee.
Select create billing details.
Once created, to add in the branding details click the ellipse '…' on your newly created billing detail and select edit.
Under QR code click edit.
Under branding, select the brand to be used.
Select review.
Select update billing details to complete the process.
Field name | Description |
|---|---|
Company name | The legal name of the company |
Tax number | the relevant tax number for the region of the company. i.e., for NZ this is the GST number. |
Billing address | |
Payment Provider | Use payment express unless otherwise instructed. |
PX Post credentials | These are the Windcave MID credentials to access the API on behalf of a customer to enable mobile payment. These credentials can be associated to many billing details. A MID represents a bank account. |
PX pay credentials | These are the Windcave MID credentials to access the API on behalf of a customer to enable web based Scan-to-Pay payment. |
Merchant Account Settlement | Use non-inugo. Inugo do not offer inugo settlement to new customers. These credentials can be associated to many billing details. A MID represents a bank account. |
Default billing details | toggle to set the credentials in the current configuration as the default for all new sites/locations created under this account. Most clients disable this setting as they prefer a configuration per location. |
Accepted credit card types | If you want to remove a card type, click the grey cross. This will mean that payments from this card type will not be accepted on site that are associated to this billing configuration. |
Convenience fee table | There is one fee table per billing configuration which applies to all monetised transactions. This will apply on transient sessions, bookings as well as payments via scan to pay and mobile payment. |
Paid by | this should be consumer. If operator is selected, no billing is produced for the convenience fees. This triggers the calculated convenience fees to be shown under the second heading in the revenue report. Selecting this does not correlate with the transaction fees paid to Inugo which are calculated and billed separately. |
User pays credit card fee | This is a fixed dollar amount that can be set to charge all monetised transactions with a charge for using a card. This is in addition to what has been configured in the convenience fees. Use this as a form of recovering payment processing fess. Setting a charge here, will itemize on the parker’s receipt a charge for credit card fees, and this charge will show under the credit card fees in the revenue report. |
QR code enabled | toggle to green if Scan to Pay is enabled on this billing configuration. You should only toggle this to green if you have entered PX pay credentials. |
Sites | Allocate the sites/locations that will use this billing configuration. One site can only have one billing configuration. You may need to consider subdividing your site if you require multiple billing details. |
Frequent Queries
Can a MID be allocated to multiple sites?
A mid can be configured on multiple billing details, therefore the same MID can be used across multiple sites. Otherwise you can have one set of details that is allocated to multiple sites to simplify the configuration.
How many billing details can be associated to a site?
There can only be one billing configuration per site.