Define the request
Use the provider-supported link flow and a clear invoice or order reference. Confirm amount, currency, expiry where supported, and who can create or cancel requests.
Give customers a clear route to pay remotely.
Give customers a clear route to pay remotely.
Use the provider-supported link flow and a clear invoice or order reference. Confirm amount, currency, expiry where supported, and who can create or cancel requests.
Check how staff learn that payment is complete and whether the information reaches the invoice or order system. A sent link does not mean a paid invoice.
Agree reminders, duplicate requests, partial payments if supported, and refunds. Avoid collecting card information through ordinary messages or forms.
The agreement should explain each part of the service.
Compare the published starting model with your transaction mix. Final rates, fees, and eligible transactions are confirmed in the merchant agreement.
Hardware, applications, gateway subscriptions, implementation, training, and support are itemised as relevant. Confirm recurring costs as well as initial setup.
An eligible arrangement can include a defined website or marketing benefit. Select the benefit that supports the business and review its conditions alongside the payment terms.
Approximate business information is enough to start.
List the provider, software, devices, monthly sales range, and the problems you want to solve. Do not submit card or bank account information in the enquiry form.
Describe a normal payment and an exception, including which records need updating and who needs access.
Tell us about opening dates, peak trading, and staff availability. Implementation depends on provider readiness and the agreed scope.