Category: Industry Insights

How ServiceTitan Drove Unprecedented Customer Adoption and Growth with Embedded Payments

Author: Ershad Jamil former Chief Growth Officer of ServiceTitan

From the initial wave of businesses collecting payments through e-commerce sites to the current approach to embed payments into software platforms, if you’re leading a Vertical Software as a Service business (VSaaS), there’s no doubt you’ve started to think about the role payments play across your entire business lifecycle.  In fact, I was in the same shoes in 2015 when I began exploring payments for ServiceTitan.

In 2015, ServiceTitan, an all in-one-platform for home contractors, referred their customers seeking payments to a large payments processor.  This integration required customers  to onboard through the third party payment processor – leaving a disjointed customer experience in which the customer would bounce from the ServiceTitan app to the payment provider.

In addition, the ServiceTitan customer teams were focused on leading the software implementation, not the payment integration.  This led to onboarding bottlenecks for customers using the payment integration. Most of the customers did not have team members dedicated to payments and they struggled to understand why certain documentation, especially sensitive financial statements from contractors, was necessary.  This back and forth could lead to 2-3 month gaps in the onboarding – with little visibility between ServiceTitan and the payments provider.

While only 10-20% of ServiceTitan customers were using the payments integration, I believed that more customers would leverage payments—especially if the payments experience looked a little different. When surveying customers about their experience with the integration, they shared frustrations with the sales and onboarding process. Additionally, the approach to sales, which emphasized “match or beat your pricing,” often resulted in lower take rates for ServiceTitan, even though the product was delivering significant value that exceeded the quoted pricing as a VSaaS business, I knew it was critical to streamline business operations for our customers—and addressing the friction in our payments integration strategy was a key opportunity. By exploring different levers in payments—such as fully embedding payments into our platform and structuring pricing to align better with customer needs—embedded payments could become just as critical to our software and as much of a revenue driver as other core platform features. Allowing home service contractors to take payments directly through a web or mobile app would deliver a significant value add.

In review of the business case with ServiceTitan’s co-founders, head of finance, head of operations and developers, three primary benefits for why to embed payments came to the forefront:

  1. Improved customer experience – Our customers, home and commercial contractors, would be able to accept their customers payments via a web or mobile app, reconcile invoices & payments, view data/analytics via reporting, and more – allowing payments to be a fully integrated experience through the ServiceTitan platform. Not only would the  ‘all in one solution’ provide a better experience for the customer, but also a great opportunity to reduce onboarding time and friction as well as improve retention for our product.
  2. Simplified end customer experience – We understood that if the end customer (a homeowner, for example) experiences a great payment experience (i.e., tapping your phone via Apple Pay, taking a picture of a check via a mobile phone, etc.), it reflects well on the business (contractor) and in the end, reflects well on the software that business is using. Bringing delight throughout the entire process would increase utilization and satisfaction.
  3. Revenue expansion – Taking on more of the work to sell, onboard and support customers via our own integration with a payments partner, we could take a larger revenue share and offer flexible pricing structures that meet customers’ business models.

By 2017, we launched ServiceTitan Payments and it provided a meaningful impact to the company from a revenue and retention perspective.  Within three years, the vast majority of ServiceTitan customers were using the embedded payments offering.

It should be no surprise that other major VSaaS platforms like Mindbody and Toast have also launched embedded payments. There are also so many features that a VSaaS business could benefit from in addition to embedded payments like storing credit cards on file for recurring billing, ability to process a refund in the app, eliminating manual reconciliation, to help their customers streamline their operations.  To increase product stickiness and long term growth, embedded payments is a great starting point.

With support from Payabli I’m going to write a series of articles to help other vSaaS operators to think strategically to optimize their Payments business and avoid many of the pitfalls I encountered along my journey in building ServiceTitan Payments. Stay tuned for more content on driving payments adoption, maximizing payments margin potential, bundling additional fintech products and more.

View the full conversation with Joseph Elias Phillips and I below 👇

Breaking Down PCI DSS 4.0 Requirements: How SaaS Platforms Can Achieve Compliance by the March 2025 Deadline

Credit card theft and misuse are growing in both volume and sophistication. Recent reports suggest that cases of credit card fraud have doubled in volume in the last five years.

In response to the shifting nature of e-commerce, the Payment Card Industry Security Standards Council (PCI SSC) announced the PCI Data Security Standard (DSS) 4.0 in March 2022.

The council gave businesses a three-year deadline to prepare for and implement the new standard. As March 2025 grows closer, SaaS platforms must comply with a raft of new PCI DSS 4.0 requirements or face stiff consequences.

What is PCI DSS 4.0?

PCI DSS 4.0 is the latest iteration of the Payment Card Industry Data Security Standard, an updated set of requirements businesses must follow when handling credit card information.

The standard aims to protect customers’ payment data from theft and fraud and ensures businesses that accept, process, store, or transmit credit card information maintain a safe, secure environment.

How does PCI DSS 4.0 affect SaaS providers?

The new PCI DSS 4.0 requirements include changes that directly impact SaaS providers. Let’s break down some of the reasons below.

Expanded scope: The PCI DSS 3.2.1 provided rulings for payment processors. However, the 4.0 version has broadened its scope to include any SaaS providers that store, process, or transmit cardholder data. Even if you don’t directly process payments, you must comply with the new standards. Within the expanded scope, additional cardholder PII info is required.

More robust password requirements: Access to cardholder data environments (CDEs) now requires multi-factor authentication. These changes affect both remote and onsite teams. Password complexity requirements have also become more stringent.

You can read more about the different authentication options in this SSC supplement.

Stronger security controls: While much depends on your type of business and the volume of transactions you process, mechanisms like DMARC, SPF, and DKIM are required to protect against phishing attacks as part of the PCI DSS assessment. Additionally, businesses must commit to testing their security systems more frequently.

Risk assessment: The new standard also mandates that SaaS providers must perform regular risk assessments and proactively identify potential vulnerabilities. What’s more, the new regulations also require businesses to outline and apply security controls to mitigate or remedy adverse findings of these risk assessments.

Customization: While the core 12 PCI DSS requirements are non-negotiable, there is room for a more customized approach to suit the needs of their specific risk environment.

Implications for SaaS providers

Meeting the new PCI DSS 4.0 standards will have several implications for SaaS businesses. Some of the topline impacts include:

  • Increased compliance costs: Meeting these new requirements means many SaaS providers will need to invest in new tech, personnel, and processes. These investments will result in a rise in compliance costs for many businesses.
  • More security monitoring: The standards’ increased emphasis on monitoring and assessing risks means SaaS teams will need to budget for more time on security processes.
  • Workflow adjustments: Stronger authentication and security controls could cause disruptions in existing workflow processes for many SaaS providers.
  • User experience: On the user side, some SaaS end users might face extra steps when paying for products. However, disruptions should be minimal and more than justifiable when weighted against security benefits.
  • Third-party risk management: SaaS providers must also ensure their third-party vendors or partners comply with PCI DSS 4.0. That means tighter contractual agreements, more ongoing monitoring, and enhanced due diligence in vendor selection and assessments.

What happens if SaaS businesses don’t comply with PCI DSS 4.0?

Non-compliance with PCI DSS 4.0 is not an option. Some of the penalties and adverse effects that could result from ignoring the March 2025 deadline are detailed below.

Fines: SaaS companies that fail to comply with PCI DSS 4.0 could face stiff monthly fines of between $5,000 and $10,000. The precise amount depends on various factors, such as non-compliance severity, business size, and any holdups in remedying the situations.

Business disruptions: Failure to comply with the new standards can lead to catastrophic payment processing bans for SaaS businesses. Additionally, non-adherence could result in companies being placed on the MATCH List or Terminated Merchant File (TMF) and even the potential loss of contracts needed to continue accepting card payments.

Legal liabilities: Failure to comply could open up SaaS businesses to lawsuits from affected parties, defense costs, and settlements. Additionally, it could increase the likelihood of audits from bodies such as the FTC, which could result in additional financial penalties.

Data breaches: The new regulations were designed to reduce the likelihood and effect of data breaches. Organizations that do not meet these standards run the risk of expensive and reputation-shredding data breaches and loss of trust among their users.

