
{"id":233119,"date":"2026-09-28T12:54:00","date_gmt":"2026-09-28T12:54:00","guid":{"rendered":"https:\/\/mycryptomania.com\/?p=233119"},"modified":"2026-09-28T12:54:00","modified_gmt":"2026-09-28T12:54:00","slug":"iso-vs-payfac-vs-acquirer-who-actually-gets-paid-when-you-swipe","status":"publish","type":"post","link":"https:\/\/mycryptomania.com\/?p=233119","title":{"rendered":"ISO vs PayFac vs Acquirer: Who Actually Gets Paid When You Swipe?"},"content":{"rendered":"<h4>Three payment models that look identical on a slide deck and feel nothing alike in real\u00a0life<\/h4>\n<p>A founder I\u2019ll call Dev launches a small booking app for salons. In week one, a customer pays for a haircut. Dev checks his dashboard, sees the money, and assumes payments are basically solved.<\/p>\n<p>Then a chargeback arrives. Then a compliance email. Then a question from his payment provider that he can\u2019t answer: who, exactly, is responsible here?<\/p>\n<p>That question is why this article exists. ISO, PayFac and acquirer get tossed around like synonyms. They aren\u2019t. Pick the wrong one and you\u2019ll find out at the worst possible\u00a0time.<\/p>\n<p>ChatGPT Generated Image<\/p>\n<h3>Four players and a\u00a0referee<\/h3>\n<p>Strip away the jargon and every card payment involves the same\u00a0cast:<\/p>\n<p><strong>Cardholder:<\/strong> the person tapping their\u00a0card<strong>Merchant:<\/strong> the business getting\u00a0paid<strong>Issuer:<\/strong> the bank that gave the customer the\u00a0card<strong>Acquirer:<\/strong> the bank on the merchant\u2019s side<strong>Networks:<\/strong> Visa and Mastercard, who write the\u00a0rules<\/p>\n<p>ISOs and PayFacs squeeze in on the merchant side. What separates them is who holds the license, who absorbs losses, and who owns the customer.<\/p>\n<h3>The acquirer: holder of the\u00a0keys<\/h3>\n<p>An acquirer is a licensed bank with direct membership in the card networks. It vets merchants, settles funds, and takes the fall when things break. If a merchant disappears owing thousands in chargebacks, the acquirer gets the\u00a0call.<\/p>\n<p>Going direct gets you the cheapest rates, but only at serious volume. Getting there means capital requirements, PCI DSS audits, and onboarding that can take weeks. Most small businesses never talk to one. Honestly, most wouldn\u2019t enjoy\u00a0it.<\/p>\n<h3>The ISO: the salesperson<\/h3>\n<p>An Independent Sales Organization resells an acquirer\u2019s services. It finds merchants, signs them up, and collects a slice of their processing fees for as long as they stay. It doesn\u2019t hold funds and has no license of its\u00a0own.<\/p>\n<p>In practice that\u00a0means:<\/p>\n<p>Each merchant signs its own account with the\u00a0acquirerEvery business is underwritten individuallySupport is personal, often local, and often includes terminalsYou get little say over pricing, tech, or payout\u00a0speed<\/p>\n<p>This suits restaurants, clinics and corner shops, where a person answering the phone beats a well-documented API. Unglamorous. Effective.<\/p>\n<h3>The PayFac: the platform\u00a0play<\/h3>\n<p>A payment facilitator is a merchant of record that brings many small sellers under one master merchant account. Stripe and Square made the model famous. Instead of forms and a two-week wait, a PayFac can approve a seller in minutes using automated checks.<\/p>\n<p>The price of that speed is responsibility. Fraud, chargebacks and sub-merchant compliance land on the PayFac first, and the acquirer holds it accountable. What you get back: control over checkout, pricing and payout timing, plus the customer data. For a software company, that\u2019s the\u00a0prize.<\/p>\n<h3>A mall, because analogies help<\/h3>\n<p>Think of a shopping mall. The acquirer owns the building and writes the lease rules. The ISO is the leasing agent who finds tenants and takes a commission. The PayFac is a master tenant who sublets small stalls to dozens of vendors, sets their terms, and answers to the owner when one of them causes\u00a0trouble.<\/p>\n<h3>Side by\u00a0side<\/h3>\n<p><strong>Licensing:<\/strong> the acquirer has full membership, the ISO borrows it, the PayFac operates under sponsorship<strong>Speed:<\/strong> acquirers are slow, ISOs moderate, PayFacs nearly\u00a0instant<strong>Risk:<\/strong> acquirers carry the final liability, PayFacs carry sub-merchant risk, ISOs carry the\u00a0least<strong>Best fit:<\/strong> enterprises, traditional shops, software platforms<\/p>\n<h3>Who makes money, and\u00a0how<\/h3>\n<p>Every payment has layers: interchange to the issuer, network fees, then a markup on top. Who keeps that markup depends on the\u00a0model.<\/p>\n<p>Acquirers earn thin margins on enormous\u00a0volumeISOs earn residuals, a monthly share of each merchant\u2019s fees, plus equipment salesPayFacs keep the spread between the wholesale rate they pay and the flat rate they\u00a0charge<\/p>\n<p>That spread explains why so many software companies want in. Payments can turn a subscription product into a second business.<\/p>\n<h3>So which one do you\u00a0pick?<\/h3>\n<p>There\u2019s no universal answer, but there are patterns.<\/p>\n<p><strong>Choose an ISO<\/strong> if you run a traditional business and want a quick start, real human support, and hardware included.<strong>Become a PayFac<\/strong> if you run a platform or marketplace and want smooth onboarding, branded checkout, and payments\u00a0revenue.<strong>Go direct to an acquirer<\/strong> if your volume is huge and your team can handle risk, compliance and integration alone.<\/p>\n<h3>Where people trip\u00a0up<\/h3>\n<p>The same mistakes keep showing up, and most are avoidable:<\/p>\n<p><strong>Underestimating compliance.<\/strong> PayFacs deal with PCI DSS, KYC and constant monitoring. None of it is optional.<strong>Shrugging off chargebacks.<\/strong> Disputes hit the PayFac first, and a high ratio can end the acquirer relationship overnight.<strong>Skimming the contract.<\/strong> ISO agreements sometimes hide early termination fees and long lock-ins.<strong>Building too soon.<\/strong> Full PayFac status costs real money, and plenty of startups aren\u2019t\u00a0ready.<\/p>\n<h3>The middle\u00a0path<\/h3>\n<p>Which brings us back to Dev. He doesn\u2019t need to become a PayFac yet. He needs PayFac-as-a-Service: PayFac-style onboarding while a partner handles underwriting, compliance and\u00a0risk.<\/p>\n<p>He launches faster, keeps a good chunk of the revenue, and can graduate to full PayFac status once volume justifies the\u00a0bill.<\/p>\n<h3>Questions to ask before you\u00a0sign<\/h3>\n<p>Before committing to anything, sit down with\u00a0these:<\/p>\n<p>How many merchants will you onboard, and how\u00a0fast?Do you need control over checkout and\u00a0payouts?Can your team realistically handle fraud and compliance?Is payments revenue central to your plan, or a\u00a0bonus?What\u2019s your budget and launch timeline?<\/p>\n<h3>Where this is\u00a0heading<\/h3>\n<p>The boundaries are blurring. Big acquirers now sell embedded payments, ISOs are bolting on software, and PayFacs are chasing direct bank relationships. Card networks keep tightening sub-merchant onboarding rules too, so strong risk controls matter more every\u00a0year.<\/p>\n<h3>Bottom line<\/h3>\n<p>These three aren\u2019t rivals so much as layers of one stack. The acquirer builds the rails, the ISO sells access, and the PayFac wraps it all into something people actually enjoy\u00a0using.<\/p>\n<p>Match the model to your stage. New and small? Keep it simple. Payments central to revenue? Push for control. Massive volume? Talk to an acquirer directly. Get that call right early and payments stop being a headache.<\/p>\n<p><a href=\"https:\/\/medium.com\/coinmonks\/iso-vs-payfac-vs-acquirer-who-actually-gets-paid-when-you-swipe-3934d207a035\">ISO vs PayFac vs Acquirer: Who Actually Gets Paid When You Swipe?<\/a> was originally published in <a href=\"https:\/\/medium.com\/coinmonks\">Coinmonks<\/a> on Medium, where people are continuing the conversation by highlighting and responding to this story.<\/p>","protected":false},"excerpt":{"rendered":"<p>Three payment models that look identical on a slide deck and feel nothing alike in real\u00a0life A founder I\u2019ll call Dev launches a small booking app for salons. In week one, a customer pays for a haircut. Dev checks his dashboard, sees the money, and assumes payments are basically solved. Then a chargeback arrives. Then [&hellip;]<\/p>\n","protected":false},"author":0,"featured_media":233120,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-233119","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-interesting"],"_links":{"self":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts\/233119"}],"collection":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=233119"}],"version-history":[{"count":0,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts\/233119\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/media\/233120"}],"wp:attachment":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=233119"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=233119"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=233119"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}