Civica Pay - eStore2
We've now added no-code support for Civica Pay.
The functionality provided enables you to:
Add a fixed cost payment item control e.g. Black Bin is £35.00
Add a user entry based payment control e.g. Council Tax payment where the user enters in any amount
Add a payment summary where the total of all payments in a form are summarised and passed to the payment system i.e. a Shopping Basket
Set Up
CivicaPayTsbBaseUrl
This is the URL end point fo the payment system's URL. eDesigner enables you to build forms that integrate to payment systems without any technical knowledge.
You get this info from Civica.
CivicaPayTsbCallingAppIdentifier
This is first of three identifiers for Civica Payment system integration.
You get this info from Civica.
CivicaPayTsbCustomerID
This is second of three identifiers for Civica Payment system integration.
You get this info from Civica.
CivicaPayTsbCustomerPassword
This is third of three identifiers for Civica Payment system integration.
You get this info from Civica.
Important
The thing to also be aware of is that we need to set your payment preference to Civica PAY. So if you wish to use this function please tell us at:
Adding Payment Items
A payment item is a fixed price item that a person can buy.
If you choose to add a payment item the following options are presented:
The Field Label is what is shown to the customer when buying it in the form.
The Item Catalogue ID is more commonly known as the fund code but its terminology in Civica Pay.
The Item Reference is the specific payment item reference number of the item.
This manifests itself as illustrated below:
You can, of course, use conditional rules to dynamically show which payment items are presented to customers should you have multiple payment items but only one/or a selection of the total is/are relevant based upon circumstances.
On moving to Civica Pay - we can see the details pushed across:
User Entered Payment
A user entered payment control enables the citizen to type in the amount that they wish to pay.
For this option there are a variety of additional fields that relate to controlling what a user entered amount looks like and its label.
I.e. the format of the numbers they can enter is controlled by a regular expression. We'd say keep this as it is as it's the standard format for currency based entry. You can also add validation and mandatory warnings too:
Above we can see that there's also an option for 'User entered reference'. If this is clicked there are the following additional options which provide you with control over what the format of the reference is in terms of:
Minimum / Maximum Length (E.g. 5 minimum 8 maximum)
Regular Expression (E.g. must start with a 4 contain 6 or 7 numbers but the final one can be x)
Failed Validation message to present if the validation rules above are not met
Mandatory warning text which if present make it mandatory and vice versa removing it makes it optional
If the user types things in wrong you can thus present messages:
Payment Summary
A payment summary automatically tallies up any payment relevant payment items/user entered amounts and acts like a shopping basket.
The only thing required when adding a payment summary is a field id and should you support a different currency (unlikely!) the ability to change the currency symbol:
This is presented like so where two items were requested on earlier pages:
Important
When adding a payment summary remember that it:
a) MUST be after any pages containing payment items/user entered payments
b) MUST be on a page that does not contain any payment items/user entered payments
You can have other content on a payment with a payment summary - just not other payment items.
Last updated
Was this helpful?