Lost access to payment processing: While this downside is limited to the worst infractions, SaaS companies that do not comply with PCI DSS 4.0 could lose access to payment processing, which would constitute an existential risk.

Additionally, merchants operating under software platforms that fail to comply with PCI DSS 4.0 face significant financial, operational, and reputational risks similar to those outlined above.

How can SaaS providers prepare for the March 2025 deadline?

With the March 2025 deadline on the horizon, SaaS teams need to take action before it’s too late. Here are some actions that can ensure you’re ready.

  • Look at the PCI DSS 4.0 requirements and compare them to your current security practices. Identify what you must do to improve your security with these new standards.
  • Perform a comprehensive risk assessment to pinpoint your vulnerabilities and shortlist tasks for remediation.
  • Right now, PCI DSS 4.0 standards are thought of as best practices. However, implementing them now will ensure you’re ready for March 2025.
  • Update your security policies, procedures, and practices to align with PCI DSS 4.0.
  • Ensure that any third-party vendors and partners are compliant.
  • Ask a Qualified Security Assessor to audit your current setup and make recommendations toward compliance.

How Payabli Can Help?

Partnering with an experienced and reputable payment service provider like Payabli can help you navigate the complexities of PCI DSS 4.0 compliance. Here is how we can support your business.

  • Payabli handles the storage, processing, and transmission of cardholder data. SaaS businesses can significantly reduce their exposure to PCI DSS 4.0 compliance standards and broader security risks by allowing us to manage their payments.
  • Payabli replaces sensitive cardholder data with tokens, adding an extra security layer and mitigating data breaches.
  • Our payment processing infrastructure is already PCI DSS 4.0 compliant as well as featuring encryption, firewalls, intrusion detection, and regular security audits. We stay up to date on emerging security threats, best practices, and regulatory changes, allowing SaaS providers to remain compliant with PCI DSS 4.0.
  • Finally, and perhaps most importantly, we have a team of payment experts with deep experience in implementing and maintaining PCI DSS 4.0 compliance. Payabli can provide personalized guidance on how your SaaS organization can meet PCI DSS 4.0 standards, helping you understand and interpret the requirements and outline areas for improvement.

Through a mix of security document preparation, self-assessment questionnaires, and audit support, we’ll ensure your SaaS business meets PCI DSS 4.0 standards and avoids fines, security breaches, and loss of payment processing associated with non-compliance. In addition, we offer ongoing PCI support, helping to ease the burden of managing and maintaining compliance. This not only protects your SaaS business but also enhances your end-user customer experience by safeguarding their sensitive data.

Reach out today to see how we can help.

 

Payment Rails: What Are They, Their Evolution, and How They Work

Commerce has evolved over millennia, and today, online businesses depend on electronic transactions to drive their operations. Customers expect the convenience of instant payments, which, while seeming magical, rely on complex systems behind the scenes. This article will explain what payment rails are, why they are important, and how they work to move money securely.

What Are Payment Rails?

Let’s start from the beginning – what exactly are payment rails? As the name implies, payment rails are similar to the physical rails that trains run on to transport goods over land. But instead of carrying physical items, payment rails transport money and data. Payment rails are the infrastructure and technology platforms that enable the movement of funds between payer and payee, facilitating transactions in the financial ecosystem. Think of them as the “tracks” on which payment information travels, similar to how physical railroads move goods and people.

These exchanges can happen between banks, businesses, and individuals. As such, they have become a crucial component of the financial ecosystem.

A Brief History of Payment Rails (1950-2010s)

You could argue that payment rails started with the first checks. These paper documents were like early versions of electronic payments and allowed customers to pay merchants without having the legal tender on hand. But it wasn’t until computers and electronic networks came along that payment rails took off.

In 1958, Bank of America introduced the first general-purpose credit card, the “BankAmericard,” marking the start of “card rails” and shifting payments from cash and checks to a credit-based system. This innovation evolved when BankAmericard became Visa in 1976, creating a global network that enabled cross-border payments and connected millions of merchants and cardholders.

About ten years after the launch of the BankAmericard, Automatic Clearing Houses (ACH) were introduced. ACH was developed as a solution to the growing need for efficient processing of large volumes of paper checks and electronic payments. The ACH network provided a way to move money between bank accounts electronically, facilitating transactions like direct deposit of payroll and automatic bill payments.

In 1978, SWIFT (Society for Worldwide Interbank Financial Telecommunication) revolutionized international finance by providing a standardized, secure messaging system for cross-border transactions. Before SWIFT, international payments were slow, costly, and error-prone due to the lack of a common protocol.

Then came the Internet, which completely transformed the payments landscape once again. The rise of the Internet in the late 1990s and early 2000s led to the emergence of Peer-to-Peer (P2P) networks, with PayPal being one of the most prominent examples. PayPal allows people to send and receive money digitally, bypassing traditional banks and payment methods.

Even traditional payment methods like checks have adapted to the digital age. With the advent of mobile banking, checks have received a modern update through mobile deposit features. Now, instead of visiting a bank or ATM to deposit a check, people can simply snap a photo of it with their smartphone and deposit it from anywhere.

In recent years, the development of real-time payments (RTP) has been a significant milestone in the U.S. payments landscape. Launched in 2017 by The Clearing House, RTP enables instantaneous transfers of funds between bank accounts, 24/7/365. Unlike traditional payment methods that could take days to process, RTP allows recipients to access funds immediately, even on weekends and holidays.

New payment technologies continue to evolve, with innovations like blockchain, digital wallets, contactless payments, biometric authentication, and AI pushing the boundaries of what’s possible. These advancements make transactions faster, safer, and more seamless, as the payments industry adapts to growing consumer expectations and technological capabilities in a digital-first world.

How Payment Rails Work

Payments can be categorized as push, pull, or a combination of both. Push payments offer control and are ideal for instant transfers, while pull payments are convenient for recurring bills and purchases. Systems like ACH provide versatile solutions for various business and personal finance needs.

  • Push Payments: In a push payment, the payer initiates the transaction by sending money directly to the recipient. A great example of this is Real-Time Payments (RTP). With RTP, the payer actively “pushes” funds from their bank account to the recipient’s account. This type of payment is usually instant, and the recipient has immediate access to the funds, even on weekends or holidays.
  • Pull Payments: On the other hand, pull payments work the opposite way. Here, the recipient or merchant initiates the transaction by requesting funds from the payer’s account. Credit cards are a common example of pull payments. When you make a purchase with a credit card, the merchant requests the amount owed from your credit card issuer, which then pulls the funds from your line of credit to pay the merchant.
  • Combination of Push and Pull: Some payment systems can operate as either a push or pull, or even a combination of both, depending on how they’re used. ACH (Automated Clearing House) is a great example of this flexibility. ACH can function as a push payment when you, for instance, initiate a direct deposit to pay your employees—sending money from your account to theirs. It can also work as a pull payment when a utility company automatically withdraws your bill payment from your account each month.

The Formula for Processing Payments

While different payment rails might use slightly different methods, most follow a similar process. Here are the main steps:

  • Initiation: The payment process starts when the payer authorizes the transfer of funds. That could mean swiping a debit card, signing a check, initiating a recurring payment, or logging into an online bank account and entering payment details.
  • Payment Creation: Once the payer approves the payment, a financial message with relevant transaction data is generated. It includes the amount to be paid, account numbers, and other information required to complete the transfer.
  • Processing: The payment message enters the payment network, which could be a card network like Visa or Mastercard or an ACH network. Here, a series of steps and checks ensure the transaction is valid and authorized.
  • Confirmation: This step occurs as soon as funds are guaranteed and the transaction is authorized. Confirmation messages are returned to the payer, payee, and other relevant parties, serving as proof that the payment went through.
  • Settlement & Reconciliation: Finally, the actual transfer of money occurs. This settlement process can happen instantly or not, depending on the type of payment rail. Once settled, accounts are reconciled and updated accordingly.

Types of Payment Rails

Now that we know what payment rails are, let’s look at the different types. We can group payment rails based on how they handle transactions, how fast they work, or what technology they use. Here are some of the leading payment rail systems in use today:

Automatic Clearing Houses (ACH)

