Reservly Payment Disclosure

Last updated: May 19, 2026

The short version

• Reservly is software-only. Reservly is not a Payment Facilitator, Payment Services Provider, Money Transmitter, or Merchant of Record under any regulatory definition.
• When your customers pay your business, money moves through your own Stripe or PayPal account. Reservly never sees card data, never holds the funds, and never takes a percentage.
• When you pay Reservly for your subscription, Paddle is the Merchant of Record. Paddle collects payment, calculates and remits taxes, and issues your invoice.
• Three money flows, three different parties handle the money. This page explains who does what so you know who to contact when something goes wrong.

Questions: support@reservly.io.

1. Reservly's regulatory posture

Reservly operates as a technical service provider under US, EU, and UK payments law. This is not a marketing label — it is the specific legal posture Reservly has adopted, and it has substantive consequences for how money moves, where card data goes, and which laws apply to whom.

1.1 United States — FinCEN technical-services exclusion

Under the Bank Secrecy Act, FinCEN excludes from the definition of "money services business" — and therefore from money-transmitter registration — persons that provide the delivery, communication, or network access services used by a money transmitter to support money transmission services. See 31 CFR § 1010.100(ff)(5)(ii). Reservly fits this exclusion: Reservly provides booking software, the software connects a business's separately licensed payment provider (Stripe or PayPal) to that business's customers, and Reservly never enters into possession of payment funds. Stripe and PayPal are the licensed money transmitters; Reservly is the software that runs alongside them.

1.2 United States — state money-transmitter law exemptions

Most US states with money-transmitter licensing regimes recognise a parallel exemption for software providers that do not handle funds. Reservly does not hold customer funds, does not have custody of payments, and does not have authority to direct payment movement on behalf of merchants. Reservly therefore operates under the technical-services exemption in each state where this exclusion exists. Reservly's business address is in Wyoming; for the licensed handling of payments, Stripe and PayPal each maintain the state-by-state money-transmitter licenses required for their own operations.

1.3 European Union — PSD2 Article 3(k) technical-services exclusion

Under the Revised Payment Services Directive (PSD2), Article 3(k) excludes from the directive's scope "technical service providers, which support the provision of payment services, without them entering, at any time, into possession of the funds to be transferred." Reservly fits this exclusion: Reservly provides booking software with embedded Stripe Elements and PayPal Smart Buttons, and the funds being transferred never pass through Reservly's infrastructure. Stripe and PayPal are the authorised payment institutions; Reservly is the technical service provider operating alongside them.

For the narrower question of whether Reservly might fall inside scope as a payment initiation service provider under PSD2 Article 4(17) — by virtue of holding OAuth tokens that can technically initiate charges, refunds, or transfers against a business's Stripe or PayPal account — Reservly's posture is that Reservly does not initiate fund movements on its own behalf. The OAuth delegation described in § 4 of this page is exercised exclusively at the explicit direction of the business owner through the Reservly dashboard, with each charge or refund authorised by an authenticated business-owner action. Reservly does not pool, batch, or schedule fund movements on its own initiative, does not have access to the business's underlying Stripe or PayPal account credentials, and the OAuth tokens may be revoked by the business owner at any time. On this basis Reservly is the executor of the business owner's deliberate action, not an autonomous payment initiation service provider.

1.4 United Kingdom — Payment Services Regulations 2017 equivalent

The UK Payment Services Regulations 2017 (PSRs) implement PSD2 in UK law and preserve the technical-services exclusion in Schedule 1, Part 2, paragraph 2(j), alongside the payment-initiation-service definition. Reservly relies on the technical-services exclusion for UK-resident merchants on the same basis described in § 1.3 above — including the equivalent narrow-reading of the payment-initiation-service definition: OAuth delegation is exercised exclusively at the explicit direction of the business owner, so Reservly is not the autonomous initiator of any payment. The Financial Conduct Authority is the UK competent authority for payment services; Reservly is not authorised or registered with the FCA because no authorisation is required for a technical service provider that does not enter into possession of funds and that does not initiate payments on its own behalf.

1.5 What this means in plain language

Reservly does not need (and does not hold) the licenses required to process payments. The licensed payment institutions are Stripe and PayPal for customer-to-business transactions and Paddle for business-to-Reservly subscription transactions. Reservly's role is software — connecting a customer's payment instrument to a processor's hosted-field environment so that card data flows directly from the customer's browser to the processor.

