Rainforest

What it is

Rainforest is Rainforest Pay, Inc.’s payments-as-a-service product for software platforms that want merchants to accept payments from users inside the platform. The homepage calls it payfac-as-a-service, purpose-built for vertical SaaS. Docs name three parties: the platform (the software embedding Rainforest), merchants (the platform’s customers), and users (the people or businesses paying those merchants).

Rainforest underwrites merchants. Public processing terms are a three-party contract among Rainforest Pay, Inc. (a Delaware corporation, entering as agent of a sponsor bank), the merchant, and the sponsor banks. The platform is not a party to those terms. Merchant card statements use the descriptor prefix RF *, which Rainforest docs call its Payment Facilitator prefix.

Who it’s for

One shape, from Rainforest’s own pages: vertical software platforms that want to monetize payments without taking on the risk and compliance work of registering as a payment facilitator. The company page says Rainforest is focused on software platforms making money from payments and does not deal directly with merchants. The product page says merchant onboarding stays inside the platform and Rainforest will never contact merchants directly.

Processing terms require merchants to have their principal place of business in the United States, excluding U.S. territories and possessions. Docs describe deposits on US banking days. This listing does not treat that as a global acquiring product.

It is a fit for a US vertical software company that wants a white-labeled payments program, control of merchant pricing, and Rainforest holding KYC, fraud monitoring, and PCI.

Standout details

• Onboarding can use a low-code embeddable component (recommended), the Platform Portal, or APIs. Docs say Rainforest runs KYC and KYB and returns approved, declined, or manual review. Default real-time checks cover tax ID against legal name, owner SSN against owner name, and bank-account ownership; estimated-activity verification is off unless enabled. Production access is not self-serve: complete a terms-of-service review and session-permissions review, then email support; Rainforest says production accounts are created within 48 business hours if those requirements are done. The start-now page offers a sandbox account alongside booking a demo.
• Payment methods on the homepage and product page: card, ACH, Apple Pay, PayPal, Venmo, PayPal Pay Later, and card-present terminals. Docs mark PayPal, Venmo, and PayPal Pay Later as beta and requiring Rainforest to enable the platform; a February 2026 newsroom press release announced the PayPal integration. Apple Pay in the Payment Component is Apple Pay on the Web, not native-app or tap-to-pay Apple Pay.
• Platforms set merchant pricing through billing profiles (percentage and per-item fees by method, plus optional Amex, business, and international surcharges). Rainforest publishes platform pricing separately as a buy-rate, interchange-plus model with no revenue share; this listing does not repeat a rate card. Residuals (merchant fees minus interchange, passthrough, and Rainforest fees) deposit to the platform monthly.
• Merchant deposits default to each US banking day. Docs’ standard timing is T+1 for card and PayPal and T+4 for ACH, configurable per merchant above platform minimums. Deposits can be daily net or monthly gross. Amount splits can take a platform fee or route part of a payin to other merchants, on top of billing-profile processing fees.
• Integration is embeddable components, API-only, or hybrid. Component Studio covers payment, receipt, payment report, chargeback report, deposit report, and merchant onboarding. The product page also lists in-context payment reports, self-serve chargebacks, webhooks, and a pre-built helpdesk. Developers get a sandbox, API logs, and Slack access to senior integration engineers.
• The homepage sells platform-friendly contract terms: ownership of customer relationships, experience, contracts, sell price, and data. A newsroom seed announcement adds no exclusivity, monthly minimums, or annual fees, and full contractual merchant portability. Sponsor banks listed on the legal page are First Citizens Bank & Trust Company and JPMorgan Chase Bank, N.A. The security page states PCI DSS Level 1 certification and AWS hosting.

Sources: rainforestpay.com, Product, Pricing, Developers, Security & Compliance, Our Expertise, Start now, PayPal, Newsroom, Seed announcement, PayPal press, Sponsor banks, Processing terms, Docs overview, Onboarding, Onboarding methods, Real-time underwriting, Merchant billing profiles, Deposits, Deposit timing, Amount splits, Going live, Requesting production access, PCI security guide, PayPal docs, Apple Pay, Devices, Component Studio, Onboarding requirements.

Honest verdict

Rainforest is the listing to read when the job is PayFac-as-a-service for a US vertical platform: white-labeled components, a published interchange-plus buy rate, and the platform setting merchant prices and keeping the relationship. Rainforest underwrites. Rainforest is the party on the merchant processing terms. Sandbox is public; live processing waits on a contract and a production-access request.

What it is not: a PayFac license you own, or a documented path to become the PayFac on the same stack. It is also not a global acquiring product. If the job is payments revenue this quarter without a buy-rate program, Connect is the simpler public path. If the job is residual economics you might own later as the licensed party, Finix is the write-up that states that path. If the job is to run a white-label program now, with Rainforest as the facilitator and the buy rate in public, start here.