ACH is a system that processes electronic payments in batches. It’s mainly used for direct paycheck deposits and automatic bill payments. In the US, ACH is overseen by NACHA (National Automated Clearing House Association).

One of the great things about ACH is that it’s affordable and perfect for recurring payments. If your paycheck gets deposited straight into your bank account every month, that’s probably through ACH. If you’re in the SaaS business and deal with ACH, check out our blog to learn more about ACH and ACH returns, how they work, and why they’re important.

Card Networks

Card networks like Visa, Mastercard, American Express, and Discover manage the infrastructure for secure and efficient card transactions. The process starts when a purchase is initiated, with transaction data sent through the network connecting the merchant’s bank (acquirer) and the cardholder’s bank (issuer). The issuer authorizes the transaction, verifying funds or credit, and once approved, the transaction is processed, transferring funds from the cardholder’s account to the merchant’s account.

Card Acceptance

Merchants can accept credit and debit cards as payment for invoices, goods, and services, expanding their customer base and streamlining their payment processes. Card payments can be processed online, by mail, over the phone, or using a physical point-of-sale device. Card details can also be stored for recurring payments, ensuring seamless transactions for subscription-based services or repeat purchases.

Additionally, merchants can leverage digital wallets to facilitate card payments, enhancing convenience for customers. Digital wallets enhance the security of card transactions by tokenizing and protecting card information. When a card is stored in a wallet, it is converted into a temporary virtual card at the time of purchase. This tokenization process ensures that the actual card details are never exposed during the transaction, reducing the risk of fraud.

Card Issuance

Card issuance allows individuals to obtain cards for making payments in person, online, or via mail/telephone orders. These cards come in various forms—credit, debit, prepaid, and gift cards—each serving different financial needs. Issued cards can be either virtual or physical, offering flexibility in how they are used. Additionally, cardholders benefit from purchase protection features, such as the ability to dispute unauthorized transactions, ensuring a fair and secure payment experience.

Interac

Since 1984, Interac has been Canada’s predominant payment network, linking financial institutions to process debit card payments at point-of-sale terminals and online. It also enables peer-to-peer money transfers through Interac e-Transfer, allowing account holders to send money using only an email address or mobile number, with SMS payments becoming particularly popular.

Domestic Wires

Domestic wires are a type of payment rail used to transfer money quickly and securely, typically for large-ticket items or transactions within a country. These transfers are instantaneous, making them ideal for situations where speed is crucial, such as high-value purchases or urgent payments. By leveraging established financial networks, domestic wires ensure that funds move efficiently between accounts, providing a reliable option for significant financial transactions.

Real-Time Payments and FedNow

This system, introduced by The Clearing House in 2017, revolutionizes payment processing by enabling real-time transactions with immediate fund availability, even on weekends and holidays. When a payer initiates a transaction through their bank’s online platform or app, funds are instantly transferred via the RTP network, allowing the recipient immediate access. Unlike traditional methods, RTP transactions are final and irrevocable, providing instant confirmation to both parties.

RTP Push and Requests for Payment

RTPs are initiated as a “push” of funds, meaning the payer actively sends money to the recipient, with no way to directly “pull” or debit funds from a payer’s account. Instead, businesses use a “Request for Payment” (RFP), which the payer must approve to process the payment. This method enhances security by ensuring payments require the payer’s explicit consent. RTPs provide instant access to funds, even on weekends.

FedNow

FedNow, an upcoming real-time payment service from the Federal Reserve, aims to enable instant transactions between banks 24/7/365. It will expand real-time payment access across the financial system, especially for smaller banks and credit unions, enhancing speed, efficiency, and accessibility for U.S. payments.

Payment Rails for SaaS Platforms

At Payabli, we like to say, “If you’re a software company, you’re a payment company.”

Every business, including SaaS companies, must handle payments and manage their entire lifecycle, from initiation to settlement. This includes processing sales, subscriptions, and paying bills for services like internet and vendors. By allowing users to manage these inflows and outflows in one place, you empower them to grow their business efficiently through your platform. Partnering with Payabli offers secure, fast, and convenient tools to support this growth. Here are some benefits:

Compliance & Security

In fintech and banking, navigating financial regulations and data security standards can be complex. Payment rails streamline compliance by transmitting payments through regulated networks that adhere to strict standards. Payabli complies with PCI Security Standards to ensure cardholder data is protected and NACHA standards to safeguard ACH transactions. This ensures that all sensitive payments are securely handled and compliant with all relevant regulations.

Speed

Payments once took weeks, causing delays and frustration. Now, payment rails enable transfers within hours or minutes. Time-sensitive SaaS companies benefit from faster settlements, improving cash flow visibility and decision-making. APIs offer instant payment requests, eliminating the wait for paper checks, while real-time status updates provide near-instant notifications when payments are funded or paid.

Customer Experience

The modern consumer and business expect fast, convenient online payment experiences with multiple options, from cards to mobile wallets. Payment rails help SaaS platforms meet these expectations by enabling payments through credit cards, debit cards, ACH transfers, and mobile wallets like Apple Pay or Google Pay. They also allow for easy payment processing via hosted payment pages or embedded checkout solutions. The result is improved customer satisfaction, loyalty, and increased referrals.

The Future of Payment Rails

Predicting the future of payment technology is challenging, but payment rails are likely to evolve in three key areas. First, payment rails change with technology; the rise of the Internet brought systems like PayPal and Stripe, and blockchain could lead to more decentralized rails. Second, AI can enhance payment processing by improving fraud detection and making transactions safer. Lastly, payment rails will increasingly integrate with other services like accounting, billing, and identity verification, creating a more holistic financial experience.

Get Started With Payabli

If you’re running a SaaS or platform business, the time is now to integrate compliant payment capabilities that help you scale globally. If you don’t, you risk falling behind your competitors.

Payabli offers the next-generation payments infrastructure to help software companies quickly embed world-class payments into their platform. We cover all aspects of payments: Pay In, Pay Out, and Pay Ops (we call these the 3Ps).

Book a demo with Payabli today to see how you can enable fast, secure payment acceptance through global payment rails with just a few lines of code.

What is Payment Tokenization and How Can it Enhance Security for Your Software Business?

Security in payment transactions is crucial for software businesses, and payment tokenization offers an innovative solution to this challenge. As we mentioned in our previous blog, there are multiple types of tokenization including standard, multi-use, and network tokenization. Each can benefit a software business’s unique use case and play a crucial role in its payment strategy.

In this blog we take a step back to explore the fundamentals of payment tokenization, why it matters for software businesses, its role in safeguarding sensitive payment data, and its impact on transaction security. We also emphasize the significance of partnering with the right payment provider for seamless and secure token migrations, ensuring a smooth experience for software businesses and their customers.

What is Payment Tokenization?

Payment tokenization involves replacing sensitive payment data, such as credit card numbers or bank account details, with randomly generated tokens. These tokens are used to facilitate secure transactions without exposing actual payment information. When a customer initiates a transaction, the payment system generates a token representing that information instead of transmitting their payment information, such as credit card or bank account details. This token is then passed through the payment process and stored in your business’s payment platform for future usage. If the token were intercepted, it would be rendered ineffective for use by unauthorized individuals or hackers, because it does not contain any sensitive data. The diagram below shows how payment tokens work for software businesses and their customers, and how the payment platforms’ backend tech, such as Payabli helps facilitate the payment tokenization process.

 

 

Why Does Payment Tokenization Matter for Software Business?

For software businesses, payment tokenization enhances security by reducing the risk of data breaches and fraud. It allows them to handle payment transactions without storing sensitive data, thus minimizing liability and compliance requirements. Additionally, payment tokenization enables software businesses to offer their customers a safer and more secure payment experience, which can enhance trust and loyalty.

 

Graph from EMV Co

Exploring Different Types of Payment Tokens

There are three generally well-known forms for tokens:

Traditional Payment Tokens: These tokens are generated by replacing sensitive payment card details such as credit card numbers with a randomly generated string of characters. Many PCI-certified gateways and processors have enabled this functionality for many years. Since they are managed by your payment service provider, they tend to be the easiest and cheapest method to manage recurring payments.

