Roam Management
These Payments Terms of Service (“Payments Terms”) are a binding legal agreement between you and Roam Management, LLC (“Roam,” “we,” “us,” or “our”) that governs payments made to and from Roam in connection with your use of the Roam platform. These Payments Terms supplement, and form part of, Roam’s Website Terms of Service (the “Terms of Service”), the Roam Privacy Policy, and any applicable Property Agreement, Host Agreement, or Guest Agreement between you and Roam. Capitalized terms not defined here have the meanings given in the Terms of Service.
By making or receiving a payment in connection with the Roam platform, you accept these Payments Terms. If you do not agree, you must not use the Roam platform or book or list a property through Roam.
Important: Section 17 incorporates the dispute-resolution and arbitration provisions of the Terms of Service. Please read them carefully. Nothing in these Payments Terms waives any right that cannot be waived under applicable law.
These Payments Terms apply to all reservations booked on Roamstays.com (“Direct Bookings”), where Roam acts as the merchant of record as further described in Section 3.
These Payments Terms apply to reservations sourced through a third-party online travel agency, marketplace, or distribution channel (each, an “OTA”), such as Airbnb, Vrbo, or Booking.com (“OTA Bookings”), only to the extent set forth in Section 9. The OTA’s own terms govern the Guest’s payment to the OTA. Where Roam receives funds in connection with an OTA Booking, Roam acts as the limited payment agent of the Host for the purpose of receiving and remitting those funds, as further described in Section 9. Money flows for OTA Bookings are governed primarily by the applicable Host Agreement, Property Agreement, or managed-plan agreement.
These Payments Terms apply both to Guests who pay for a stay and to Hosts who receive funds from Roam. Where a provision applies only to one, that is indicated.
These Payments Terms govern payment mechanics. The economic terms of a particular stay, including price, length of stay, fees, cancellation policy, refund eligibility, and damage rules, are governed by the applicable Listing, Property Agreement, and any Guest Agreement. To the extent these Payments Terms conflict with a Property Agreement, Host Agreement, or managed-plan agreement on commercial terms specific to a Listing or a Host’s plan, the applicable Property Agreement, Host Agreement, or managed-plan agreement controls.
Roam’s payment services described in these Payments Terms apply only to Bookings sourced through Roamstays.com or through OTA channels connected to or operated by Roam. Roam does not provide payment-processing services for Bookings sourced outside Roam’s channels (for example, on a Host’s own website or other distribution channels not connected to or operated by Roam), and these Payments Terms do not authorize Hosts to use Roam’s payment rails, Stripe Connected Accounts established for Roam’s platform, or any other Roam payment infrastructure for any other purpose.
Stays of thirty (30) consecutive nights or longer may, in certain jurisdictions, be treated as residential tenancies rather than transient lodging, and may be subject to landlord-tenant laws, residential lease requirements, and other consumer-protection laws that supersede the commercial terms set out in these Payments Terms or the applicable Property Agreement.
“Booking” means a confirmed reservation of a Listing, whether made through Roamstays.com or an OTA.
“Card on File” means a payment card tokenized and stored by Stripe at the Guest’s direction for use on Direct Bookings and related charges.
“Damage Waiver” means a non-refundable Roam product that, in the markets where it is offered and where permitted by applicable law, replaces a refundable Security Deposit and provides limited damage-cost relief to the Guest, subject to its own terms and exclusions.
“Direct Booking” means a Booking made on Roamstays.com.
“Guest” means a person or entity who books, occupies, or pays for a Listing.
“Host” means a person or entity whose property is offered as a Listing on the Roam platform, regardless of the Host’s plan or the level of services Roam provides for that Listing (including under self-serve, RoamCore, Roam+, or other plans).
“Host Agreement” means the agreement between Roam and a Host that governs the Host’s use of the Roam platform, which may include a self-serve listing agreement, a RoamCore agreement, a Roam+ managed-plan agreement, or another written agreement between Roam and the Host.
“Listing” means a property made available for booking on the Roam platform or, where applicable, on a connected OTA channel.
“OTA” means a third-party online travel agency, marketplace, or distribution channel through which a Listing may be booked, including Airbnb, Vrbo, and Booking.com.
“OTA Booking” means a Booking sourced from an OTA channel.
“Payment Method” means a payment instrument the Guest provides for use on the Roam platform, including a credit card, debit card, or U.S. bank account.
“Payout” means an amount paid by Roam to a Host in connection with a Booking, after applicable deductions.
“Payout Method” means the U.S. bank account a Host provides to receive Payouts via ACH.
“Security Deposit” means a refundable deposit collected from the Guest before the start of a stay, in an amount not exceeding one (1) month’s rent for the applicable stay, or such lower amount as may be required by applicable law.
“Stripe” means Stripe, Inc. and its affiliates, the third-party payment processor used by Roam for Direct Bookings and (where applicable) for Host Payouts.
“Total Price” means the total amount payable by the Guest for a Direct Booking, including the Listing price, cleaning fees, Roam’s service fee, host-specified fees, applicable taxes, and any Security Deposit or Damage Waiver fee.
For Direct Bookings, Roam acts as the merchant of record, regardless of the Host’s plan or the Host’s relationship with Roam (including RoamCore, Roam+, or other plans). This means Roam sells the stay to the Guest and contracts directly with the Guest for the Total Price. Roam engages each Host as a supplier under the applicable Host Agreement to deliver the stay. Roam is not a fiduciary, escrow agent, real-estate broker, travel agency, or insurer.
For OTA Bookings, Roam’s role in payments depends on the OTA, the Listing, and the Host’s plan, and is governed primarily by the applicable Host Agreement and the OTA’s own terms. Where Roam receives funds from an OTA or from a Guest in connection with an OTA Booking, Roam receives those funds as the limited, non-fiduciary payment agent of the Host solely for the purpose of receiving the funds from the OTA or Guest and remitting them to the Host (net of permitted deductions). The Guest’s payment obligation to the OTA, and where Roam is acting as the Host’s agent the Guest’s payment obligation that flows through Roam, is satisfied as to the Host upon the Guest’s payment to the OTA or to Roam as the Host’s agent, as applicable. Roam is not a money transmitter or money services business in connection with OTA Bookings. These Payments Terms apply to OTA Bookings only as expressly set forth in Section 9.
Card processing for Direct Bookings, and the default ACH Payout rail to Hosts, are provided by Stripe under Stripe’s applicable terms, including the Stripe Services Agreement. Hosts that receive Payouts from Roam via Stripe are also subject to the Stripe Connected Account Agreement, which they enter into directly with Stripe through the Roam platform. Where Roam initiates Payouts outside Stripe (for example, by direct ACH or by domestic wire transfer under Section 12.9), those Payouts are governed by these Payments Terms and the applicable Host Agreement. Guests are subject to Stripe’s consumer-facing terms when paying through Stripe. By using the Roam platform, you authorize Roam to share information about you and your transactions with Stripe and, where applicable, with any other payment processor or bank used by Roam, as needed to provide payment services, and you agree to be bound by Stripe’s applicable terms in your use of those services.
Roam does not store full Payment Method numbers. Card numbers are tokenized and held by Stripe, which represents that it maintains compliance with applicable industry standards including the Payment Card Industry Data Security Standard (PCI-DSS). Roam receives only limited card metadata (e.g., last four digits, brand, expiration) for purposes of identifying a Card on File and supporting customer service. Roam maintains administrative, technical, and physical safeguards designed to protect payment-related information in its possession, and handles payment-related personal data in accordance with the Roam Privacy Policy.
By using the Roam platform, you represent and warrant that you are not, and you are not owned or controlled by, a person or entity that is the subject of sanctions administered by the U.S. Department of the Treasury’s Office of Foreign Assets Control (OFAC), the U.S. Department of State, or any other applicable sanctions authority, and that you are not located, organized, or resident in a country or territory that is the subject of comprehensive sanctions. Roam may screen Guests, Hosts, and transactions against sanctions lists and may delay, decline, suspend, reverse, or refer to law enforcement any transaction or account that Roam reasonably suspects of being unlawful, fraudulent, sanctions-violating, or otherwise non-compliant with applicable law.
By submitting a Direct Booking, you (i) represent that you are the authorized user of the Payment Method provided, (ii) authorize Roam (via Stripe) to charge that Payment Method for the Total Price and any other amounts owed in connection with the Booking as set forth in these Payments Terms, and (iii) agree to keep your Payment Method information current.
The Total Price for a Direct Booking is disclosed during checkout and includes:
Direct Bookings are priced and charged in U.S. dollars (USD). If your Payment Method is denominated in a different currency, your bank or card issuer may apply currency conversion or foreign-transaction fees, for which you are solely responsible.
If you create an account on Roamstays.com, you may choose to save a Payment Method as a Card on File. Each subsequent Direct Booking you submit using that account is a cardholder-initiated transaction; by submitting that Booking, you authorize the charge of the Card on File for the Total Price of that Booking. In addition, by saving a Card on File you authorize Roam (via Stripe) to initiate merchant-initiated transactions against the Card on File only for (i) scheduled installments under Section 5, in the amounts and on the dates disclosed at checkout, and (ii) damage and other post-stay charges within the cap and subject to the notice requirements set forth in Section 11. Roam will not charge a Card on File for any other amounts without your specific, additional authorization. You may remove your Card on File at any time through your account; removal does not relieve you of obligations incurred before removal.
Authorizations under Sections 4.4, 5, and 11 are intended to be stored, presented, and processed in accordance with the applicable card network’s stored-credential transaction framework (including the Visa Stored Credential Transaction Framework and Mastercard equivalent). Roam and Stripe will identify each transaction as cardholder-initiated or merchant-initiated, as applicable.
For stays of 30 nights or fewer, the entire Total Price is charged at the time of Booking.
For stays longer than 30 nights, and except as Section 5.5 may require for stays subject to residential-tenancy laws, the Total Price is paid in a series of pre-defined installments, each in a known amount on a known date:
By making a multi-month Direct Booking, you authorize Roam (via Stripe) to charge your Payment Method for each installment in the amounts and on the dates disclosed at checkout. This is a defined installment authorization, not an open-ended recurring authorization. You may revoke this authorization at any time, in which case Roam will not initiate further charges; revocation does not relieve you of the underlying contractual obligation to pay the remaining balance for your Booking, which Roam may collect by other lawful means and which may result in cancellation of the Booking under Section 5.4 and the applicable cancellation policy.
If a scheduled installment is declined, returned, or otherwise fails, Roam will provide notice and a reasonable opportunity to cure the failed payment, including by updating the Payment Method or providing alternative payment instructions. Roam’s right to re-initiate a failed ACH debit is limited by the Nacha Operating Rules. Roam will not re-initiate a debit that has been returned by your bank as unauthorized; in those cases, Roam will instead request that you provide an alternative Payment Method or other payment arrangement, and the underlying obligation remains payable. For debits returned for insufficient or uncollected funds, Roam may re-initiate the debit only within the limits set by the Nacha Operating Rules, which generally permit up to two re-initiations within one hundred eighty (180) days of the original settlement date, and re-initiated debits will be identified as such in the entry description as required by those Rules. If the failed payment is not cured within the time specified in the notice, Roam may, in its discretion, cancel the Booking. Cancellation under this Section is treated as a Guest cancellation under the applicable cancellation policy, and refund eligibility (if any) is determined accordingly. Roam does not charge a separate late or returned-payment fee.
For stays subject to a residential lease or to residential-tenancy laws under Section 1.6, including all stays of thirty (30) nights or longer the Guest’s payment obligations, the timing and manner of rent payments, and the collection and return of security deposits are governed primarily by the applicable lease and applicable law. Roam may, on behalf of the Host, present the Guest with payment authorizations or installment authorizations consistent with the lease and applicable law in lieu of the schedule set out in Section 5.2. Where the lease and these Payments Terms conflict on payment-mechanic matters as to such a stay, the lease and applicable law govern.
Most stays require a refundable Security Deposit, in an amount not exceeding one (1) month of the applicable stay’s rent, or such lower amount as applicable law may require. The Security Deposit is collected at or before the start of the stay and held by Roam (or by Stripe on Roam’s behalf) for the duration of the stay, in each case in the manner permitted by applicable law.
After checkout, Roam will refund the Security Deposit to the original Payment Method, less any deductions permitted under Section 11 (Damage Charges) or under the applicable Property Agreement or lease, within ten (10) business days after checkout (or such shorter period as applicable law may require). Where applicable law requires that an itemized statement of any deduction be provided to the Guest, Roam or the Host will provide that statement within the time required by law. Refunds are processed by Stripe; once issued, the time for the refund to appear on your statement is determined by your card issuer or bank and is outside Roam’s control.
In certain markets, and only where permitted by applicable law, Roam offers a non-refundable Damage Waiver as an alternative to a refundable Security Deposit. The Damage Waiver is a contractual product offered by Roam. It is not insurance, is not a substitute for insurance, is not regulated as insurance, and does not provide the protections or rights afforded under an insurance policy. Where the Damage Waiver applies:
The Damage Waiver is not offered in every jurisdiction. A current list of jurisdictions in which the Damage Waiver is offered, and the applicable Damage Waiver terms, are made available at Roamstays.com and are disclosed at checkout where the Damage Waiver is offered.
Roam charges Guests a service fee on Direct Bookings for the Guest’s use of the Roam platform. The service fee is disclosed at checkout, is calculated based on the Booking subtotal and other factors, and is non-refundable except as expressly provided in the applicable cancellation policy.
Cleaning fees and host-specified fees (such as pet fees, utility fees, or resort fees) are set by the Host or the applicable Property Agreement and are disclosed in the Listing and at checkout. These fees are passed through to the Host, less applicable processing or service deductions described in the applicable Host Agreement.
Applicable sales, lodging, occupancy, tourism, and similar taxes are shown separately on Roamstays.com at checkout. Roam collects and remits taxes to the applicable taxing authority where it is required by law to do so in the relevant jurisdiction, including under marketplace-facilitator and similar laws. The jurisdictions in which Roam is required to collect and remit change over time as laws are enacted or amended, and Roam’s tax obligations may exceed those that the Host or any Property Agreement has separately authorized; Hosts acknowledge and authorize Roam to comply with applicable tax-collection and remittance obligations regardless. In jurisdictions where Roam is not required by law to collect and remit, the Host is responsible for determining, collecting, and remitting any taxes due. If Roam subsequently determines that taxes were over-collected from a Guest, Roam will refund the excess to the Guest. If Roam determines that taxes were under-collected as a result of inaccurate or incomplete information provided by the Host, including with respect to the location, status, or registration of the Listing, Roam may deduct the shortfall from the applicable Host Payout under Section 13, and the Host indemnifies Roam against any related tax liability, interest, and penalties.
Roam may change its service fee or other Roam-charged fees from time to time. Fee changes will not affect Bookings confirmed before the effective date of the change. Material changes will be communicated in accordance with Section 16.
Roam reserves the right, subject to applicable law and card-network rules, to apply a surcharge, convenience fee, or similar charge in respect of certain Payment Methods, provided that any such charge is disclosed at checkout before the Guest authorizes the transaction. No surcharge is currently applied.
The cancellation policy applicable to a Direct Booking is disclosed at checkout and incorporated into the Property Agreement. Refund eligibility and amount are determined by that cancellation policy, except where superseded by these Payments Terms, the Terms of Service, or applicable law.
Approved refunds are issued by Roam (via Stripe) to the original Payment Method only. Roam will issue refunds within ten (10) business days after approval (or such shorter period as applicable law may require). The time for refunds to appear on your statement is determined by your card issuer or bank and is outside Roam’s control.
If a Booking is materially disrupted by an event outside the reasonable control of the Guest or the Host, including a natural disaster, severe weather event, government-issued travel restriction, declared public-health emergency, mandatory evacuation, fire, flood, war, terrorism, or other force-majeure event, Roam may, in its reasonable discretion exercised in good faith and consistent with applicable law, modify, defer, credit, or refund the Booking, in whole or in part, notwithstanding the cancellation policy that would otherwise apply. Any refund, credit, or rebooking adjustment issued under this Section 8.3 is borne by the Host and is deducted from the Host Payout in accordance with Section 13. Roam may, in its sole discretion, elect to absorb a portion of the cost; any such election must be made in writing and applies only to the specific Booking or program identified in the writing.
Refunds for Direct Bookings are issued only through the Roam platform. Hosts must not offer or accept off-platform refunds, side payments, or rebates in connection with a Direct Booking.
For OTA Bookings, the OTA’s own terms govern the Guest’s payment to the OTA, including the timing of charges, accepted payment methods, currency, refund mechanics, and chargeback handling. Roam is not the merchant of record for OTA Bookings and does not contract directly with the OTA Guest for payment of the Total Price.
For OTA Bookings, the flow of funds among the OTA, Roam, and the Host is governed primarily by the applicable Host Agreement, the OTA’s own terms, and any managed-plan agreement between Roam and the Host. Where Roam receives funds from an OTA or from a Guest in connection with an OTA Booking, Roam receives those funds as the Host’s limited, non-fiduciary payment agent for the sole purpose of receiving and remitting them to the Host (net of permitted deductions under Section 13). The Guest’s payment obligation that flows through Roam is satisfied as to the Host upon receipt by Roam. Roam may commingle such funds with its own operating funds to the extent permitted by applicable law and does not hold them in trust or in a separate fiduciary account unless required by applicable law. If there is any conflict between these Payments Terms and the Host Agreement, managed-plan agreement, or OTA terms (as applicable), the Host Agreement, managed-plan agreement, or OTA terms control.
After an OTA Booking is confirmed, Roam sends the OTA Guest a pre-stay communication that includes a link to Roam’s Guest Agreement, these Payments Terms, and any applicable lease (for stays subject to Section 1.6 or 5.5). The OTA Guest must affirmatively accept Roam’s Guest Agreement (by clicking to agree, signing electronically, or another affirmative manifestation of consent recorded by Roam) before receiving check-in instructions, the property address, or access credentials. Roam discloses in the OTA listing (where the OTA permits) and in the booking-confirmation message that acceptance of Roam’s Guest Agreement is required for check-in. If an OTA Guest declines to accept the Guest Agreement, the Booking will be canceled and any refund is determined by the applicable OTA cancellation policy; Roam will provide reasonable advance notice of cancellation to the OTA Guest. By accepting Roam’s Guest Agreement, the OTA Guest agrees to these Payments Terms, which are incorporated into the Guest Agreement. Roam maintains a record of each OTA Guest’s acceptance, including timestamp and method.
Where the applicable OTA permits, Roam may collect a Payment Method or authorization hold from an OTA Guest in connection with damage, incidentals, or additional charges, subject to the OTA Guest’s acceptance of the Guest Agreement under Section 9.3 and these Payments Terms. Where the applicable OTA does not permit Roam to collect a Payment Method from the OTA Guest, damage charges, additional cleaning charges, or other post-stay charges related to an OTA Booking are pursued through (i) the applicable OTA’s resolution or claim process, (ii) any Damage Waiver elected by the Host, or (iii) lawful collection efforts by Roam or the Host against an OTA Guest who has accepted the Guest Agreement, as applicable.
Chargebacks and payment disputes initiated by an OTA Guest are handled in the first instance by the applicable OTA in accordance with the OTA’s terms. Roam’s participation in OTA chargeback handling varies by OTA, by integration model, and by the Host’s plan. Among other variations: (i) where the OTA acts as merchant of record and uses its own dispute team, Roam may be required to provide evidence, documentation, or a written response on behalf of the Host, and Roam will use commercially reasonable efforts to coordinate such response; (ii) where Roam acts as merchant of record for an OTA Booking, including through a property-management integration in which Roam or its processor is the acquirer of record, Roam handles the chargeback directly through its processor; and (iii) where the OTA’s terms permit it to reverse, recoup, or deduct chargeback amounts from amounts otherwise owed to the Host or to Roam (as the Host’s agent) after a stay, those reversals will flow to the Host as a deduction from Host Payouts under Section 13. Roam does not guarantee any outcome of an OTA chargeback process and is not responsible for OTA decisions, timing, or evidence requirements. Section 10 applies only to Direct Bookings.
If you have a concern about a charge on a Direct Booking, you agree to contact Roam first and to give Roam a reasonable opportunity to resolve the issue before initiating a chargeback or payment dispute with your card issuer or bank. Nothing in these Payments Terms limits any right you may have under the Fair Credit Billing Act or other applicable law to dispute a charge with your card issuer.
Roam may suspend or terminate your account, cancel pending or confirmed Bookings, and pursue collection of unpaid amounts in accordance with the Terms of Service if a chargeback is decided in Roam’s favor and the Guest does not pay the underlying obligation, or if the chargeback was initiated in bad faith.
If a Host or Roam identifies physical damage to the property, missing items, excess cleaning costs, unauthorized guests, unauthorized pets, smoking, parties or events held in violation of house rules, fines or fees imposed on the Host or Roam as a result of Guest conduct, or other costs caused by the Guest, Roam may submit a damage report to the Guest with supporting evidence (including photographs, receipts, or invoices, where available).
On Direct Bookings, and subject to the notice provisions in Section 11.4, the Guest authorizes Roam (via Stripe) to:
Roam will not charge the Card on File or the Payment Method for damage amounts in excess of the cap in Section 11.2 without the Guest’s specific, additional authorization. Amounts in excess of the cap may be invoiced separately, settled with the Guest by agreement, recovered through insurance, or pursued through other lawful means.
Before withholding any amount from the Security Deposit, and before charging any damage amount above the Security Deposit, Roam will provide the Guest with written notice of the claim, including a description of the alleged damage, the amount claimed, and the supporting evidence on which Roam relies. The Guest has seven (7) calendar days from the date of the notice to respond, except where applicable law requires a longer period (in which case the longer period applies). Roam will determine the validity and amount of the damage charge in good faith after considering any timely response from the Guest. Where the Damage Waiver applies, the Damage Waiver terms govern the determination of relief. For stays subject to residential-tenancy laws under Section 1.6 or 5.5, the notice, itemization, and deduction requirements imposed by applicable law govern and supersede this Section 11.4 to the extent of any conflict.
For OTA Bookings, Roam pursues damage recovery through the channels described in Section 9.4. Where Roam does not hold a Payment Method for an OTA Guest, Roam cannot directly charge a card for OTA-Booking damages. Roam does not guarantee recovery of damages on OTA Bookings. If the channels in Section 9.4 do not produce full recovery, the Host absorbs the shortfall, except as the applicable Host Agreement or managed-plan agreement otherwise provides. Examples include an OTA denying or limiting a claim, the absence of a Payment Method on file, exhaustion or inapplicability of the Damage Waiver, and unsuccessful collection efforts. Roam has no duty to advance or backstop these losses.
Nothing in these Payments Terms limits Roam’s or a Host’s right to pursue recovery under any insurance policy or under any other legal or equitable remedy available to them, including subrogation rights.
The right to receive Payouts, the calculation of Payouts, and the schedule on which Payouts are made are governed primarily by the applicable Host Agreement. This Section 12 sets out general Payout mechanics that apply unless and except as the Host Agreement provides otherwise.
Payouts are made in U.S. dollars to the U.S. bank account the Host has designated as its Payout Method. The default Payout rail is ACH transfer via Stripe Connect. Where Roam permits or elects, Roam may also initiate Payouts by direct ACH outside Stripe Connect or by domestic wire transfer (subject to Section 12.9). Roam selects the Payout rail in its reasonable discretion, taking into account operational, compliance, and timing considerations. The Host is responsible for the accuracy of its Payout Method information, including routing and account numbers and any wire-specific details. Roam and Stripe are not responsible for delays, fees, losses, or misdirected funds caused by inaccurate Payout Method information.
Unless the Host Agreement provides otherwise, Payout timing follows the schedule for the Host’s plan: for RoamCore, no later than two (2) business days after check-in; for managed plans (including Roam+), on the cadence specified in the Host’s managed-plan agreement, which typically follows a pre-set monthly schedule. In all cases, Payouts are subject to the deductions described in Section 13, the holds described in Section 12.6, and the account-setup and verification conditions described in Section 12.12. Payout timing under this Section is measured by Roam’s (or Stripe’s, on Roam’s behalf) initiation of the Payout; actual receipt by the Host depends on the receiving bank, the Payout rail used, and applicable bank cutoff times. Roam is not liable for Payout delays caused by Stripe outages, banking-system disruptions, force-majeure events, regulatory or compliance reviews, or other events outside Roam’s reasonable control, and Payouts delayed for such reasons will be released as soon as reasonably practicable after the underlying cause is resolved.
Stripe Connect is Roam’s default Payout rail. To receive Payouts through Stripe Connect, a Host must establish and maintain an active Stripe Connected Account in good standing and comply with the Stripe Connected Account Agreement entered into directly between the Host and Stripe. Where Roam permits a Host to receive Payouts outside Stripe (for example, certain Roam+ managed-plan Hosts who receive Payouts by direct ACH or by domestic wire under Section 12.9), the Host must complete Roam’s identity-verification, business-verification, beneficial-ownership, taxpayer-information, and other onboarding requirements, which Roam maintains to be equivalent in scope to those imposed by Stripe and applicable law. In all cases, the Host must provide identification documents, beneficial-ownership information, taxpayer information, and any other information requested by Stripe, Roam, or applicable law (collectively, “KYC/KYB”). Roam is in the process of migrating all Hosts to Stripe Connect and may require any Host currently receiving Payouts outside Stripe to establish a Stripe Connected Account on reasonable notice; failure to do so within the period specified in the notice may result in suspension of Payouts under Section 12.12. Roam is not responsible for Payout delays or interruptions caused by Stripe verification, Roam verification, holds, or compliance reviews.
In addition to KYC/KYB requirements imposed by Stripe, Roam may at any time request additional information or documentation from the Host that Roam reasonably determines is necessary to comply with applicable law, prevent fraud, satisfy tax or reporting obligations, evaluate risk, or maintain the integrity of the Roam platform. The Host must respond promptly and in good faith. Roam may suspend a Host’s account, withhold Payouts, or terminate the Host Agreement if the Host fails to provide requested information within a reasonable time, provides materially false or misleading information, or fails to maintain its Stripe Connected Account in good standing.
Roam may delay or hold a Payout if (i) Roam reasonably expects to issue a refund, credit, or rebooking adjustment to the Guest, (ii) a chargeback or payment dispute relating to the Booking is pending, (iii) Roam is reviewing a damage report, fraud signal, or compliance concern, or (iv) the Host’s Payout Method or Stripe Connected Account is incomplete or under review. Holds will be released as soon as reasonably practicable after the underlying matter is resolved, and in any event no later than ninety (90) days after the original Payout date unless an active dispute, investigation, claim, or legal hold remains pending.
If a Payout (whether by Stripe Connect, direct ACH, or wire transfer) is rejected, returned, misdirected, or otherwise not received because of incorrect Payout Method information, a closed or invalid bank account, the Host’s failure to keep its Payout Method information current, or other circumstances within the Host’s control, the Host is responsible for any returned-payment fees, intermediary-bank fees, currency-conversion costs, or FX losses charged by Stripe, Roam’s bank, the Host’s bank, or any intermediary, and Roam may deduct such amounts from the Payout or from any future Payout under Section 13.
Roam’s payment rails, including Stripe Connected Accounts established through the Roam platform, are used solely to process Bookings sourced through Roamstays.com or Roam-connected OTA channels and to make Payouts to Hosts in connection with those Bookings. Hosts must not use, attempt to use, or instruct Roam or Stripe to use Roam’s payment rails for any other purpose, including processing Bookings sourced outside Roam’s channels, processing payments for unrelated services, or facilitating transactions between the Host and any third party. Roam may suspend a Host’s account or terminate the Host Agreement for violations of this Section 12.8.
Roam may, in its discretion, initiate a domestic wire transfer as the rail for a particular Payout. Where Roam elects to initiate a wire for operational reasons (including to remedy a failed ACH, to expedite a payment for risk-management reasons, or to satisfy an internal operational requirement), Roam bears any outgoing wire fee charged by Roam’s bank. Where the Host requests a wire for the Host’s convenience or preference, or where a wire is necessitated by the Host’s failure to maintain a valid ACH Payout Method, the Host bears any outgoing wire fee, intermediary-bank fee, or incoming wire fee, which Roam may deduct from the Payout or invoice to the Host. The Host’s receiving bank may apply additional fees, for which the Host is solely responsible.
For any single Payout of one hundred thousand U.S. dollars ($100,000) or more initiated by wire, Roam will, before initiating the wire, obtain voice confirmation of the wire instructions from an authorized representative of the Host using a telephone number on file with Roam. Roam will not act on changes to a Host’s wire instructions, bank account, or authorized representatives communicated solely by email or other unverified channel; all such changes are subject to verification through a channel of Roam’s choosing. The Host is responsible for keeping its authorized representatives, telephone numbers, and Payout Method information current and accurate, and for notifying Roam promptly of any suspected compromise of its email, account credentials, or bank-account information. Roam is not liable for losses arising from wires or other Payouts initiated based on instructions that Roam reasonably believed to be authentic and that conformed to the verification procedures in effect at the time, including instructions later determined to have been the product of fraud against the Host (such as business-email compromise) where Roam followed its verification procedures.
Roam’s Payout Methods are limited to U.S. bank accounts. Hosts may not designate an international (non-U.S.) bank account as a Payout Method, configure a Stripe Connected Account that pays out to a non-U.S. account, or otherwise direct Roam to make routine or recurring Payouts to a non-U.S. account. Roam may, in its sole discretion and on a strictly exceptional, one-time basis, initiate an international wire transfer to a Host’s non-U.S. account, subject to additional verification, sanctions and OFAC screening, beneficial-ownership review, and any other compliance procedures Roam deems necessary. The Host bears all outgoing wire fees, intermediary-bank fees, currency-conversion costs, FX losses, and incoming wire fees associated with any international wire, which Roam may deduct from the Payout or invoice to the Host. Roam may decline to initiate any international wire for any reason or no reason, and Roam’s election to initiate one international wire does not create any obligation to initiate future international wires or to consider future international-wire requests.
Roam has no obligation to initiate, calculate, or remit a Payout to a Host until the Host has (i) established a valid Payout Method through Stripe Connect or, where Roam permits non-Stripe Payouts under Section 12.4, an alternative Payout Method approved by Roam, and (ii) completed all KYC/KYB, tax, sanctions-screening, and other verification requirements imposed by Stripe, Roam, or applicable law. Until the Host completes these requirements, funds otherwise allocable to the Host will be held by Roam (or by Stripe on Roam’s behalf), without interest except as required by applicable law, and Roam will have no liability for any delay in Payout caused by the Host’s failure to complete account setup or verification. Held funds remain subject to the deductions described in Section 13, including for refunds, chargebacks, and tax obligations attributable to the underlying Bookings. If the Host fails to establish a valid Payout Method and complete required verification within twelve (12) months after the original scheduled Payout date (or such other period as applicable unclaimed-property or other law may require), Roam may treat the funds as unclaimed property and remit them to the applicable state unclaimed-property authority, or otherwise dispose of them as required by applicable law. The Host’s failure to establish a valid Payout Method or to complete required verification does not relieve the Host of its obligations under the Host Agreement to deliver the stay, maintain the Listing, or perform other obligations.
Unless the applicable Host Agreement provides otherwise, Roam deducts the following amounts from a Host Payout, as applicable to the Booking and the Host’s plan:
Where, after a Payout has been made, Roam becomes obligated to issue a refund or credit to a Guest, incurs a chargeback or payment-dispute reversal (including from an OTA), receives a tax assessment attributable to the Booking, or otherwise becomes entitled under these Payments Terms or the Host Agreement to recover an amount from the Host, Roam may (i) net the amount against any future Payout, or (ii) invoice the Host for the amount, payable within fifteen (15) days. Roam will provide the Host with reasonable documentation of the underlying obligation. The Host’s obligation to reimburse such amounts survives termination of the Host Agreement to the extent necessary to give effect to this Section.
Roam issues IRS Form 1099-K or other tax forms to Hosts as required by applicable law. Hosts are solely responsible for the accuracy of taxpayer information they provide and for their own tax reporting and remittance.
If a Guest payment is declined, returned, or fails for any reason, Roam may attempt to recharge the Payment Method, contact the Guest to arrange an alternative payment, suspend or cancel the Booking under Section 5.4, or pursue any other remedy available under these Payments Terms or applicable law.
Roam may set off any amount owed by a Guest or Host against any amount Roam owes that Guest or Host, including by deducting amounts owed from a future Payout or refund, to the extent permitted by applicable law.
Where you provide a U.S. bank account as a Payment Method or Payout Method, the specific authorization for ACH debits or credits is presented to you and obtained at the point of use, in accordance with applicable Nacha rules and other applicable law. At the point of use, the authorization will disclose: (i) the dollar amount of the debit or credit (or, where the amount may vary, the method by which the amount will be determined and any variance tolerance), (ii) the date or frequency of the debit or credit, (iii) the receiver’s name, and (iv) the procedure for revocation. By providing the bank account and completing the authorization at that point, you authorize Roam (directly or through Stripe or another processor selected by Roam) to initiate the disclosed ACH transaction.
Where applicable to your account or your role on the Roam platform (for example, a Host receiving recurring Payouts, or a Guest authorizing recurring installments under Section 5), you authorize Roam (directly or through Stripe or another processor selected by Roam) to initiate ACH debits or credits to the same bank account on the same terms for subsequent transactions of the same type, in the amount or within the variance tolerance disclosed at the original point of use, until you revoke the authorization. If the amount of a future debit will vary from the original authorized amount by more than the disclosed variance tolerance, Roam will provide notice to you at least ten (10) calendar days before the debit, except where applicable law or Nacha rules require a different notice period.
You may revoke this authorization by removing the bank account from your Roam account, providing Roam with written notice at support@roamstays.com a reasonable time before the next debit or credit (and in any event at least three (3) business days before the next scheduled debit), or following the instructions provided in your account or by Stripe. Revocation does not affect transactions already initiated and does not relieve you of any underlying contractual obligation, which Roam may collect by other lawful means.
The bank account you provide must be a U.S. account on which you are an owner or authorized signer. At the time of authorization, you must accurately indicate whether the account is a consumer account (held primarily for personal, family, or household purposes) or a non-consumer (business) account, and you represent that the designation is accurate. Where the account is a non-consumer account, you acknowledge that: (i) the Nacha Operating Rules and applicable law governing non-consumer accounts apply, including a return window of two (2) banking days from settlement, rather than the sixty (60)-day window applicable to consumer accounts; (ii) the protections of the Electronic Fund Transfer Act and Regulation E may not apply to debits from the account; and (iii) you are authorized to act on behalf of the account holder for the purposes of the authorizations under this Section, and your authorization binds the account holder.
Roam may modify these Payments Terms from time to time. Material changes will be communicated by email, by notification on the Roam platform, or through another contact method available in your account, and will take effect no earlier than thirty (30) days after notice, unless a shorter period is required by law or for security reasons. Your continued use of the Roam platform after the effective date constitutes acceptance of the revised Payments Terms. If you disagree with the revised Payments Terms, you may terminate your account and stop using the Roam platform; existing Bookings will be governed by the Payments Terms in effect at the time of Booking, and any cancellation will be subject to the applicable cancellation policy.
Disputes arising out of or relating to these Payments Terms are governed by, and resolved in accordance with, the dispute-resolution and arbitration provisions of the Terms of Service, which are incorporated into these Payments Terms by reference, including any applicable arbitration agreement, class-action waiver, jury-trial waiver, governing-law provision, and venue or forum-selection provision.
Sections that by their nature should survive termination of your account or these Payments Terms will so survive, including authorizations to charge or debit, indemnification, dispute resolution, and limitations of liability under the Terms of Service.
You may not assign these Payments Terms without Roam’s prior written consent. Roam may assign these Payments Terms in connection with a corporate reorganization, merger, sale of assets, or similar transaction, on thirty (30) days’ notice.
These Payments Terms, together with the Terms of Service, the Privacy Policy, the applicable Property Agreement, the applicable Host Agreement (including any managed-plan agreement), the applicable Guest Agreement, any applicable residential lease, the SMS Terms, and any other written agreement between you and Roam, constitute the entire agreement between you and Roam with respect to payments on the Roam platform. In the event of a conflict:
Roam’s performance under these Payments Terms, including the timing of Payouts, refunds, and post-stay charges, may be delayed or suspended by events outside Roam’s reasonable control, including Stripe outages, banking-system disruptions, OTA system outages, acts of God, government actions, and other force-majeure events. Roam is not liable for such delays.
If any provision of these Payments Terms is held unenforceable, the remaining provisions remain in full force and effect.
Roam’s failure to enforce any right or provision is not a waiver of that right or provision.
Nothing in these Payments Terms waives any right that cannot be waived under applicable law, including any non-waivable consumer-protection right.
Questions about these Payments Terms can be sent to support@roamstays.com.
