Group Config

BACS and Faster Payments Online group config settings are shown below.

Service User Number (SUN)

A SUN is a 6 digit number used by BACS to identify organisations when submitting payments. NB. Your company could have more than 1 SUN.

Import Schema

When creating a new submission, the payment file being imported must be in a format specified by the “Import Schema”. The possible values are: None - no file can be imported Legacy - original Barron McCann file format Standard18 - in a format specified by BACS Custom - requires a mapping to import the file

A mapping must be linked to the group if the “Custom” import schema option is selected. An additional dropdown is displayed in this instance so you can select the correct mapping for this group.

Bank Account

This is necessary if the originating bank details are needed to create the payment data. E.g. A group with an import schema of “Legacy” will need to set a bank account because a file in Legacy format doesn’t contain the originating bank details, only the destination bank details. NB. paygate Online currently enforces you to select an originating bank account regardless of the import schema.

Click the “View” button next to the bank account dropdown to show the details of the selected bank account.

Payment Signing Method

This determines how a submission linked to this group will be signed. The options are: Smart Card - use a bank issued smartcard to sign a submission. This is BACS specific and the card must be registered with BACS. The benefit to using a smartcard to sign a submission is that your SUN doesn’t need to be linked to the paygate “Bureau Number”.

USB Token - these tokens contain a certificate issued by paygate. When committing a submission using a token, the certificate is verified as being one issued by us. Also the certificates are linked to a specific user so an additional check is made to ensure the certificate on the token is the correct one for the user who is committing the submission. A password is entered by the user to verify they can access the token. NB. These tokens are only supported on Internet Explorer.

Security Code - the user will request a security code which will be sent via SMS to their mobile phone. Your organization must be registered for SMS in order to select this option.

None - no security measures are enforced. This option isn’t recommended.

Individual Payment Limit

The amount of an individual payment item this group can process when creating a new submission.
Set to a default of £0 means there is no limit for an individual item up to the BACS and Faster Payment limits of £20 million and £250,000 respectively.

Submission Limit

The maximum amount of an entire submission which this group can create. Set to a default of £0 means there is no limit.

Segregate Group Roles

When this option is selected each submission stage must be processed by a different user. So each user can either create, sign or approve a submission created for this group.

Bureau Group

A “Bureau Group” is used if you send submissions on behalf of your own customers. For this to be set, the “Import Schema” must be “Standard18”. The SUNs in the “Standard18” file don’t have to be linked to the paygate “Bureau Number”. If they’re not linked then the “Payment Signing Method” would need to be “Smart Card”.

NB. You must purchase an additional licence to use this feature.

Delete Payment Data

When this option is selected, the imported payment data is deleted from the database after the payments have been submitted. While it may be considered more secure to not have your data stored permanently the downside is that searching for previous submissions won’t be as effective.