Device Tokens: Device tokens are associated with specific devices, such as smartphones or smartwatches, and are used in mobile payment systems like Apple Pay, Google Pay, or Samsung Pay. Instead of using the primary account number, the payment system generates a unique token tied to the device’s secure element or software.

Network Tokens:  Unlike traditional tokens or device tokens, which are generated by merchants or payment processors, network tokens are created and managed by the card networks themselves. These tokens can be automatically updated since they are linked to the issuer and network if a change occurs.

Payment service providers like Payabli work with all three of these modalities to provide a convenient and secure payment processing experience for our software Partners.

That Seems Too Easy… What’s the Catch? And What Does This Mean For Software Businesses?

As mentioned above, traditional tokens are stored with either the gateway or processor. This means those platforms are managing the token lifecycle on behalf of customers and thus control the flow of that data. If a merchant or software provider (ISV) had to switch to a new gateway or processor, they would have to migrate all those saved tokens or even risk losing them all. Not having access to those tokens could have a massive impact on the merchant’s ability to process transactions and could affect their business operations overall.

There are two key factors that software platforms need in order to save their clients from this grief:

  1. Token Portability: When working with a provider that processes your payments, make sure you can migrate your tokens to a new provider.
  2. Token Migration: When you select a new payment service provider, it is important to ensure they can handle token migrations. Are they PCI-compliant and do they have a formal process to ingest the token information securely?

How does Payabli Do it Better?

Migrating a token may sound simple but it tends to be fraught with error. At Payabli, our team of payment experts has spent a significant amount of time normalizing data from the largest players in the payments space to ensure that migrations work smoothly for software businesses. You can see in the diagram below how the token migration process works within our technology ecosystem.

 

 

Moreover, we have automated the process, which often takes 2-3 weeks with other payment providers, down to a one-day process.

Here’s how we help facilitate the token migration process in a timely and secure manner:

  • We set secure file transfer protocol (SFTP) inboxes for our clients to deliver the information
  • We have built proprietary tools to standardize the formats from big payment service providers in the industry
  • We automatically decrypt the files and extract all the information
  • We create Payabli tokens for our merchants to be able to process transactions immediately

Conclusion

In conclusion, payment tokenization stands as a cornerstone of modern transaction security for software businesses, providing a robust shield against data breaches and unauthorized access. By adopting this technology, businesses not only safeguard sensitive payment data but also enhance the trust and confidence of their customers. Partnering with the right payment provider, such as Payabli, further amplifies these benefits through efficient token migrations and management, ensuring that the payment process remains seamless and secure. Payabli not only simplifies compliance with PCI standards but also equips businesses with the tools necessary for handling complex token migrations effectively. Therefore, embracing payment tokenization is not just about adopting new technology—it’s about investing in the future of secure, reliable, and customer-centric digital transactions.

Interested in learning more? Our team of payment experts would love to chat. Schedule a demo here.

 

ACH & ACH Returns: Everything Your SaaS Business Needs to Know

In the dynamic landscape of digital transactions, it’s crucial for businesses, especially Software as a Service (SaaS) companies, to stay abreast of various payment methods and their associated processes. One payment method that holds significant importance is Automated Clearing House (ACH) transactions.

Understanding what ACH is, how ACH works, as well as subsequent processes like ACH returns is fundamental for SaaS businesses to efficiently manage their finances and maintain customer satisfaction.

What is ACH?

ACH (Automated Clearing House) is a network in the United States for electronic payments and transfers between bank accounts, facilitating transactions such as consumer transactions, direct deposits, and bill payments. It offers a more efficient and cost-effective alternative to traditional paper-based methods like checks.

How does ACH Work?

The ACH rail supports pushing and pulling funds from a US Bank Account. This means it can be used for purchases, payroll, and pretty much any use case as long as you have an originating and receiving bank account on either side of the request. See the diagram below.

 

What is an ACH Return?

An ACH return is a process where an ACH transaction is sent back to the originating bank by the receiving bank. There are several reasons why an ACH transaction may be returned, including insufficient funds, invalid account numbers, incorrect information, or issues with the account holder’s authorization. When a transaction is returned, the funds are not transferred and the payment is considered unsuccessful. It is important for businesses to understand with ACH returns that just because you set up a payment, doesn’t mean it is completed.

  • What is the Flow of the ACH Return Once It Has Been Initiated? (AKA how do ACH returns happen?)

 

 

 

  • Once initiated and depending on the return code, a return can take 2 banking days to up to 60 calendar days to process.

Why ACH Returns Matter for SaaS Businesses?

With ACH returns, the RDFI is responsible for initiating the return entry or the return for the total amount of the original payment (partial returns are not permitted).

ACH returns not only incur fees and lose revenue for merchants but also endanger a merchant’s ability to use ACH payments. If a merchant incurs too many ACH returns, their ability to use the ACH network can be revoked altogether.

There are other implications around ACH Returns for SaaS businesses, including:

Cash Flow Management: ACH returns can disrupt cash flow for SaaS businesses, especially those operating on subscription-based models. Failed payments mean delayed revenue, which can impact budgeting, forecasting, and overall financial stability.

Customer Experience: Payment failures can result in customer dissatisfaction and churn. For SaaS businesses, where customer retention is paramount, failed transactions due to ACH returns can damage relationships and erode trust. Customers expect seamless payment experiences, and frequent returns can tarnish a company’s reputation.

Compliance and Risk Mitigation: Understanding ACH regulations and compliance requirements is crucial for SaaS businesses to mitigate risk and avoid potential penalties. Non-compliance with ACH rules can lead to fines and legal consequences. By proactively managing ACH returns and adhering to industry standards, businesses can reduce compliance risks.

Operational Efficiency: A high volume of ACH returns can strain operational resources as businesses need to investigate and resolve payment issues promptly. Implementing efficient processes and leveraging the right payment solutions for ACH management can streamline operations and reduce the administrative burden associated with returns.

How Can SaaS Businesses Address ACH Returns?

Partnering with the Right Payment Provider: Utilize a payment provider that offers robust ACH processing capabilities and built-in features for managing returns. These platforms often provide monitoring, reporting, and automated retry mechanisms to help minimize returns.

Data Verification and Validation: Implement account verification processes to ensure the accuracy of customer information before initiating ACH transactions. Validating account details can reduce the likelihood of returns due to incorrect or incomplete data.

Communication and Notification: Maintain transparent communication with customers regarding payment failures and ACH returns. Promptly notify customers of any issues and provide clear instructions for resolving payment discrepancies to mitigate dissatisfaction and preserve relationships.

Risk Assessment and Fraud Prevention: Implement risk assessment protocols to identify and mitigate potential fraud risks associated with ACH transactions. Utilize fraud detection tools and monitoring systems to detect suspicious activity and prevent unauthorized transactions.

In conclusion, ACH transactions and ACH returns play a significant role in the payment ecosystem, particularly for SaaS businesses reliant on recurring revenue streams. By understanding the fundamentals of ACH, actively managing returns, and implementing best practices for ACH processing for PayIn, SaaS companies can enhance cash flow, preserve customer relationships, and ensure compliance with regulatory requirements, ultimately driving long-term success in the digital economy. There are other implications as it relates to ACH for PayOut, which we will cover in more detail in a future blog post.

Looking to learn more about how Payabli helps SaaS companies like yours better handle ACH and ACH Returns? Schedule some time to speak with one of our Payment Experts.

 

Key Takeaways from NTEN 2024

The Payabli team had the pleasure of attending and sponsoring the NTEN (Non-Profit Technology Conference) in Portland, Oregon for the second year in a row. We interviewed our payment experts Aaron Vela and Collin Haberl who attended the event this year and met many amazing non-profit organizations and members of the NTEN community.

Can you provide a brief overview of the event and what it is all about?

NTC is the Non-Profit Technology Conference. The event brings together those in the non-profit community who are looking to make the world a better place through the skillful and equitable use of technology.

The conference encourages the non-profit community to explore the latest trends in technology and Software-as-a-Service (SaaS) tools that can help enable and streamline the management of their organizations. Many technology vendors were attending, from customer-relationship management platforms (CRMs) to Grants to Payments to Marketing agencies and web development. Overall, the conference is a great opportunity to educate yourself on the entire non-profit sector in an open and communal environment.

What were some of the highlights or memorable moments from the event this year?

Aside from sharing our core competency of “every software company is a payments company” with visitors at our booth, we also enjoyed keeping tabs on attendees’ running totals of the top Skee Ball scores as our booth was positioned right across from the activities! (440 was the highest score we witnessed, by the way).

All jokes aside, one of the key themes we encountered this year during our discussions with attendees, (especially some of the CRM providers), was the misconception about the ease of integrating payments into their platforms. Historically, both fundraising platforms and CRMs have leaned on gateway providers to handle payment processing for their charitable organizations, but increasingly we found that both donor management platforms and CRMs are intrigued and exploring options to build in-house white-labeled payment solutions in order to provide a better customer experience and monetize their payments volume. This invigorated us and brought about some exciting discussions.

We also really enjoyed the happy hour events Bonterra and Pantheon hosted during the event where we had great conversations with some prospects and consultants about Payabli and payments.

Were there any notable speakers or key themes you’d like to mention?

Yes. One of the speakers we enjoyed listening to was Amber Case, Founder of Calm Technology Institute. The topic of her presentation was around the interaction between humans and technology, which we appreciated. She reinforced the importance of keeping the mindset that the development of technology should be driven by the users and not just the developers. This allows for the feedback loop to be open versus restricted to the development.

A key theme we noticed throughout the event is how much people are concerned about data and privacy online. The non-profit, donor, and CRM platforms, especially, expressed that clients who use their software are concerned about their experience using their platform.

Payabli had a booth at the show. Can you share some feedback you received from booth visitors and attendees?

We were very excited to have a booth at the show and demo our product to attendees. Overall, we received great feedback about where their heads are at when it comes to payments. We found that a lot of attendees are particularly curious about payments and how our solution differs compared to some of the legacy providers in the space.

In a lot of our conversations, organizations expressed that they have allowed their charities to bring their own payment provider on board, which quickly turns into having to juggle multiple providers over time and naturally, less control over a singular solution.

Additionally, we were psyched to hear some of this feedback post-demo from some of the booth visitors:

“We want to start with a proof of concept solution that is “plug-and-play” before going “all in” on a payments offering.”

“The timing is perfect right now because we’re currently evaluating building our own payment solution!”

“Wow, the docs are beautifully laid out, and the level of granular detail is very nice.”

“It’s cool to see the reporting mechanisms from the top down – a bird’s eye view of our entire payment ecosystem is something we never knew we could see or have offered in a single solution.”

A lot of booth visitors also really appreciated our “meet you where you are” philosophy around Tech and Operations and our process of solving a tailored implementation through connections with our team. We were very pleased around the receptiveness of our mindset of consolidation and how we provide software Partners PayIn, PayOut, and PayOps solutions in a single unified platform. They also liked to hear about our hands-on approach from guided implementation to shared service responsibility, which brought reassurance to prospective partners looking to dip their toes in the water.

Overall it sounds like this was a very successful event not only for Payabli but also for the entire NTEN community! Can you sum up your top three takeaways?

Three takeaways, or themes that were prevalent during this year’s show were:
Education, Data, and Community.

Education: It was more apparent this year than ever that the NTEN community and attendees are there to learn. This crowd is very curious and always looking for new and innovative ways to better their organization. There were over 300 sessions for attendees to go to, which shows the conference is dedicated to learning.

Data: One of the major takeaways from this year was the importance of data and its security. For us, we wanted to tie that into our conversations with attendees as it relates to payments. We highlighted how working with the right provider can help non-profit organizations crawl, walk, and run in their payments journey, while also providing the data and security measures they need to be successful.

Community: This is a wonderful community where everyone is looking to help each other. The NTC attendees are all about self-determination, educating themselves, and sharing ideas for organizational transformation. The show’s focus on advocacy and forward-thinking nature encouraged highly engaged and productive conversations.

Any final thoughts on the event?

The opportunity for growth via the use of embedded payments is alive in the non-profit sector, as the community begins to see the simplicity available from the implementation to operationalizing with the right partner.

We are really excited to attend next year’s show in Baltimore and already looking forward to having more exciting conversations with the NTEN community and its attendees. We encourage you to stay connected with our team and reach out to schedule a demo if you would like to learn more about our product.

 

Hosted Payment Page vs. Embedded Component – What’s the Difference and Key Benefits

In the competitive landscape of software, staying ahead means mastering your chosen verticals. One crucial aspect is integrating payments seamlessly into your system. However, the task is often daunting due to the intricate nature of embedding and operationalizing payments.

As a software platform embarking on your payment journey, you will face the challenge of creating the best and most secure payment user experience for your customers. The development required and the allocation of resources can appear complex and time-consuming. Yet, it doesn’t have to be.

Partnering with the right payment provider can streamline the process from discovery to implementation, enhancing the end-user experience for your platform. The right provider offers flexible solutions, to crawl, walk, and run depending on where your software platform is in its payments monetization journey. Hosted Payment Pages and Embedded Components are two such tools.

These solutions enable platforms to evolve from their minimum viable product (MVP) to a fully seamless payment experience. This blog will delve into the details of these options, empowering your software platform to navigate its payment journey effectively.

Hosted Payment Pages vs. Embedded Components – What’s the Difference?

  • What is a Hosted Payment Page? A Hosted Payment Page is a payment page hosted on a payment provider’s secure URL allowing an entry of payment information from your customers.
  • What is an Embedded Component? An Embedded Component is a secure container placed within your software platform’s web experience, which allows for secure entry of your customers’ payment information.

An Overview of Hosted Payment Pages

Using prebuilt options such as Hosted Payment Pages are an easy option for your software platform to offer payments. Many benefits come with choosing the Hosted Payment Page path and there is flexibility for your software platform, including:

  • Little to no coding needed: When it comes to Hosted Payment Pages, one of the main benefits for your software platform is that there is little to no coding needed. Hosted Payment Pages allow you to start monetizing payments quickly, securely, and easily. This means if you’re resource-constrained and don’t have available developers or roadmap capacity you can still begin monetizing your payments volume while buying time to build a deeper integration.
  • Security and compliance advantages: Via the Hosted Payment Page, the right provider can ensure that no sensitive data/payment information touches your system, greatly reducing the burden of compliance for your software platform.
  • Ease of integration and scalability: Hosted Payment Pages and Boarding Links are great starting points for your software platform to accept payments and board customers today while allowing you the ability to build a seamless, payments and boarding experience into your platform over time.
  • Customization: There’s a common misconception that Hosted Payment Pages and boarding forms don’t offer any customization. However, the right payment provider can make this available and offer flexible options. For example, it can be as simple as branding your payment pages with your brand’s custom colors, fonts, and logo to give it your own look and feel even if it is still hosted on your payment provider’s URL. 

An Overview of Embedded Components

Embedded Components provide a seamless experience to allow your customers to accept payments securely via a JavaScript-based collection and tokenization system embedded within your platform, protecting sensitive data and limiting your PCI Compliance scope.

Similar to the Hosted Payment Page solution outlined above, there are various benefits for software platforms that choose the Embedded Component path for payment acceptance as well as merchant boarding and advanced reporting.

  • Seamless and immersed user experience: Embedded Components provide a more native user experience ensuring your customers always stay within your platform reducing customer friction and abandonment.
  • Greater control and customization options: Your payment provider will provide you with the Embedded Component, and from there you will have the ability to customize it with all your branding needs to fit your platform’s look and feel. Any additional information you want to include is still available to you.
  • Security and compliance: Just like the Hosted Payment Pages, your payment provider should be hosting any payment information and reduce the burden of PCI compliance via the Embedded Component path. They take care of the security, you take care of the UI and branding.
  • Development and maintenance considerations: You are in control of anything that involves your Embedded Component, which boosts user experience.

Does Your Payment Provider Offer the Flexibility You Need?

Choosing the right payment provider is crucial for your software platform as you seek flexibility in your payment offering. Here are a few key things to consider when choosing your payment provider as it relates to Hosted Payment Pages vs. Embedded Components:

  • Do they offer solutions that allow you to “crawl, walk, or run” depending on your needs? The right payment provider can meet you where you are in your journey and provide flexibility with your implementation. For example, maybe your team wants to get up and running quickly so you decide to start with the Hosted Payment Page solution but eventually would like to graduate to the Embedded Component path. The right payment provider will take on a consultative approach with you and your team from the beginning, assess your software platform’s current stage and needs, and map out the proper development and implementation plan to ensure success.
  • Is your payment service provider aligned with your requirements? With the consultative approach, the right provider will have the confidence to recommend the solutions they think are best for your business. At Payabli, our team of payment experts has extensive knowledge of the intricacies of different implementation paths and use cases. While we like to give our Partners full reign of their payment journeys, we are also here to offer best practices and recommendations so that your platform is set up for long-term growth and payment success.
  • Security, compliance, user experience, and scalability: As you embed payments into your software platform, you are inherently in scope for PCI compliance by bringing payments into your ecosystem. However, working with a PCI Level 1 certified provider like Payabli, you can reduce this scope by leveraging the security built into Hosted Payment Pages and Embedded Components which will insulate you as the platform from touching any PCI-sensitive card data. This will provide a foundation for a safe and successful launch of your platform.
  • Do they offer an “all-in-one” solution and tools for optionality? From Embedded Components and Hosted Pages to a Robust WebApp and No-Code tools, it’s important to make sure you are partnering with a payment provider that provides a holistic offering that spans myriad use cases and features. 

For software platforms, integrating seamless payment solutions is paramount. By partnering with a payment provider like Payabli, platforms can streamline the process and enhance user experiences with our API-first approach.

Whether through Hosted Payment Pages or Embedded Components, platforms can swiftly adapt and scale their payments business. The key lies in selecting the right payment service provider, one that aligns with the platform’s needs and champions flexibility.

Ultimately, strategic partnerships pave the way for sustainable growth and success in the ever-evolving realm of software platforms.

Are you interested in learning more?

Speak with our payment experts to learn more about Payabli’s hosted vs. embedded payment solutions and how our team can help get you on the right path.

Winning the Chargeback Game: Strategies for SaaS Platforms to Reduce Merchant Chargebacks

In the fast-paced realm of Software as a Service (SaaS), efficient payment operations are vital for business success. Chargeback management, in particular, is crucial as customer disputes can profoundly affect a SaaS platform’s bottom line and reputation.

This comprehensive guide provides essential insights into chargebacks, emphasizing their impact and the importance of choosing a reliable payment service provider to handle and minimize associated risks for SaaS businesses.

Understanding Chargebacks in the SaaS Ecosystem

What is a chargeback? A chargeback is when a customer disputes a transaction with their bank or credit card issuer, leading to a forced reversal of a transaction.

How and why do merchant chargebacks occur in SaaS platforms? There can be several reasons merchant chargebacks occur for SaaS platforms. Some of the most common reasons are:

  • Unauthorized transactions: This occurs when a SaaS business’s merchant/customer does not recognize a charge, assumes it is fraudulent, and then initiates a chargeback. 
  • Dissatisfaction with service: Customers might file for chargebacks if they feel the service didn’t meet the advertised standards or expectations. This could be due to issues like downtime, bugs, or lack of promised features.
  • Billing errors: Mistakes such as being charged the wrong amount, being billed twice, or not receiving a promised refund can lead to chargebacks. These issues often arise from administrative errors or system glitches.
  • Subscription and cancellation issues: SaaS businesses most commonly operate on a subscription model, and sometimes customers may have trouble canceling their subscriptions or might not understand the terms of renewal. If they see charges after attempting to cancel or if they were unaware of automatic renewals, they might file a chargeback.
  • Fraud: Chargebacks can occur due to actual fraudulent activities, where stolen card information is used to purchase subscriptions. Once the rightful card owner notices, they will likely dispute the charges.
  • Friendly Fraud: This occurs when a customer makes a purchase but then disputes the charge with their bank instead of requesting a refund directly from the service provider, often claiming they didn’t authorize the purchase or weren’t satisfied with the service, even if they were.

What is the Difference Between Refunds and Chargebacks? 

Refunds are direct reimbursements from merchants to customers for issues like returns or dissatisfaction, initiated by the customer but processed by the merchant.

Chargebacks are disputes initiated by the customer through their bank against a transaction, potentially leading to a forced reversal of the charge, additional fees for the merchant, and a more complex resolution process. Chargebacks can be more damaging to merchants than refunds due to higher fees and negative impacts on their acquiring bank relationship.

The Significance of Chargeback Management for SaaS Platforms 

Chargeback management holds significant importance for SaaS businesses and their customers across several fronts.

It is important to understand how unchecked chargebacks can inflict substantial financial ramifications on SaaS companies, leading to revenue losses, increased operational costs, and potential disruptions to cash flow. Moreover, excessive chargebacks can tarnish a merchant’s reputation and strain relationships with payment processors, potentially resulting in account termination or heightened transaction scrutiny.

Maintaining healthy chargeback ratios is also paramount for SaaS businesses, as high ratios can trigger penalties and restrictions from payment processors, impacting their ability to offer a compelling embedded payment offering. As a general rule of thumb, a healthy chargeback ratio is considered below .5%.This emphasizes the importance of close monitoring and the proper tools SaaS businesses should leverage to avoid high merchant chargeback rates.

For Saas Platforms’ customers, chargebacks can damage their reputation, negatively impact cash flow, jeopardize their business’s health, and even place them on Industry Blacklists like Mastercard MATCH list, impeding their ability to accept electronic payments. Effective chargeback management strategies, including fraud prevention measures and clear communication with customers, are essential for sustaining the financial health and reputation of SaaS businesses while ensuring a positive experience for their clientele.

Proactive Measures and Best Practices for SaaS Businesses to Prevent Chargebacks

SaaS platforms can take several proactive measures to prevent chargebacks and minimize their occurrence for both their business and customers:

  1. Offering merchants a comprehensive onboarding experience and user guides:
  • Develop comprehensive onboarding materials and user guides to help customers understand how to use the platform effectively and navigate billing processes with their customers.
  • Provide tutorials, walkthroughs, and instructional videos that demonstrate key features, functionalities, and billing procedures to minimize user confusion and reduce the likelihood of billing-related disputes.
  • Offer ongoing training and support resources to empower customers to make informed decisions and manage their accounts efficiently.

2. Educate your merchants about implementing clear and transparent billing practices:

  • Clearly communicate subscription terms, pricing, billing cycles, and renewal policies to customers in initial conversations.
  • Ensure that billing descriptors are easily recognizable on credit card statements to minimize confusion and prevent customers from disputing charges due to unrecognized transactions.
  • Provide detailed invoices or receipts outlining the products or services rendered and the associated charges. For any services provided detailed photography of any work done and a customer signature is highly recommended.  
  • Refund policies: It is important to communicate what your refund policies are upfront with your customers to prevent dissatisfaction or chargebacks.

3. Enhancing customer communication and support:

  • Offer multiple channels for customer support, including email, phone, live chat, and self-service portals, to address inquiries and concerns promptly.
  • Provide proactive notifications and updates regarding subscription renewals, billing changes, or service interruptions to keep customers informed and mitigate surprises that may lead to chargebacks.
  • Implement a customer feedback mechanism to gather insights into potential issues or areas for improvement, allowing the platform to address customer concerns proactively.

4. Utilizing preventative tools like fraud and anomaly detection to catch bad actors before they run a payment:

  • Leverage a modern payment infrastructure that provides robust tools, such as access to fraud consortiums, anomaly detection systems, and user behavior analytics to identify suspicious activities and potential fraudulent transactions.
  • Ensuring that Address Verification Service (AVS) details are passed through with every transaction. AVS verifies that the billing address entered by the customer is the same as the one associated with the cardholder’s account. AVS not only helps prevent merchant chargebacks it can reduce interchange rates by .10% to .30% reducing merchant processing rates and/or improving SaaS Platforms Payments margins.  
  • Set up alerts and monitoring for unusual customer behaviors, such as multiple failed login attempts, changes in payment methods, or unusually high transaction volumes, to trigger further investigation and mitigation efforts.

Work with reputable payment service providers that offer fraud prevention tools, and real-time monitoring capabilities to prevent chargebacks from being created in the first place.

Leveraging the Appropriate Payment Technology for Chargeback Management

With all this being said, working with the right integrated payment service provider can help you ensure and manage potential risks and flags regarding chargebacks and chargeback management.

Reputable payment service providers like Payabli offer advanced chargeback management and risk tools to ensure your SaaS business is in good hands, including:

  • Integrated dispute management tools to automate and provide an extra layer of control and security over your platform and its merchants.
  • White-glove support with responsive tools like our Chargeback Concierge program to help your team respond to merchants about chargebacks at no charge.
  • Chargeback management APIs so you can handle chargebacks and disputes directly from your platform in real time.
  • Risk management. Our risk team works closely with our SaaS partners every step of the way to proactively monitor, mitigate risk, and prevent chargebacks from occurring.

We’ve received incredible feedback from our partners and have significantly reduced their time spent managing and responding to chargebacks with our easy-to-use chargeback and dispute management tools mentioned above. Megan Mclean, fitDEGREE’s Integrator stated she’s “saved dozens of hours per month” managing and responding to merchant chargebacks after integrating with Payabli.

Beyond Chargebacks: Building a Customer-Centric SaaS Platform

Customer satisfaction is paramount in reducing chargebacks for SaaS businesses. Satisfied customers are less likely to resort to chargebacks to resolve disputes or express dissatisfaction. By analyzing chargeback data, businesses gain insights into customer pain points and areas for improvement, driving continuous enhancement of products and services. Investing in customer success initiatives enables proactive engagement, personalized support, and early issue resolution, reducing the risk of disputes.

By fostering positive relationships and delivering exceptional experiences with the help of payment partners like Payabli, SaaS platforms can mitigate chargebacks, drive loyalty, and differentiate themselves in the market. Embracing feedback loops and prioritizing customer satisfaction are essential strategies for minimizing chargebacks maximizing long-term success and fostering a more customer-centric platform.

Conclusion

Chargeback management is critical for SaaS businesses as it directly impacts customer satisfaction and financial stability. Proactive management of chargebacks demonstrates a commitment to resolving disputes swiftly, preserving customer relationships, and maintaining trust in the service. Partnering with the right payment service provider with advanced built-in chargeback management and risk monitoring tools equips businesses with tools and expertise to effectively manage, reduce, and gain valuable insights into chargeback trends, enabling them to optimize processes and minimize financial losses in the long term.

Interested in learning more? Schedule time with our team to chat more about your SaaS platform’s payments and chargeback management strategies.

Merchant Underwriting: Balancing Onboarding & Risk for Platform Success

You may have read our recent blog on creating frictionless experiences for onboarding. As SaaS Founders we all want to over-index on providing exceptional customer experiences. A smooth merchant underwriting and onboarding experience is key to making a positive first impression. With fraud continuously on the rise, software platforms must take the necessary precautions to ensure they have the proper measures in place. In fact, McKinsey found that 37% of merchants seek fraud prevention as one of their top value-added services in their Payment Service Provider. With more conversations and education around this topic, we already expect that percentage to have risen. By the same token, ensuring the safety and security of your platform so that ‘bad actors’ are not committing fraud should be also considered part of creating positive user experiences.

Not only can bad actors cause significant losses for your software platform, but they can also put your entire payment processing program in jeopardy with Sponsor Banks, Card Networks, and regulators. Some big names in the payments industry have recently come under fire for lax Know-Your-Customer (KYC) policies allegedly enabling activity like money laundering and illicit sales of contraband. In this blog, we discuss how software platforms should balance frictionless merchant onboarding with proper merchant underwriting and risk protocols to build their payments business the right way.

So when we say ‘frictionless onboarding’, we should add an asterisk saying, “for the good businesses who intend to actually use our platforms.”

Defining Good Actors vs. Bad Actors

While we’re not part of the Oscars Committee, Payabli is determined in distinguishing good actors from bad actors. Let’s start with defining what a good actor versus a bad actor means for software platforms embedding payments:

Good actor: A good actor in the context of payments and fintech operates a legitimate business and intends to adhere to the terms of service of your platform as well as payment network requirements or government regulations.

In simpler terms, these are your regular users and clients of your platform who intend to run payments through a legitimate business without breaking any rules and regulations. It’s important to note that some good actors may operate large, complex, or even regulated businesses that require greater due diligence.

Bad actor: A bad actor can come in many forms even when applying just the context of accepting and disbursing funds. These are persons or organizations that engage in fraudulent activities like attempting to attack your hosted or embedded payment capabilities with stolen card data or even worse, trying to impersonate a business by creating a synthetic identity and submitting it as an application for services. There are even cases when good customers develop fraudulent intent, despite having a positive history but have recently changed their motives due to unknown circumstances.

Now that we have a general understanding of good actors and bad actors. Let’s dive into the merchant onboarding and underwriting process that Payment Service Providers like Payabli must perform to enable good actors to process payments and prevent bad actors from infiltrating our ecosystem.

What Goes into Merchant Underwriting?

With the help of automated tools, underwriters at reputable Payment Service Providers evaluate the application based on a variety of methods such as but not limited to:

  • Blocklists: To identify previous bad actors, any suspicious demographics, how frequently the same application details have come through, and many more functions to prevent repeat offenders.
  • Fraud and Identity Verification: Reputable Payment Service Providers want to catch bad actors immediately. This includes rules for detecting synthetic identities, reviewing device and browser details, geolocation, and more.
  • Know Your Customer (KYC): To confirm the identity and accuracy of the information on the application about the business and its owners.
  • AML, Sanctions, and Watchlists: To meet our regulatory obligations by verifying the business and its owners against the list of sanctions, politically exposed, and other government lists.
  • Creditworthiness: Credit risk will vary by product and client so it’s important to be flexible. Payment Service Providers will evaluate businesses and their owners based on industry type, transaction volume, financial stability, and other factors.

Upon approval, businesses are set up with an account and provided with payment processing capabilities for collecting invoices for goods and services and paying their bills to vendors. However, even with approval, it’s wise to have compensating controls for mitigating credit and other types of risk after onboarding.

Balancing Frictionless Boarding with Comprehensive Risk Management

Risk processes don’t have to be invasive or require intense back and forth between applicants and risk teams. Modern risk capabilities should operate continuously throughout the customer’s interaction with your platform. For example,

  • When a user creates an account – a Payment Service Provider like Payabli can identify where the application is originating in the background and compare that with information being submitted to calculate the physical distance between them. We can then block that IP from submitting further information to our platform.
  • When an unknown customer attempts to process a transaction – we can hold transactions from being captured and processed when they occur at suspicious times like 3am. The user may see an authorization but it will not settle until a risk officer approves it.
  • When someone attempts to login into an account – we can compare this with a history of previous interactions to detect anomalies in their login attempt such as an unrecognized device. We can then push an alert to the account owner that someone has attempted to log in from a different device and IP Geolocation than normal.

Using tools that operate discreetly allow software platforms to manage their risk without noticeably impacting good actors. It’s important to note that False Positives can still arise so it’s wise to collect more information. Typically, a bad actor won’t upload bank statements, much less get on the phone when we catch them. This quickly hampers their attempts. Most good actors are well aware of review processes for financial products and feel safer when a partner does verify their information.

Streamlining Complex Businesses with Care

Setting expectations is crucial in life and especially in payments. Every vertical is different so you don’t want to use the same rules, conditions, or requirements to underwrite them all. There are certain industries and business sizes that will require greater due diligence than the average micro-merchant. When we are working with these types of businesses, it’s useful to ask for information up-front or to automate additional tasks. A few examples could be:

  • A large construction company requests merchant services but processes some very large transactions worth hundreds of thousands. Our partners can choose to segment their boarding processes with templates so that their enterprise customers like this construction company get asked to upload financial statements as part of their application process.
  • A seasonal business invoicing thousands of dollars with advanced payments for services has requested processing. Based on these inputs, we can automatically pull financials, assets, liabilities, and balance data to decide without ever needing to interact with the client to determine they are in good standing.
  • A fitness studio that offers high-ticket yoga retreats as an ancillary service to some of their customers has applied for merchant services. Every now and then they receive cancelations but they’ve always been able to return the funds to customers historically with no issues based on a review of their processing statements. However, taking lessons from the start of the pandemic it would be hard to weather all canceled trips. So as part of boarding these types of nuanced scenarios, you let your clients know you will be collecting a rolling reserve as part of the transaction processing to serve as a rainy day fund in case things go south (and I don’t mean to the Bahamas.)

Oftentimes people forget that opening a merchant account is akin to receiving an unsecured loan. When a business asks for a loan they typically expect some financial due diligence to be conducted. At a certain amount of volume requested, you and your customers should anticipate providing some additional financial documentation to mitigate undue risk and prevent bad actors from committing fraud. As we mentioned, certain scenarios and industries will require Payment Service Providers like Payabli to perform this additional level of review. However, it shouldn’t have to be painful or time-consuming for customers. So, working with a partner who understands how to handle this with finesse is key.

*Note: Though we do not cover it in this post, it’s important to keep a pulse on these businesses even after merchant underwriting and onboarding to properly manage your ongoing exposures. Keep your eyes peeled for a future post on ongoing monitoring.

Conclusion

Balancing frictionless onboarding with effective risk management is crucial for your software platform’s success. Distinguishing between legitimate and fraudulent actors, Payment Service Providers like Payabli implement stringent merchant underwriting processes to mitigate risks. It is also important to note that as business owners or software platforms, making the effort to integrate personal interaction and request additional information via phone calls, or other forms of direct communication can yield significant value during the merchant underwriting and onboarding processes.

Through measures like blocklists, fraud verification, and tailored criteria, payment providers like Payabli can strike a balance – welcoming compliant businesses while safeguarding against potential threats. This nuanced approach fortifies platform integrity, fosters trust, and supports sustainable growth in the dynamic digital landscape. ​​

Interested in learning more? Schedule some time to chat with one of our payment experts. 

Becoming a Payment Facilitator: Top 3 Myths SaaS Platforms Face

In today’s digital age, software (SaaS) businesses are constantly exploring new opportunities to expand their services and generate additional revenue streams. One such avenue is becoming a payment facilitator (Payfac), where businesses obtain a special designation in the payments industry giving them more control over their payment operations and better economics in exchange for taking on more responsibility and compliance requirements.

However, the decision to become a payment facilitator is more nuanced and deserves the appropriate context for your business. In this blog, we aim to unravel these myths, shed light on the truth behind them, and share how partnering with a reputable payment facilitator provider can help streamline the journey to becoming a payment facilitator.

Myth 1: Payment Facilitation Will Distract from the Core Business

There’s a prevalent belief that venturing into payment facilitation can divert software businesses from their core focus – and take attention away from resources and the core functions of the company. It is true becoming a Registered Payment Facilitator is indeed a significant amount of effort, and time. The decision to become a registered Payment Facilitator should be carefully weighed depending on numerous factors, however, selecting the right Payment Facilitator provider can allow you to obtain many of the benefits of becoming a PayFac under a Managed PayFac program while maintaining the optionality to graduate into a Registered PayFac when the time is right for your business.

If the context is right for a SaaS platform to become a fully registered payment facilitator, the right Payfac Enabler can make this process easier than ever before. Ultimately, with the right provider, SaaS businesses can focus on their core competencies while expanding their service and product offerings as they will provide a flexible API First Platform that makes integrating simple and can offer both a Managed and Registered program depending on the needs of the Software company.

Myth 2: Payment Facilitation Requires Extensive Resources and Infrastructure

Another misconception about becoming a payment facilitator is the belief that it requires vast resources and extensive infrastructure. It’s crucial to understand that the transition does necessitate certain capabilities, but the magnitude of these requirements largely depends on the intended path taken Managed vs Registered, and the technology provided by the PayFac Enabler.

The truth is, that the scope and complexity of your infrastructure will vary based on your specific business needs, the vertical in which you operate, the size of your customer base, and the volume of transactions you intend to process. The right provider will offer the technology needed for payment facilitation to be incorporated into your existing software platform with relative ease. Additionally, depending on the path taken whether Managed or Registered PayFac the right provider will provide the tooling and infrastructure that can reduce the overall amount of headcount and resources needed and avoid building a payment infrastructure from scratch.

Partnering with a payment facilitator can simplify the transition process. In addition to a Pay Ins gateway for transaction processing the right partner can provide comprehensive Pay Ops tools like merchant onboarding, merchant underwriting, client relationship management, risk monitoring, and a billing engine, which enables software companies to launch with payment facilitation capabilities quickly, securely, and easily. Plus, you’ll still have the ability to own and monitor your payment activities and transactions easily and efficiently all in one place. In turn, this will lessen the demand on your internal resources.

Myth 3: Becoming a Payment Facilitator is Expensive

The perception of high costs often stems from misunderstanding the process involved in becoming a payment facilitator. Becoming a payment facilitator is an investment in your SaaS business’s future growth and sustainability, not just an expense. The costs involved are the groundwork for creating an additional, scalable revenue stream through payment fees. In addition to unlocking new payment revenue, a strong payment partner adds more value for your customers in turn extending customer lifetime value and allowing the software to charge more for their core product.

Integrating with a flexible payment facilitator that can offer software businesses the option of starting with a managed payment facilitator program and grow into a registered payment facilitator program can be more cost-effective and prudent. The right provider can offer solutions tailored to your business needs, eliminating the need for a large team to build your payment infrastructure and helping you optimize your overall investment.

When it comes to your organization’s headcount and resources, partnering with a (Payfac) Enabler alleviates and supports specific areas, including:

  • Payment Operations. The right payment facilitator provider can unbundle key Pay Ops capabilities and offer a-la-carte solutions for SaaS businesses such as boarding, underwriting, risk management, and billing tools. This eliminates the need to task engineering teams to build this from the ground up.
  • Risk management. By partnering with a payment facilitator that offers best-in-class risk management tools, SaaS businesses are provided with the technology needed to optimize their risk management. Whether working under a managed payment facilitator where you offload risk management to the provider or pursuing a registered payment facilitator you can leverage their technology to not have to scale a large in-house risk team.
  • Legal and administrative burden. Under a managed payment facilitator program with a registered payment facilitator provider, SaaS businesses can lean on their provider’s resources and do not have to assume many of the legal and administrative responsibilities that come with becoming their own payment facilitator.
  • The need for additional vendors, service providers, and tools integrations. A payment facilitator provider can serve as an orchestration layer offering hundreds of different risk providers, and tools, allowing Software companies to customize their risk solution with a menu of many different back-end providers via one integration and take advantage of simplistic pricing.   

While it’s fair to acknowledge that there are costs associated with this move, it’s equally important to understand the potential for a robust return on investment. The McKinsey Global Payments Report cited in their 2023 analysis that the “five-year outlook for payments revenue remains strong, with likely revenue growth anywhere from 6 to 8 percent, and that the market remains on pace to exceed $3 trillion in payments revenue by 2027.”

Bain & Company cites that “by 2026 financial services embedded into software platforms will exceed $7 trillion.”

With all this being said, payments should be seen as a strategic investment that can pave the way for sustainable growth and enhanced profitability. It’s about adopting a forward-thinking approach, balancing the initial costs against the potential for increased revenue, improved customer satisfaction, and long-term savings.

Conclusion

By unraveling these common myths, we hope to inspire software (SaaS) businesses to consider the possibilities and benefits of payment facilitation seriously. Additionally, educating themselves and exploring the option to partner with a reputable payment facilitator and orchestration provider like Payabli can offer the guidance, support, and tools they need to navigate the process more efficiently and confidently.

At Payabli, we help hundreds of software businesses navigate their payment journeys in a way that suits their needs and growth goals.

And when your software business is ready to dive head-first into payment facilitation, we are there to support and provide you with:

  • The room for you and your team to focus on your core SaaS products and growth 
  • A comprehensive payments tech stack, with built-in tools and resources, such as risk monitoring, customer relationship management, and more.
  • Cost-effective solutions tailored to your vertical focus and business needs, eliminating the need for additional headcount dedicated to your payment infrastructure.

If you’re interested in speaking with one of our payment experts to learn more about our solutions, contact us here.