# Software as the Future of Payments Distribution Notes

**Published by:** [jelca thinks](https://paragraph.com/@jess/)
**Published on:** 2022-02-08
**Categories:** payments
**URL:** https://paragraph.com/@jess/software-future-payments

## Content

Bain Capital - Software as the Future of Payments DistributionEarly DaysLegacy merchant acquirers e.g. Chase, BoA, Wells, Elavon / US Bank sold directly to large merchants like Best BuyThese merchant acquirers needed better distribution channelsThe rise of ISOs and ISVsISOs do not integrate with software but are more SME facing and on the streets sellingFor example they'd sell a merchant a POS system then intro them to a payment processor like Worldpay to set up the back endMerchants have little software overlaying it like data analytics, only can accept paymentsMerchants need to be underwritten by a bank acquirer. Took a long ass time and often was difficult due to documentation requirementsFirst Wave of Integrated PaymentsMaybe ISOs aren't the best. Let's look at software company-led sales channels insteadPayments embedded in software sold to merchants. Essentially pre-packaged.Merchants get a POS system with a bunch of integrations such as CRM, analytics, etc.The tech company would refer the merchant back to Worldpay and then an acquirer to be underwrittenA lot of consolidation occurred - Global Payments acquired Accelerated Payment Technologies in 2012 and Vantiv/Worldpay acquired Mercury Payments in 2016 for $1.65bn. Over $10bn was spent on acquisitions for companies in this space to boost integrated payments abilities.Integrated payments is important because you can own the payments experience at a lower CAC and increase customer stickiness as you cross and up sell. Onboarding is sleeker and implementation is easier.Vertically Driven Payments SoftwareRise of Shopify, Mindbody, LightspeedThese softwares becoming commoditized? Becoming a price war? Need to keep layering on more value added services such as analytics, campaign marketing, etc. Greater focus on value way beyond just payments. This is why Square is so expensive and can charge an MDR (merchant discount rate) that is more expensive than industry averageMDRs cover interchange to issuer, network fees to the network, and merchant acquirer spreadNew revenue models such as Lightspeed monetizing through referrals (company refers merchants to third party payment processors to get a share of payment processing economics). Merchants can choose to use a Lightspeed partner basically and Lightspeed gets % based referral feesHuge benefits when merchants scale - EBITDA margins on average of 70% (adj net rev)Value Driven OfferingsIntegrations suck. There are a lot of them. Offer a fully baked end to end solution in a vertical specific manner.Examples: MindBody for fitness, spa and salon. They also have dynamic pricing to price classes. Lightspeed offers ingredient and order management, menu and floor managementSeamless Merchant OnboardingBefore, software providers set up an offering for the merchant then referred the merchant to a payments provider to set up acceptance. The process sucked - it is easier to just purchase payments as part of a software package with integrations in it already. Software providers become the one stop shop.This also makes it easier for merchants to get underwritten. Onboarding became instant. Square was a pioneer in the space. They popularized the payfac model to underwrite small merchantsThis is also great for software companies because they will have visibility into merchant payment activity, inventory fluctuations, marketing campaigns, etc. Basically data is king. Vertical players know their market very deeply and can help underwrite them better too.Ease of Implementation and UseThere are so many vertical specific payments companies now, it is easy to find one that can serve you!3 Options for Software Companies to Get Into this SpaceISO ModelCompany refers merchant customers to payments processorMindBody is an ISV that refers salons and spas to Total System ServicesMindBody is NOT involved in underwriting and compliance aka funds flows BUT this means they can't fully monetize their transactions hence they take a referral fee instead of % of tx volumeISVs do not have end to end control of the payments experiencePartner with a PayfacStripe, Adyen, Braintree, SquareSoftware company can capture more payment economics and own the payment experience more.Merchants can accept payments instantly.Because you are foregoing building a payfac, you better pay up! If you scale up in GMV a lot, end users will bear the fees.You are limited and reliant on the payfac you partner withBecome a PayfacSoftware company opens a merchant bank account and gets a merchant ID (MID) to acquire and aggregate payments for their submerchants. Submerchants do not need to register their own MIDs because they get aggregatedThe software company is thus responsible for underwriting and acquiring all these submerchants. The software company better reduce the complexity of setting up payments!Good for those who have access to a broader pool of merchants e.g. low sales volume merchantsThis allows software companies to monetize their submerchants' transactions and create differentiated services aka stickiness.They also get the biggest chunk of payments economicsCons: Must control who they admit (onboarding), meet KYC/AML standards, monitor high risk activity and fraud, PCI complianceThis is not easy! Huge time and monetary investment.Companies like Finix, Payrix, Infinicept provide middleware to help software companies capture more payfac upside without all the time investment.

## Publication Information

- [jelca thinks](https://paragraph.com/@jess/): Publication homepage
- [All Posts](https://paragraph.com/@jess/): More posts from this publication
- [RSS Feed](https://api.paragraph.com/blogs/rss/@jess): Subscribe to updates

## Optional

- [Collect as NFT](https://paragraph.com/@jess/software-future-payments): Support the author by collecting this post
- [View Collectors](https://paragraph.com/@jess/software-future-payments/collectors): See who has collected this post