Confirm the use case
Identify why manual payment entry is needed and which transactions the provider allows. Compare it with hosted payment links that let the customer enter information directly.
Assess a provider-supported way to take remote payments.
Assess a provider-supported way to take remote payments.
Identify why manual payment entry is needed and which transactions the provider allows. Compare it with hosted payment links that let the customer enter information directly.
Give access only to the staff who need it and follow the provider’s handling requirements. Do not retain full card details in ordinary notes or spreadsheets.
Manually entered transactions may have different costs, evidence requirements, and risk treatment. Confirm receipts, refunds, and support routes before use.
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.