Attrition in merchant services is concentrated far earlier than agents expect. The accounts that leave mostly decide to leave in the first month, not the first year, and they decide on operational experience rather than on price. A merchant who was sold well and then left alone through their first confusing week is a merchant who will take the next call they get from a competitor.
Three moments carry almost all of that risk, and each one takes an agent about ten minutes to handle.
Moment one: the first deposit
The first deposit is the single most anxious event in a merchant's relationship with a payment processor, and it is anxious for a reason that has nothing to do with the processor. The merchant has been paid, the money has left the customer, and it is not in their account yet. Every hour of that gap is spent wondering whether they have been had.
It gets worse when the number does not match. The first deposit is net of fees, frequently covers a partial period, and often arrives as one amount covering several days of transactions. A merchant who processed a known amount and received a different one will do arithmetic, fail to reconcile it, and call somebody. You want to be the person they call, and better still, the person who called them first.
So: tell them before it happens what to expect, in specifics. Which transactions will be in the first batch, that the amount is net, and where in the app they can see the deposit broken down into the transactions that made it. A merchant who can open a deposit and see the line items behind it stops needing to trust you about the arithmetic, which is a far more durable position than being trusted.
Moment two: the first dispute
Most merchants have never seen a chargeback notice and will read it as an accusation. The instinct is either to ignore it, because it looks like spam, or to panic, because it looks legal. Both are expensive: an ignored dispute is a lost dispute, and a panicked merchant makes promises to a customer that create a second problem.
The pre-brief takes two minutes and it is worth more than any amount of post-hoc help. A dispute is a customer asking their bank to reverse a charge; there is a deadline; evidence is what decides it; here is where the notice will arrive; do not refund a transaction that is already disputed, because you will pay twice.
That last point is the one merchants get wrong most often and it is the one that costs real money. A merchant who refunds a disputed charge to be helpful has given the customer their money back and will still lose the dispute.
Moment three: the first statement
The first statement is where a merchant checks whether you told them the truth. They will compare it to what you quoted, and any line they do not recognise reads as a hidden fee, whether or not it is.
Walk it with them once. It costs a phone call and it converts your proposal from a claim into a verified fact in the merchant's own mind. It is also your best opportunity to catch a real problem early, a card mix that does not match what they described, a transaction type clearing at a rate neither of you expected, a plan that is not billing.
Agents skip this because the statement usually confirms what they said, and confirming something feels like a low-value call. It is a high-value call precisely because it is uneventful. You are converting trust-because-they-like-you into trust-because-they-checked.
The setup items worth doing on day one
Beyond the three moments, a short list prevents most first-month support contacts.
- The statement descriptor. Wrong descriptors generate retrievals and then disputes, and it is the single highest-yield thing to get right before any volume runs.
- Who else needs access. A business where only the owner can take a payment will have a problem the first day the owner is out.
- Receipts. Confirm the customer gets one, and that it says what the customer expects to see.
- The refund path. Every merchant will need it in the first month and nobody reads documentation under time pressure.
- Whether recurring plans, if any, are actually enrolling customers rather than being created and left unbilled.
Then stop
There is an opposite failure, and it is less discussed: agents who check in weekly forever. After the first statement, a merchant who is processing normally does not want a relationship manager, they want to be left alone and to know you answer the phone.
Front-load the attention into the week that decides retention, then move to a light cadence and be genuinely reachable. The account you keep is not the one you called the most. It is the one whose first month contained no unexplained surprises.
Michelle Hope
Payments Editor, Paydigo
Michelle Hope writes about payment economics for the businesses that live on them, trade contractors, route-based service companies, and the agents who sell to them. Her work focuses on the unglamorous mechanics: effective rates, recurring-billing recovery, dispute ratios, and the difference between a rate sheet and a statement.