6 Payment Providers to Consider for Vertical SaaS

0
18

A home service technician and homeowner check payment details after an appointment.

A contractor may collect a deposit before anyone visits the job site. An appointment business may save a card when a customer books, then charge the balance after the service. Software for either business has to connect the payment to work that is still underway.

A payment screen suited to a one-time sale may not handle repeat charges or payments in the field. The provider also has to support merchants when they need help with their accounts. To choose a provider for your vertical SaaS app, look at how your merchants earn their money and check which businesses the provider will approve.

Merchant payments versus SaaS subscription fees

Billing merchants for your app differs from helping hundreds of separate businesses take payments from their own customers. For the second service, you need to review each merchant and give it access to the right records. You also need to resolve payment problems while keeping each business’s money and details separate from those of the others.

1. Finix fits platforms that need merchant-specific review

Finix offers payment and underwriting tools for software businesses. You can use them to review merchants based on how their businesses differ. Hosted forms or an API let merchants apply. The Merchant Underwriting product supports custom scoring and decision rules, with a way to handle cases that need more review. It can also work with other payment providers.

Finix is a useful starting point if the businesses using your app work in the same industry but earn money in different ways. What a business sells or how it takes payment may mean its application needs a closer look.

Check which merchants can join. Finix’s US platform policy prohibits some categories that its direct-merchant policy only restricts, including card-not-present alcohol sales. Being in a broad industry does not mean a merchant is approved. Give Finix the specific merchant categories and sales methods before making promises about signup.

2. Stripe Connect gives platforms several payment arrangements

Stripe Connect offers several ways to handle payments for separate merchants. With direct charges, merchants sell to their own customers, and your business can collect an application fee. Other charge models let you send funds to one or more connected accounts.

Choose the model based on how merchants use your app. A simple charge for a service and a sale involving several sellers may need different ways to handle the money. With Connect, merchants can also sign up and manage their accounts inside your app. They can see payments, refunds and disputes. Terminal lets them take payments in person where they meet its regional rules.

The charge model changes which balance covers fees and the costs of refunds or chargebacks. Product and finance staff need to agree on who pays before engineers build the payment flow. The simplest example in the docs may not match your team’s duties.

3. Rainforest suits a vertical SaaS product team

Rainforest focuses on vertical SaaS. It offers ready-made screens for merchant signup and payments, with reports and chargeback tools. You can embed those screens or build through its APIs, combining both approaches where needed. This lets you add payment tools to the steps merchants know from using your app.

Rainforest supports card and ACH payments. Merchants can also take payments in person and save payment methods for later charges. If your app serves businesses working in the field, check how Rainforest handles a first payment followed by a later charge.

Rainforest lets you set merchant prices using a buy-rate model without a revenue split. Its risk-management fee depends on your platform’s risk, and the headline calculator leaves that fee out. Compare the full quote for your mix of merchants. The published charge per payment is only part of the cost.

4. Adyen for Platforms supports online and in-person payments

Adyen for Platforms lets merchants take payments online and in person under your brand. Merchants can supply their business details through hosted signup or ready-made screens. You can also build your own form.

Adyen supports merchant balance accounts and fund splits. You can choose managed or custom payouts when paying merchants. Review those controls if you need to pay several parties for a service, or if merchants need to see fees and payouts alongside their daily work.

The details a merchant must provide depend on its country and legal structure. Approval gives it access to specific functions, not every feature. Each function also has its own geographic limits. Adyen supports platform payouts in Australia, the EU, the UK and the US. Taking payments from buyers in many countries does not mean you can sign up merchants in all of them.

5. Tilled supports platforms serving US and Canadian merchants

Tilled lets you add merchant payments to your app in the US and Canada, with Canadian French language support. You can prefill merchant applications and put your brand on payment management screens and emails about payments or accounts. This may suit customers who expect payment messages and account screens to match the rest of your app.

Tilled supports recurring billing, payment links, payments taken in person and updates to stored cards. Reports connect payments with payouts and fees. A user can switch among several merchant accounts. Review these features if your customers serve repeat buyers or run more than one legal business.

Standard platform plans have fixed monthly SaaS fees. Work out those costs based on how many merchants are likely to start using payments, rather than your whole customer list. Custom domains and custom reporting are part of the Enterprise tier. Include those needs when asking for a quote.

6. Fiska fits software with connected payment channels

Fiska lets you add online and in-person payments through one integration. You can put your brand on terminal displays and manage the devices remotely. APIs and code snippets let you add online payment pages to your app. You can also embed merchant signup under your brand.

Its shared token system supports sales and refunds across channels. This helps merchants who start a sale online and continue working with the customer in person. You control the prices merchants pay within an interchange-based profit-sharing partnership.

Your team answers merchants’ first requests for help, with Fiska specialists available for cases you pass on. Agree on which questions your staff will answer and how to refer difficult cases to Fiska. Check whether merchants must repeat any details when another person takes over.

Review business models within the same vertical

A list of industries gives the provider only part of the picture. A home-services app might serve businesses that get paid after a repair and others that collect large deposits for future work. Explain those differences in the first review.

Build a sample merchant list with each legal business, location, services sold, average bill and usual gap between payment and delivery. Include customers whose business falls outside the norm. A provider may serve most of your customers but leave a sizable group out. Finding that group before you build gives your product team time to decide how to serve them.

Separate appointment payments from billing the software user

Check what each recurring feature does. A SaaS subscription bills the merchant for software. A recurring customer payment bills that merchant’s customer for an ongoing service. Each service has different people paying and receiving money. Cancellation requests come from different people too.

Ask each provider on your shortlist to show you the second type of payment with a normal merchant example. Check how the payment method is saved and who may charge it later. Have the provider show how merchants see failed payments. If your app handles bookings, check what happens to billing when an appointment changes or gets canceled. Staff should not have to fix a separate billing task by hand.

Help staff resolve merchants’ payment problems

Merchants will ask for help finding a refund or explaining why a deposit differs from their sales. They may ask your help desk even when a provider handles processing.

Check what staff can see without asking an engineer to find records. They should be able to find the merchant and payment, then see who needs to act next. Set a clear way to pass on applications that need more details and problems your team cannot solve. Include this work in staffing plans before assuming your current support team can take on a payments program.

Compare providers using sample merchant accounts

Take a small sample of merchants through the final talks with providers. Include a business with routine payments and one with delayed delivery. A merchant with demanding channel or regional requirements will help you assess those limits too. Have each provider explain how it would handle the sample accounts.

Get written confirmation of which merchants qualify and the functions each can use. Record what your team must do when a payment becomes a problem. This gives you a firmer basis for choosing than a broad claim about serving your industry. It also gives your launch team a realistic first group of merchants to invite.