eDesigner - v2.7 - Payment Features Update

This release contains two updates:

• Support for Civica Pay (eStore 2 - Transportable Basket - hereafter called TSB) with details below
• A fix for GOV.UK Pay so that one does not need to have a 'Who Are You' page in order to take a payment through this payment provider

Civica Pay - TSB

Adding to Capita Pay, Civica Paris, GOV.UK Pay, we've now added no-code support for Civica Pay.

This means the functionality we already provide in eDesigner:

• Add a fixed cost payment item e.g. Black Bin is £35.00
• Add a user entry based payment 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

Can now be used with the payment system Civica Pay.

1) Payment Item

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:

2) User Entered Payment

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 you user types things in wrong you can thus present messages:

3) Payment Summary

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:

Release Version Details

The following is the release version info for the version of eDesigner, which has this functionality.