2. The three money flows

Reservly's customers see three different payment relationships when they use the platform. Each is governed by a different set of terms and a different party handles the money.

2.1 Flow 1 — Business pays Reservly (Paddle is Merchant of Record)

When you subscribe to Reservly's Solo, Team, or Professional plan, your subscription is sold to you by Paddle.com Market Ltd. as Reservly's reseller and Merchant of Record. Paddle collects your payment, calculates and remits any applicable sales tax, VAT, GST, or equivalent, issues your invoice, and processes subscription refunds on Reservly's instruction in accordance with our Refund Policy.

Your payment contract is with Paddle (subject to Paddle's Buyer Terms). Your software license is with Reservly (subject to the Reservly Terms of Service). These are two separate legal relationships that arise from the same transaction.

2.2 Flow 2 — Customer pays business via Stripe (business is Merchant of Record)

When a business enables Stripe as a payment method on its Reservly booking pages, it is using its own Stripe Connect Standard account, connected to Reservly via Stripe's OAuth flow. The business is the merchant of record for every transaction; Stripe holds and settles funds directly to the business's bank account; Reservly never touches the money.

Payment processing for businesses on Reservly is provided by Stripe and is subject to the Stripe Connected Account Agreement (stripe.com/legal/connect-account), which includes the Stripe Services Agreement (stripe.com/legal/ssa). By operating as a business on Reservly, the business owner agrees to be bound by these agreements as Stripe may modify them from time to time. By using Reservly to enable payment processing through Stripe, the business owner authorises Reservly to share business and transaction information with Stripe.

2.3 Flow 3 — Customer pays business via PayPal (business is Merchant of Record)

When a business enables PayPal as a payment method, it is using its own PayPal Commerce Platform seller account, connected via OAuth. Payment processing is governed by the PayPal Platform Seller Account Agreement (paypal.com/us/legalhub/paypal/platform-seller-agreement) and the PayPal User Agreement. The business is the merchant of record; PayPal acts as the business's limited agent for receiving and processing payments. PayPal's Seller Protection Program does not apply to platform-seller transactions — chargeback risk falls directly on the business, as PayPal itself discloses in the Platform Seller Account Agreement.

3. What Reservly does not do

To be unambiguous about Reservly's posture:

• Reservly does not hold customer payment funds at any point in any flow.
• Reservly does not see, store, transmit, or log full payment card numbers, CVV codes, card expiry dates, or bank account numbers. Card data is collected directly by Stripe, PayPal, or Paddle through their own hosted fields, iframes, or redirected pages.
• Reservly does not take a percentage or per-transaction fee on customer-to-business payments. Reservly's revenue comes from subscription fees only.
• Reservly does not route customer-to-business funds through any internal Reservly account, balance, or escrow. Funds flow from the customer's payment instrument directly to the business's Stripe or PayPal account.
• Reservly does not issue payment cards, payment instruments, or virtual accounts of any kind.
• Reservly does not settle, fund, or guarantee any payment. Settlement timing, holds, reserves, and payout schedules are determined by Stripe, PayPal, or Paddle under their own terms with the business.
• Reservly does not adjudicate payment disputes or fund chargebacks. See § 5 below.

4. What Reservly does do

• Reservly provides booking software that allows a business to sell its own services, events, or rentals through a public booking page.
• Reservly stores non-sensitive payment references returned by the processor — a tokenised transaction ID (e.g., a Stripe pi_… payment-intent ID, a PayPal order ID, or a Paddle transaction ID), the last four digits of the card, and the card brand — used to reconcile bookings and to link to the processor's dashboard for dispute research.
• Reservly stores OAuth tokens (encrypted at rest in Supabase Vault) that authorise Reservly to create charges, issue refunds, and fetch account status on the business's behalf — only when the business takes those actions through the Reservly dashboard.
• Reservly sends confirmation emails, reminders, receipts, and webhooks reflecting the state of bookings and payments as reported by the processor.
• Reservly provides a configurable tax rate per service, event, or rental as a convenience feature. This does not make Reservly the business's tax agent; the business is responsible for determining its own tax obligations (see § 8).

5. Payment disputes and chargebacks

Disputes and chargebacks are handled by whichever party holds the funds when the dispute is raised. Reservly does not adjudicate disputes and does not fund chargebacks.

Customer disputes against a business. If a customer of a business disputes a booking payment, the dispute is between the customer, the customer's card issuer or PayPal, and the business. Stripe and PayPal notify the business directly through their own dashboards and email. The business is responsible for gathering and submitting evidence, meeting response deadlines, and — if the dispute is lost — paying the chargeback amount and any processor fees out of its Stripe or PayPal balance or its linked bank account, per the processor's terms.

Reservly's role. On request, Reservly will provide (a) a PDF or CSV of the booking record, (b) the customer-facing confirmation emails Reservly sent, and (c) any IP address or timestamp metadata Reservly holds. Reservly does not contact the customer on the business's behalf and does not fund any chargeback. Because Reservly never holds customer payments, Reservly has no balance from which to reverse them.

Subscription disputes (business owner against Reservly). If a business owner disputes a Reservly subscription charge, Paddle responds to the card network or PayPal on Reservly's behalf as Merchant of Record. Paddle will usually contact the disputing party first to offer a direct refund under Reservly's Refund Policy. Repeated chargebacks of subscription fees instead of requesting a refund through Paddle or support@reservly.io is a material breach of the Terms of Service.

6. PCI compliance posture

Reservly is designed so that payment card data never reaches Reservly's systems.

• Customer payments on booking pages use Stripe Elements or PayPal inline buttons — both are hosted-fields integrations. When a customer types a card number, the data flows from the customer's browser directly into Stripe's or PayPal's infrastructure. The data does not pass through Reservly's servers and is not stored in Reservly's database.
• Reservly subscription payments are collected on a Paddle-hosted checkout page. Paddle is PCI DSS Level 1 certified as both a service provider and a merchant.
• Reservly's own PCI assessment is therefore SAQ-A (Self-Assessment Questionnaire A) — the shortest and lowest-risk PCI DSS questionnaire, available only to merchants who completely outsource card processing to PCI-compliant third parties.

Reservly follows the SAQ-A script-integrity guidance clarified by the PCI Security Standards Council in 2024 and 2025, including script inventory and integrity monitoring of the third-party hosted-field scripts used on Reservly pages.

Security questions: support@reservly.io with subject line "Security" or "PCI".

7. Liability carve-out for processor acts

Reservly does not adjudicate, fund, or reverse any payment that Stripe, PayPal, or Paddle processes. To the fullest extent permitted by law, Reservly has no liability to a business owner, a customer, or any third party arising from the acts or omissions of Stripe, PayPal, Paddle, any card network, or any acquiring bank — including delays, holds, reserves, account reviews, KYC or AML actions, payout failures, fee changes, or service interruptions on those systems.

Remedies for matters inside Stripe's, PayPal's, or Paddle's control are with Stripe, PayPal, or Paddle directly, under their respective agreements with the business.

8. Tax

Reservly subscriptions. Reservly does not charge sales tax, VAT, or GST on subscriptions. Paddle calculates, collects, and remits all applicable taxes globally as Merchant of Record, including US state sales and use taxes where Paddle has nexus, EU VAT under the OSS regime, UK VAT, Canadian GST / HST / PST, Australian GST, and similar taxes elsewhere.

Customer-to-business payments. Reservly does not calculate, collect, or remit taxes on customer-to-business transactions. The business is responsible for determining whether a transaction is taxable, calculating the correct tax, displaying it on the customer's receipt, and remitting it to the appropriate tax authority. Reservly's booking pages support a configurable tax rate per service, event, or rental as a convenience — this does not make Reservly the business's tax agent.

9. Where this disclosure lives

This page is the canonical statement of Reservly's payment posture for regulators, partners (including Stripe, PayPal, and Paddle), business owners, and customers. Where Reservly's Terms of Service, Privacy Policy, or Refund Policy reference Reservly's payment posture or its non-processor status, this page is the source of truth for the underlying claim.

10. Contact

Reservly c/o Northwestern Registered Agent Services 30 N Gould St Ste R Sheridan, WY 82801 United States

Email: support@reservly.io Subject line for payment-related questions: Payments Subject line for compliance / due-diligence inquiries: Compliance

This page works together with our Terms of Service, Privacy Policy, Refund Policy, and the Sub-Processor List. Where this page describes the platform-level payment posture, the per-business Terms of Service and Refund Policy for each business on Reservly govern that business's own relationship with its customers.