Choosing a payment provider
Before You Sign: 12 Questions to Ask a Payment Processor
Compare payment processor fees, settlement, reserves, contracts and support with 12 questions to resolve before you sign.

A payment processor becomes part of your daily business. It affects how customers pay, when money reaches your bank, what your team can see and who helps when something goes wrong. A low advertised rate is useful information, but it does not describe that whole relationship. Before you sign, you need to understand the operating arrangement behind the quotation.
These twelve questions help you compare providers on the same basis. Use them in a meeting, send them with a request for a proposal, or work through them with your finance and operations teams. For every important answer, ask where it appears in the agreement, pricing schedule or supporting documentation. A verbal explanation should help you understand the documents, rather than replace them.
The right answer depends on what you sell, where your business and customers are located, how you deliver and which systems you use. No single price model or feature list suits every merchant. Begin with your actual requirements, then test whether the proposed service fits them. Our payment solutions overview can help you identify the areas to discuss.
Explore payment solutions for your business →
Follow the money, not just the sale
Payment approved
Confirm what the approval means.
Funds settled
Check deductions and any restrictions.
Payout sent
Identify the cutoff and banking calendar.
Bank receipt matched
Connect the deposit to its payment records.
1. Who are we signing with, and who approves our account?
Ask for the legal name of each organisation involved and a clear explanation of its role. The company presenting the offer may introduce the service, supply the gateway, provide the merchant account or combine several functions. Find out who receives your application, who makes the approval decision, who holds the contractual relationship and who is responsible for paying funds to you.
Check that the proposed arrangement covers the business you actually operate. Describe your products, delivery times, sales channels, expected transaction sizes and customer countries accurately. If you have several companies or trading names, ask which entity is being assessed and which names customers will see. Approval for one business activity or company should never be assumed to cover a different one.
Get a list of the documents still required and ask which commercial terms remain subject to review. Distinguish an initial quotation from a final approval. Before committing to a launch date, establish what must happen between application, approval, account access and the first live payment. Keep the named contacts and responsibilities together so your team knows where to direct questions.
Request the contracting entity names, approval scope, outstanding requirements and named owner for onboarding.
Prepare your business information for payment-provider checks →
2. What will the complete cost be for our payment mix?
Ask for the full pricing schedule, including transaction charges and charges that arise outside a successful sale. Discuss setup, monthly service, gateway access, terminals, software connections, refunds, disputes, currency conversion, payouts and any minimum commitment. Ask which charges come from the provider and which depend on the card network, payment method or another party. Do not compare a headline percentage with a quotation that includes more of the service.
Give each provider the same operating assumptions: expected volume, typical sale value, card and payment-method mix, customer locations and the split between online and in-person sales. Ask how the proposal changes when those assumptions change. A business with many small purchases has a different cost pattern from one with fewer large invoices, even where monthly sales are similar.
Request a worked illustration and a sample statement that connect the quoted charges to the way you sell. Keep processing charges separate from reserves or withheld funds, because a temporary restriction on access to money is a different issue from a fee. Also ask which charges can change, who controls them, how changes are communicated and where that process appears in the documents.
For an existing business, compare a representative trading period rather than an unusually quiet month. Include staff time spent resolving unexplained deductions or reconciling reports in your operational review. The aim is a transparent comparison, not a promise that one provider will always cost less.
Request an itemised pricing schedule and a worked cost illustration using the same assumptions for every provider.
Review card-processing requirements →
3. When will money actually reach our bank account?
A successful payment and an available bank balance are different stages. Ask the provider to walk through a transaction from authorisation and capture to settlement, payout and bank receipt. Find out which stage starts the promised timing and whether the schedule refers to business days, calendar days or a particular banking calendar. Ask for the relevant time zone and daily cutoff.
Work through an ordinary trading day, a weekend, a public holiday and a payment received after the cutoff. Ask whether new accounts begin on a different schedule and whether a change in volume, business model or risk review can affect payouts. Where several currencies or local payment methods are involved, confirm the timing for each route rather than assuming the card schedule applies everywhere.
Clarify whether fees, refunds, disputes and reserves are deducted before the payout or collected separately. Ask which report explains the difference between gross sales and the money received. Your finance team should be able to connect the payout reference to its underlying transactions. Write the expected schedule into your cash-flow planning, leaving room for the exceptions described in the agreement.
Request a dated example showing the payment, cutoff, payout and expected bank-receipt stages.
Understand the payment reconciliation workflow →
4. Can you hold funds or require a reserve?
Ask whether the provider can retain funds, delay a payout or require a reserve, and under what circumstances. Discuss the proposed arrangement for your business, rather than only the provider’s general marketing description. A reserve may be structured in different ways, so ask how the amount is determined, which transactions it affects and how changes are communicated.
Find out how held amounts are reviewed and released. Ask what information you can provide during a review, who makes the decision and how you can obtain an explanation. Review the treatment of refunds and disputes while funds are held. If your business takes payment well before delivery, explain that clearly and ask how the delivery period influences the proposed terms.
Also ask what happens after the relationship ends. Closing an account does not by itself tell you when outstanding funds will be released or how later claims will be handled. Record the applicable conditions and contact route. Your team needs to distinguish money that has been paid out, money still pending and money restricted under the agreement before relying on it for payroll, suppliers or customer refunds.
Request the reserve and hold provisions, review process, release conditions and treatment after termination.
5. Which payment methods, countries and currencies are included?
Separate three questions: where your company may be established, where your customers may pay from and which currencies can reach your bank. Those are different dimensions of coverage. A provider’s presence in a market does not automatically mean that your business can accept every local method there or settle in the currency you prefer.
List the countries and payment methods that matter for your customers now, then identify what you may need later. For each one, ask whether it is included in the proposal, requires a separate application or depends on another provider connection. Distinguish accepting customer payments from sending money to recipients. Confirm any business-category restrictions before planning a launch.
Ask who performs currency conversion, how the exchange rate and related charges are determined, and how converted amounts appear in reports and refunds. Use your own customer journeys to check the proposal. A traveller buying in a shop, an overseas online shopper and a business paying an invoice can require different payment experiences even when they are in the same country. Make the priority routes explicit rather than buying a long list of possibilities you may never use.
Request a written matrix of merchant countries, customer markets, payment methods, collection currencies and settlement currencies.
Explore payment methods by customer country →
Give each task an owner
Your business
Customer communication, staff access and the records you must supply.
Your provider
Agreed processing, support and account-management responsibilities.
Your shared process
Clear handovers for security checks, refunds, incidents and disputes.
6. Will it work with our checkout, terminals and business systems?
Name the systems your team already uses, including the exact checkout platform, point-of-sale system, booking software and accounting tools. Ask whether each connection is supported today, what it supports and who maintains it. A general statement that a provider integrates with a platform is not enough to establish that your particular setup and workflow are covered.
Walk through a normal sale and the awkward cases: a failed attempt, a duplicate click, a partial refund, a cancelled order and an interrupted connection. Ask how payment status is passed back to your system and how your team can confirm the final outcome. For recurring payments, establish how the customer relationship and payment instructions are created, changed and ended.
Agree who performs setup, testing and staff training, along with any separate costs. Ask for a realistic test environment or demonstration and define what successful testing means for your operation. If you are replacing an existing service, plan a controlled change with a clear fallback. Keep the old arrangements available until you have verified that the new route can accept payments, issue the required records and support your daily reconciliation.
Request a compatibility list, responsibility split, test plan and agreed process for switching over.
Match payment methods to your business workflow →
7. Which security and PCI DSS responsibilities remain with us?
Ask where card data enters the process, which parties can access it and which parts of your business environment remain involved. The answer may differ between a hosted checkout, a terminal, a telephone payment process and a custom connection. Request a clear explanation of your responsibilities and the evidence your acquiring or payment provider expects you to maintain.
The PCI Security Standards Council explains that outsourcing processing does not remove the merchant’s responsibility for protecting account data through its providers. Ask how that applies to the service being proposed. Confirm the relevant validation route with the responsible provider and distinguish optional support services from the actual duties your business retains.
Discuss staff access, multifactor authentication, software updates and the process for reporting a suspected incident. Ask who owns each task, how access is removed when someone leaves and what assistance is available when requirements change. Keep passwords and complete card details out of ordinary email or support messages. A useful security explanation leaves your team with named responsibilities and a practical process, rather than a broad assurance that everything is handled elsewhere.
Request a security responsibility summary, provider compliance evidence and confirmation of your validation requirements.
PCI SSC explains merchant responsibilities when payment processing is outsourced. ↗
8. How will fraud, refunds and disputes be handled?
Ask which fraud controls are available for your payment channels and who configures them. Find out how your team reviews a flagged payment, what happens to an order while it is reviewed and how a change in settings affects the customer experience. Avoid treating the presence of a fraud tool as a guarantee that fraudulent payments or legitimate declines will disappear.
Next, follow a refund and a customer dispute from start to finish. Confirm which staff can issue refunds, how partial refunds work, how they are funded and which charges apply. For disputes, ask where notices appear, how deadlines are communicated and what evidence your team must provide. Establish who submits the response and how the outcome is reported.
Visa’s merchant guidance stresses prompt responses to dispute notices from the acquirer. Build your internal process around the deadline actually provided for each case. Identify a backup owner for holidays and absences. Ask how the provider handles a customer who has already received a refund or a case involving several related payments, so your team can avoid confused or duplicate action.
Request a demonstration of a refund and dispute case, including permissions, evidence, deadlines and charges.
Build a clearer chargeback-prevention process →
Visa explains why merchants should respond promptly when an acquirer raises a dispute. ↗
9. What can we see and control in the merchant portal?
Ask for a demonstration using the roles your business will need. The owner, finance team, store manager and customer-support team may each need different access. Check whether permissions separate viewing transactions, exporting records, issuing refunds and managing users. For a group with several locations or companies, ask how access is limited to the appropriate business records.
Find an individual payment, match it to an order, locate its payout and export the information needed for reconciliation. Check that reports show fees, refunds, disputes and any withheld funds clearly enough for your team to explain the bank receipt. Ask which information is available through the portal and which requires a separate report or connection.
Finally, test the access journey itself: account invitation, first sign-in, multifactor authentication, password recovery and removal of a user. Confirm who administers your account and how access is restored if the main administrator is unavailable. An impressive dashboard is only useful when the right people can use it safely and retrieve the records their jobs require.
Request a role-based portal demonstration and a sample export that your finance team can reconcile.
Plan the records your finance team needs →
Compare the written answers
Cost
Full schedule and common trading assumptions.
Cash flow
Payout timing, deductions and reserve conditions.
Operations
Tested systems, reporting and support.
Exit
Notice, linked contracts and access to records.
10. Who helps when payments stop or a payout is missing?
Ask who provides support after onboarding and which hours, languages and channels are covered. Distinguish commercial questions from technical faults, payout investigations, fraud alerts and disputes. If different organisations handle different parts of the service, find out whether one contact coordinates the case or whether your team must approach each party separately.
Run through a realistic incident: your shop cannot take payments, customers see errors at checkout, or an expected payout is missing. Ask what details support needs, where the case is recorded and how it is escalated. Request the relevant service commitments in writing, including any limitations. Availability of a support channel does not by itself establish a response or resolution time.
Check how service interruptions and planned maintenance are communicated. Agree who in your business receives notices and who can make operational decisions during an incident. Keep a short internal contact guide with the account references support needs, but no passwords or sensitive payment details. Review it when staff or providers change so the first minutes of an outage are spent investigating rather than searching for the right number.
Request support coverage, escalation contacts, incident procedures and any written service commitments.
11. What are the renewal, change and cancellation terms?
Read the length of the agreement, its renewal process and the exact way notice must be given. Ask whether cancelling a service also ends connected gateway, terminal, software or support arrangements. Identify any separate contract, notice period, return requirement or continuing charge. The commercial offer and all linked documents should tell a consistent story.
The UK Payment Systems Regulator has highlighted long terminal-contract lock-ins as an obstacle to switching providers. Treat that as a reason to check linked equipment arrangements carefully, not as a statement that the same terms or rules apply in every country. Ask who owns the equipment, how it is returned and what happens if it is damaged, replaced or no longer compatible.
Check whether pricing, supported activities or service terms can change during the relationship, and how you will be told. Ask what happens if either party ends the arrangement, including access to records, remaining payouts and later disputes. Where a clause is important or unclear, have it explained before signing and obtain qualified advice on its legal effect where needed. Keep the final agreed documents, not only an earlier sales presentation or email.
Request every linked agreement, the renewal and notice dates, exit charges and equipment-return conditions.
The UK PSR highlights how lengthy terminal contracts can discourage merchants from switching. ↗
12. What can move with us if we change providers later?
Ask which business records you can export, in what format and for how long they remain accessible after the account closes. Include transaction history, payout references, fees, refunds and dispute records. Your finance and support teams may still need those records after new sales have moved elsewhere. Check who can request an export and whether a separate charge applies.
For stored payment details and recurring customers, ask a more specific question: can the relevant payment credentials or tokens be transferred securely to a new provider? Portability depends on the arrangement and the parties involved. Do not assume that a token usable in one service will work in another, or that an ordinary transaction export contains transferable payment credentials.
Plan the customer experience and the remaining obligations as well as the technology. Confirm how subscriptions, pending refunds, open disputes and outstanding funds are treated during a change. Some customers may need to provide fresh payment instructions. Agree the responsibilities and sequence before ending the old service. A clear exit plan protects continuity even when you expect the provider relationship to last for years.
Request data-export terms, any supported credential-transfer process and a continuity plan for recurring payments.
Review the requirements for recurring collections →
Turn the answers into a decision
Keep one comparison sheet with a column for each provider and a row for every question. Beside each answer, record the document or demonstration that supports it. Mark unresolved points clearly and give someone responsibility for following them up. A missing answer is not proof that an offer is unsuitable, but it is a reason to investigate before relying on it.
Compare the same business model, trading assumptions and payment routes across proposals. Include the people who will use the service, especially finance, operations and customer support. Ask them to identify anything that would create manual work or make a customer problem hard to resolve. Then weigh cost alongside cash flow, compatibility, control and the ability to leave on understood terms.
Before signing, ask for confirmation of any material change from the original proposal. Save the final documents and create a short operating summary for your team. The strongest decision is one your business can explain and operate, not simply the offer with the most confident sales presentation.
Discuss your payment requirements with Lefebvre International
Lefebvre International helps businesses frame their payment requirements and discuss the relevant merchant-services, international-payment or enterprise-payment route. Bring your sales channels, customer markets, current arrangements and the questions you still need answered. An initial merchant-services enquiry is free.
Approval, payment-method availability, reserves, settlement arrangements, pricing and contractual terms are confirmed by the relevant provider. Start with a clear picture of your operation so the discussion centres on what your business needs, rather than a generic feature list.
Request a free merchant-services enquiry →
Frequently asked questions
Is the lowest processing rate always the best offer?
No. Compare the complete pricing schedule using the same trading assumptions, then review payout timing, reserves, compatibility, reporting, support and exit terms. A low quoted rate may cover a different mix of services or transactions. Ask for a worked illustration so your team can see which costs are included and which depend on actual activity.
Does an approved payment mean the money is available immediately?
No. Approval, settlement, payout and bank receipt are separate stages. Ask your provider which stage its timing refers to, which cutoffs and banking calendars apply, and what can delay access to funds. Include deductions and any reserve conditions when planning cash flow.
Can one payment arrangement cover all our countries?
That depends on the provider, your contracting entities, business activities, customer locations, payment methods and currencies. Ask for confirmation of each priority route. Separate where the business may be established from where customers can pay and where funds can be settled. A broad coverage claim is not a substitute for approval of your own operation.
Can we switch providers without interrupting recurring payments?
Sometimes, but continuity must be assessed before you cancel the existing service. Ask whether the relevant credentials or tokens can move securely, whether the new provider can use them and whether customers need to give fresh instructions. Keep responsibility for pending refunds, disputes and historical records clear during the transition.
What should we prepare for a first payment-services discussion?
Bring your website or sales channels, a description of what you sell, company and customer locations, expected payment activity, typical transaction sizes and delivery times. Existing merchants can also bring a representative statement and a list of operational problems. Share sensitive documents only through the secure process specified by the responsible provider.


