Pay360

Integrating online forms with line of business applications can be a complex technical requirement. So it is even more complex to be able deliver a user friendly way of delivering this integration by staff that are not trained developers. This ability is commonly known as ‘low code’.

The way this functionality to integrate online services with your payment system has been designed, it is beyond low code; it's ‘no code’.

High Level

The functionality we provide is comprised of five functions. These provide the ability to:

1) Add fixed value payment items that a person can choose to buy

2) Add a user entered value control where the citizen can type how much they wish to pay

3) Add a shopping basket that tallies up all payments before submission - the payment summary

4) Prepopulate the Capita Pay360 interface with name, address etc. from the eDesigner form

5) Send internal email(s) upon submission per form

To add a payment element, one simply clicks on Add Item in the Designer function and then clicks on the payment tile:

There are then the following three options:

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:

Once added to the form it will appear like so:

You should use Page Rules to dynamically hide/show the payment amount the person needs to pay.

The relevant fields you can add and what they are:

Element

What is it?

Field Label

This is what the customer will see when they’ve selected what they want

Amount

The amount one needs to pay for the item

Tax included

The ability to set a VAT amount against an item

Currency Symbol

Used purely for those taking payments in other countries

Item Description

This is the description passed to the payment system as the description and what is shown in the payment summary

Item fund code

This is the payment system’s fund code

Item amount

This is the amount specific to the item

Item reference

This is the budget code / payment reference code

Where the 'Tax included' check box has been ticked, the user is able to provide a breakdown of the VAT code (as held in Capita Pay360), the % and the amount:

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 suggest you keep this as it is, as it's the standard format for currency based entry.

You can also add validation and mandatory warnings too.

You can configure it such that there is a fixed item reference or enable the customer to enter this i.e. Council Tax account number. If the check box 'User entered reference' is clicked the following additional fields are displayed for completion:

Field

What it does

Reference field label

Tells the citizen what to enter e.g. Rent account number, overpayment reference

Reference field minimum length

The minimum length of the reference they need to enter

Reference field maximum length

The maximum length of the reference they need to enter

Reference field regular expression

The ability to control the format well beyond the min/max settings about.

To learn more about regular expressions have a read below:

https://www.regular-expressions.info/quickstart.html

To search for examples of regular expressions - so you don't need to learn them - please see here:

https://regexlib.com

Reference field validation error message

If the citizen enters a value that is too short/long or doesn't meet the rules of the reference as defined by the regular expression, you can control the content of the message presented.

Reference field mandatory warning

If the citizen doesn't enter a value, you can control the content of the message presented.

Include help text for reference field

If checked, you're able to then provide help text for your custom reference field.

Purchase 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.

Internal Email Receipts

It is possible to send an email receipt of the payment on any form to an email addresses or addresses as set by you.

The functionality is accessed using the 'Payment Settings' button on the Designer menu:

Here you can tick the box to enable the function - 'Email payment receipt internally'. Then use the 'Add a new email' button to add the email address(es) that should receive the receipts:

IMPORTANT

This email is actually sent from the Capita system. This functionality essentially tells Capita who to email.

Therefore the functionality and the content within the email itself is controlled entirely by the Capita Pay360 application.

You should therefore raise any issues with these emails with Capita support.

Unlike most payment systems where one passes the amounts and things to buy, there is a stage which asks about name, address, email etc. in the Capita Pay360 flow.

To ensure these details are automatically populated from the eDesigner form, there's functionality to ensure that any of the following can be passed to the Capita payment system :

PersonTitle
Firstname
Surname
Email
AddressFieldsAddressLine1
AddressFieldsAddressLine2
AddressFieldsAddressLine3
AddressFieldsAddressLine4
Postcode

Ultimately ensuring that it is quicker to make / take a payment from a form. The functionality is accessed using the 'Payment Settings' button on the Designer menu:

Once in here one can see there is a new 'Pre-populate customer details in payment system' option:

If this is checked/ticked then the following fields (using the standard fieldids) from the 'Standard' or 'Blank' Who Are You page will be used to to pre-populate the Capita payment screen.

PersonTitle
Firstname
Surname
Email
AddressFieldsAddressLine1
AddressFieldsAddressLine2
AddressFieldsAddressLine3
AddressFieldsAddressLine4
Postcode

There is also an option to pre-populate these pieces of data from any page within the form. To do so you need to check the 'Override default 'Who are you' field XPaths' option.

You don't need to override the defaults and therefore have to delve into the realm of XPaths. It's specifically if you want to use field ids on pages that are not the standard ones.

An XPath is a technical term to indicate which field on which page of the form you want to refer to.

So in this case the XPath can be used to override the standard behaviour if:

a) You don't have a WhoAreYou page

b) The details to pre-populate are on a later page.

The UI is illustrated below:

To help give an example let's say you have built a page called My Information and you want to use the email address from that page in the pre-population of Capita. If you go to that page you will see its XPath name in the URL.

I.e. this form is PAYMENTTEST, the page it is on is myinfo as that is what is shown in the URL:

So in the XPath description we need the page id to be myinfo:

page[@id='myinfo']/....

But this only tells eDesigner which page the field is on. The next thing you need to do is add the field id for the field you want to map. So if the Field ID for the form is myinfoemail, as shown in the screenshot below:

The XPath override value would therefore be:

page[@id='myinfo']/myinfoemail

We can see that we have adjusted which field will be used to pre-populate Capita by placing the above into the Email override field:

Capita Pay360 Set Up

CapitaPaymentEndPointAddress

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.