What Your Payment Provider Is Really Saying Yes To

The money it puts at risk for you

A card payment is not final when it lands in your account. The cardholder can dispute it for months. If your customer says the goods never arrived and the issuer agrees, the money goes back to the cardholder whether or not you still have it. If you cannot cover it, responsibility for the shortfall follows the applicable account and acquiring agreements.

Now scale that up. A merchant takes $200,000 in pre-orders for a product that ships in ninety days. The facilitator has paid most of that out. If the product never ships, or the merchant closes, or a fraud ring used stolen cards for half the orders, those payments can become chargebacks, and losses are allocated under the applicable agreements. Across a portfolio of thousands of merchants, it carries this exposure every single day, for sales it did not make, to customers it has never spoken to, on products it has never seen.

Reserves and holds exist because of this. They are among the tools used to manage exposure from a merchant's failure. Where providers go wrong is in how they communicate them, not in having them.

The obligations it carries alongside yours

If you wanted to accept cards directly from a bank, you would need your own merchant account, your own underwriting review, your own PCI validation, any required network registration and the compliance arrangements that apply to your business. Requirements, timing and costs vary by provider and business.

The facilitator handles the responsibilities assigned to it. The merchant’s own obligations remain. It verifies who you are and who owns your company, and keeps verifying as long as you process. It screens you and your beneficial owners against sanctions lists. It registers with Visa and Mastercard, follows their rulebooks, and answers to them when a merchant in its portfolio misbehaves. PCI DSS requirements and validation depend on the payment environment and the account. It analyzes whether the way your money flows makes it a money transmitter under state and federal law, and licenses or structures accordingly. Its monitoring and reporting duties depend on its role and applicable law.

Every one of those is a cost and a liability. If a merchant turns out to be laundering money or selling something prohibited, each party remains responsible for the obligations that apply to it. When it says yes to you, it is betting its own standing with the banks on your business being what you said it is.

Why the yes is special, and how to be worth it

Seen this way, approval is not the start of a vendor relationship. It is the start of a partnership in which one side has already put its balance sheet and its reputation behind the other. The best merchants treat it that way.

They keep their business description accurate, because the facilitator underwrote the business they described. They tell their provider before a launch, a seasonal spike or a large order, so growth looks like growth and not like fraud. They ship on time, keep tracking and delivery proof, and answer customer complaints before they become disputes. They respond when the risk team asks a question, because that question is usually a person trying to avoid a hold, not impose one.

None of this is servility. It is the same courtesy you would extend to a partner whose responsibilities depend on your business being what you described.

How Etail Depot sees it

We take on the responsibilities assigned to us, and we think the merchants we accept should know exactly what those are. In return, we owe you the same clarity: reasons where disclosure is permitted, the funding terms for your account, and a support contact when you have a question.

Trust extended in one direction becomes resentment. Extended in both, it becomes the kind of payments relationship that survives a bad quarter, a fraud attack or a record-breaking Black Friday. That is the relationship we are building, one approval at a time.