# Direct Debit Mandate Details and Bank Validation in Go Operator

HTML version: [Direct Debit Mandate Details and Bank Validation in Go Operator](https://support.gladstonesoftware.cloud/gooperator/direct-debit-mandate-details-and-bank-validation-in-go-operator)

## Problem
Sites selling Direct Debit memberships on Go need the mandate, online DD guarantee and price breakdown to show the right details, and need bank details validated, without spending lookup credits in test.

## Resolution

1. **Open the settings**
   - In Operator go to `Configuration > Modules > Configure`.

2. **Enter the Direct Debit details**

   | Setting | What to enter |
   |---|---|
   | **Company name** | Your legal company name |
   | **Operator trading name** | Usually the same as the company name. Also the organisation name shown on Go |
   | **Service user number (SUN)** | Supplied by your finance team |
   | **Advance notice (days)** | Notice given before a change to DD amount or frequency. This is your own policy, commonly somewhere between 3 and 10 days; use the value your DD agreement states |

   - These pull through to the automatic DD mandate and to the **online DD guarantee** shown at the end of sign-up, which banks expect to see.
   - Have finance approve the DD confirmation wording.

3. **Word the mandate for third-party collection (if applicable)**
   - If payments are collected by another body (e.g. a council on behalf of a trust), say so in the mandate wording (e.g. "collected by X on behalf of Y").

4. **Check the purchase breakdown and contract totals**
   - For a DD membership, Go shows the **pro-rata** amount today and the **recurring** amount after that. Both come from the Plus2 price product behind the subscription.
   - Consumer rules require the **total amount payable over the contract** to be shown too, which matters most for committed-term memberships (e.g. a 12-month minimum term). Check with Gladstone Support what your version of Go displays, and test it on each committed-term membership.

5. **Enter the GB Group credentials**
   - Address lookup and bank validation use GB Group. Enter the site's GB Group username and password, then switch on the licences the site holds.
   - **Bank validation is required when selling DDs**; email and phone validation are optional.

6. **Save and test**
   - Save, then check the mandate, guarantee and breakdown in the customer journey on your **test** site.

## Notes

- Update all of the Direct Debit details if the company name or SUN changes.
- The 360 DD mandate document and the DD confirmation emails sent from 360 use the same details, held in the GMC. Keep both consistent.
- In 360, selling a committed-term DD shows staff the earliest end date.
- DD collections, rejections and the EFT module are managed in the GMC and Plus2; see [How to Perform an EFT or AUDDIS Run in GMC](../gladstone360/how-to-perform-an-auddis-or-eftdirect-debit-run-in-the-gmc.md) and [Direct Debit Set-Up in Plus2](../plus2/direct-debit-set-up-in-plus2.md).
- Lookups use paid credits, so don't use them in test. After any live-to-test copy, check validation is off in the test Operator settings, because the copy carries the credentials into test. See [Testing Gladstone Go Before Go-Live](testing-gladstone-go-before-go-live.md).
- Older guidance describes GB Group as "formerly Capture Plus"; current guidance describes Loqate Capture+ as the service replacing GB Group Matchcode, set with a **Capture+ Auth Key** and **Validation Provider**. If your settings show Capture+, follow [Enabling Capture+ Validation](enabling-capture-validation.md).
- Plus2 has its own bank validation and address lookup settings: see [Configuring GBGroup for Plus2](../kb/configuring-gbgroup-for-plus2.md).
- Related: [Go Join Joining Settings in Operator](go-join-joining-settings-in-operator.md); [Information to Collect Before Configuring Go Operator](information-to-collect-before-configuring-go-operator.md).