How to Set Up Your Payment Request Settings
This guide will walk you through configuring your Payment Request Settings to ensure a smooth experience for both your team and your customers / clients. By following the steps below, you’ll set up only the relevant payment methods, avoid presenting unsupported options (such as cards, Apple Pay, or Google Pay), and define clear rules for payment terms, notifications, and account settings.
The goal is to make sure that when clients interact with your payment requests, they only see valid, functional options, reducing confusion and preventing failed payment attempts. At the same time, you’ll maintain flexibility for your team by allowing overrides where appropriate.
Note: this is a basic guide and may not suit your business operations. Feel free to set whatever settings you desire that work best for your users who are setting up payment requests.
First, navigate to the Payment Request Settings. Click here for an overview.
You can do this by going to the Accounts Receivable module → Settings → Basic settings.
Available payment methods
Under ‘Available payment methods’ → leave ‘Pay by bank’ toggled on and the rest off (as below).
If you do not have cards, Apple Pay, or Google Pay set up, these payment methods should not be toggled on and presented to clients / customers, as it will only cause confusion when it does not work.
Make sure that this section is set to ‘Don’t allow override’:
Payment terms
Under ‘Payment terms’, you can determine whether clients pay in full or partially. Initially, you can set this to ‘Require full payment upfront’. If you’d like, you can set this to ‘allow override’ which will allow users to change this to partially during set up.
Notification
Under ‘Notification’, make sure that none of the boxes are ticked as below. Allow users to override this setting if they want to be notified whenever a payment is made via email:
Default destination account
Under ‘Bank payment options’, you can set a default destination account. Leave these blank if you are using different accounts to collect payments.
Set this to ‘allow override’ so that users can change the destination account during set up.
Prioritise a bank option
Similar to the default destination account section, you can leave these fields as No bank selected for now and set this to ‘don’t allow override’. If you select a bank, it will appear as it's own icon on the hosted payment page.
Card payment capture
Under ‘Card payment options’ (on the left sidebar), leave as automatic capture unless you would prefer to manually capture payments. Set this to don't allow override.
Form Configuration
Under ‘Form configuration’, you can determine what default and custom fields you want to show clients / customers:
There are fields that appear to users during set up (requirement column) and to external customer / clients (display for payer column) when making a payment. For example, you can set the Customer information as required for your team to enter but have it not appear on the payment link to the external customer client - only on receipts (see last row in screenshot above).
Similarly, you can have it set that your team must enter a case reference number, but the customer / client never sees this:
