• The four things software can embed
  • Worked example: one contractor, one app, four products

Embedded finance means getting a financial product, such as a payment, a business account, a card or a loan, inside software that isn't a bank. You see it as a "Pay now" button on an invoice, a balance in your job-management app, a card you order from your accounting tool, or a financing offer next to your sales history.

The software company runs the screens and the customer relationship. The regulated part, meaning holding deposits, issuing cards and making loans, sits with a bank or another licensed financial company working behind the software.

In the US, federal bank regulators describe it this way. Fintech companies give end users access to deposit accounts, payment services and loans "through online and mobile applications, platforms, or digital wallets" by partnering with banks. These setups are "sometimes referred to as 'banking-as-a-service' or 'embedded finance'" (Federal Reserve, FDIC and OCC request for information, July 2024).

This page explains the US setup. Other countries regulate these arrangements under their own rules.

The four things software can embed

The same regulators group these arrangements into deposit-taking, payments (including card issuance and digital wallets) and lending (RFI). For a small business, that looks like this:

  • A "Pay now" button on your invoices is card or bank payment processing. The regulated part comes from a payment processor and the banks behind it.
  • A business balance with account and routing numbers is a deposit account, provided by a bank. The software company is not the bank.
  • A debit or spending card for you or your staff is a card program, issued by a bank.
  • "You're pre-qualified for $15,000" is a loan or cash advance from a bank or a lending company.

Stripe, one of the companies that provides these building blocks to software firms, describes its platform product the same way. It lets software "let businesses accept payments, hold funds, move money, spend with cards, and access financing within your software" (Stripe Connect docs).

Its own disclosures show who holds the regulated pieces. For its Treasury accounts, Stripe says "Stripe is not a bank" and that checking accounts are "provided exclusively by Fifth Third Bank, National Association, Member FDIC" (Stripe Treasury docs). Its financing product provides "loans, cash advances, loan advances, and a line of credit from different financial partners" (Stripe Capital docs).

Worked example: one contractor, one app, four products

Sample business, sample figures and a fictional app. The fee and financing terms are illustrations, not any provider's prices.

Rosa runs a two-van heating and cooling business. She uses a job-management app, which we'll call FieldDesk, to schedule jobs and send invoices. FieldDesk has embedded four financial products. Here is one week, and who is really doing each job behind the screen.

1. Her customer pays an invoice inside the app. Rosa sends a $3,200 invoice for a furnace replacement. The customer pays by card from the invoice link.

  • At a sample processing fee of 2.9% + $0.30, the fee is $92.80 + $0.30 = $93.10, so $3,106.90 reaches Rosa.
  • Behind the screen, FieldDesk passes the payment to its payment processor, which settles it through the card networks and banks. FieldDesk never decides whether the card is approved.

2. The money lands in a "FieldDesk balance." The app shows a balance of $18,450 with an account number. Legally, that's a deposit account at FieldDesk's partner bank.

  • The account agreement names the bank. That bank, not FieldDesk, is the FDIC-insured institution.

3. She gives a technician a card. Rosa orders a debit card for her technician and sets a $500 daily limit in the app.

  • The card is issued by a bank. FieldDesk only provides the screen where Rosa sets the limit.

4. The app offers financing. Based on 12 months of invoices, FieldDesk shows an offer: $15,000 now for a flat fee of $1,200, repaid by holding back 10% of each payment she receives.

  • She owes $15,000 + $1,200 = $16,200 in total.
  • The next $3,200 invoice payment sends $320 to repayment, leaving $15,880 owed.
  • The money comes from a lending partner, and the loan agreement names it. FieldDesk's part is showing the offer at the moment Rosa is looking at her receivables.

What the example shows:

  1. One login, four separate providers. Rosa deals with FieldDesk, but each product has its own regulated provider and its own agreement. Those agreements, not the app's labels, set her rights. Stripe's docs say the same about its own accounts: "Account labels don't by themselves determine your legal rights or FDIC insurance eligibility" (Stripe Treasury docs).
  2. Convenience comes from the data the software already has. The app knows the invoice, the customer and the payment history. So it can collect the payment, show the balance and size the financing offer without Rosa re-entering anything.
  3. Cost is easier to miss. The $1,200 fee is stated as a flat amount, not an interest rate. Before accepting, Rosa should compare the total repayable ($16,200) with other options, such as invoice financing or a bank line of credit.

Is money in an embedded account FDIC-insured?

In the US, it depends on where the money actually sits and how the account is set up. The FDIC is direct about it: "nonbank companies themselves are never FDIC-insured." Money you send to a nonbank company isn't eligible for FDIC insurance until the company deposits it in an FDIC-insured bank and other conditions are met (FDIC: Banking with third-party apps).

Two points matter for a business using an embedded account:

  • Insurance covers a bank failure, not a software company failure. FDIC deposit insurance "does not protect against the insolvency or bankruptcy of a nonbank company" (FDIC). The Federal Reserve, FDIC and OCC have warned that end users may not realize "access to their funds may depend on the third party" (joint statement, July 2024).
  • Pooled accounts rely on "pass-through" coverage. When a software company holds customers' money in one pooled account at a bank, each customer can be covered only if certain recordkeeping requirements are met (joint statement). Stripe's docs show both setups side by side. In its "checking account," the business is the direct account holder at the bank. Its "business account" holds funds through a pooled "for benefit of" (FBO) arrangement that relies on pass-through coverage (Stripe Treasury docs).

Where coverage applies, FDIC deposit insurance covers "$250,000 per depositor, per FDIC-insured bank, for each account ownership category" (FDIC: Understanding Deposit Insurance).

Questions to ask before you use an embedded financial product

  • Which bank or lender is behind it? Look for the name in the account agreement or footer disclosures. You can check that a bank is FDIC-insured with the FDIC's BankFind tool (FDIC).
  • Am I the account holder, or is the money pooled? That decides whether ordinary or pass-through insurance rules apply.
  • What happens to my money if the software company shuts down or I cancel my subscription? Ask how you would get access to the balance.
  • What does it cost in total? Find the processing fee per payment, any account or card fees, and, for financing, the total repayable amount and how repayments are taken.
  • Can I export the records? Payments, payouts and fees should come out cleanly, so you can reconcile them with your bank account at month end.

If you run the software platform

For a software company, embedding finance means taking on a share of a bank's work. Under these arrangements, the bank may rely on third parties to:

  • keep the account records;
  • process payments;
  • carry out compliance work, such as customer identification, suspicious-activity monitoring and sanctions screening;
  • handle customer service and disputes.

The bank, though, "remains responsible for failure to comply with applicable requirements" (joint statement).

In practice, that means your bank partner will expect several things from you:

  • a compliance program;
  • accurate records of whose money is whose;
  • careful wording in any marketing that mentions FDIC insurance.

The joint statement lists telling users their funds are FDIC-insured without explaining what that covers as a possible violation of the FDIC's rules. Confirm your obligations with your bank partner and a lawyer before launch.

Embedded finance vs. related terms

  • Payment gateway. A gateway passes a single card or ACH bank payment to a processor. It's one ingredient of embedded payments. See what a payment gateway is.
  • Integrated payments. This is payment processing connected to the software you already use, such as a pay link on every invoice you send. See integrated payments explained.
  • Open banking. Software reads data from an account you hold elsewhere, with your permission. Embedded finance provides the account, card, payment or loan inside the software. See what open banking is.
  • Banking-as-a-service (BaaS). BaaS is the bank-and-middleware layer that software companies build on. US regulators use "banking-as-a-service" and "embedded finance" for the same family of arrangements (RFI).

The simplest version for a small business is taking card payments on invoices. Billed, which publishes this guide, connects to Stripe and PayPal so clients can pay your invoices online (how payments work in Billed). For the account behind the payouts, see what a merchant account is.

Frequently Asked Questions

What is embedded finance in simple terms?

It's a financial product, such as a payment, a business account, a card or a loan, that you get inside non-financial software instead of going to a bank directly. The software company provides the screens. A bank or licensed lender provides the regulated product behind it.

Is embedded finance the same as banking-as-a-service?

They're two views of the same arrangement. Banking-as-a-service is the bank and technology layer a software company builds on. Embedded finance is what the software's users see. US bank regulators refer to these bank-fintech arrangements by both names.

Is my money FDIC-insured in an app's business account?

Only once it's deposited at an FDIC-insured bank and the conditions for coverage are met. The FDIC says nonbank companies themselves are never FDIC-insured. Deposit insurance doesn't protect you if the software company itself fails. Check the account agreement to see which bank holds the money and whether the account is in your name or pooled.

Who lends the money when my software offers financing?

A bank or lending company does, not the software screen you see. Stripe's financing product, for example, provides loans, cash advances and lines of credit from different financial partners. The loan agreement names the lender and sets out the total cost and repayment terms.

How is embedded finance different from a payment gateway?

A payment gateway handles one job: passing a card or bank payment to a processor. Embedded finance can include payments, but also business accounts, cards and loans delivered inside the same software.

Share

Was this article helpful?