RTP99 Pay — Payment Service Terms

Effective date: 2026-10-01

RTP99 Pay connects payment functionality with RTP99 Orbit and POS. RTP99 LLC uses Stripe Connect for payment processing. Transaction funds are held and processed through Stripe under the applicable Stripe account arrangements; RTP99 does not provide a separate custody or escrow service. Stripe onboarding, verification, payout, reserve, and risk requirements apply. Your accepted merchant and service agreements govern those services. Product branding does not itself make RTP99 your bank, acquiring institution, or the merchant selling goods to your customers.

Eligibility and onboarding

Availability depends on location, business activity, identity and business verification, risk review, device support, and provider approval. Providers may request additional information, decline or restrict an account, or impose reserves or other risk controls under their agreements. Approval and continued availability are not guaranteed.

Merchant responsibilities

Unless your written agreement expressly provides otherwise, the merchant remains responsible for its products or services, lawful sales, fulfillment, customer support, receipts, accurate descriptors, taxes, required disclosures, and its refund and cancellation policy. Donations require appropriate authorization and accurate representations about the recipient and any tax treatment. Do not process prohibited activity, unauthorized transactions, or transactions on behalf of an undisclosed party.

Fees, payouts, and transaction status

The applicable agreement or account schedule must disclose processing and platform fees, taxes, settlement timing, currency conversion, reserves, and other charges. Authorization is not a guarantee of final settlement. Payouts can be delayed, reversed, reserved, or restricted by provider rules, disputes, compliance checks, bank processing, or other events. Do not advertise guaranteed payouts or instant access to funds unless expressly supported by the contracted service.

Refunds and disputes

Customers should contact the merchant identified on their receipt about the underlying purchase, delivery, or refund. Merchants must follow applicable law, their published policies, and provider rules. Chargebacks, dispute evidence, deadlines, fees, negative balances, and loss allocation follow the accepted merchant and service agreements. Using RTP99 Pay does not eliminate fraud or chargeback risk. Report duplicate or unclear transactions and reconcile provider records before attempting another charge.

Security and PCI responsibilities

Use approved payment interfaces and protect devices, accounts, and access permissions. Do not send full card numbers, verification codes, passwords, or payment secrets through general support channels. Outsourcing processing does not automatically remove the merchant's PCI DSS obligations. Confirm your validation and shared responsibilities with your processor or acquirer. No blanket PCI certification of a merchant's business is implied by this website.

Connected services

Platform manages the services and permissions available to your organization; POS provides the applicable sales workflow. Service configurations, merchant accounts, authentication, and payment integrations remain governed by their existing applications. This marketing website does not execute payments or change those configurations. Mobile and contactless payment features depend on supported devices, regions, provider approval, and applicable platform requirements.

Help and related terms

For account or integration assistance, contact support@rtp99.com with your organization, a non-sensitive transaction reference, time, amount, and currency. For a compromised payment account, also use your processor's official urgent support channel. The applicable privacy notice, acceptable-use policy, provider terms, and signed service agreement also apply. Mandatory rights are preserved.

Authorization, recurring payments, and receipts

Merchants must obtain and retain the authorization required for each payment method and provide clear purchase, recurring-charge, cancellation, and refund disclosures before charging. Do not treat possession of contact details or a previous payment as unlimited authorization. Follow applicable rules for saved payment methods, recurring payments, retries, and revoking authorization. Provide accurate receipts and a customer support channel. ACH, card, and other payment methods can have different authorization, return, and dispute requirements.

Identify the parties before activation

Your onboarding documents must identify the contracting parties, payment provider, merchant of record where applicable, recipient of settlement, and responsibility for refunds, reserves, negative balances, and disputes. Confirm those arrangements before accepting live payments. This website does not promise that RTP99 holds funds, provides escrow or deposit insurance, guarantees settlement, or has a particular financial-services license. The actual service and applicable law determine those obligations.

Software subscription cancellation and underlying merchant purchase refunds are separate processes. See billing and cancellation guidance for an RTP99 subscription; contact the merchant on your receipt for a purchase refund. Do not submit card security codes, full card numbers, or banking credentials to support.

Stripe agreements and RTP99 fees

Use of Stripe services is subject to the applicable Stripe Services Agreement and Stripe Connected Account Agreement. Your RTP99 customer agreement identifies the platform services and agreed markup. Stripe fees and RTP99 fees may be disclosed separately or combined in the agreed price; confirm the complete fee schedule before activation. Stripe processing does not remove the merchant's or RTP99's responsibilities under their respective agreements.

Support-assisted refunds and subscription requests

Submit refund and recurring-subscription change or cancellation requests to support@rtp99.com as a support ticket, with your organization, account email, and a non-sensitive transaction or invoice reference. Requests are reviewed manually and applicable payment or subscription actions are processed through Stripe. A request does not by itself establish refund eligibility, approve a refund, or confirm that a subscription has ended. Ask support for confirmation. The accepted purchase terms and mandatory law determine eligibility, timing, remaining charges, and any refund of platform or processing fees. Stripe processes the action; it does not replace the seller's refund policy.

Default transaction markup and fee refunds

RTP99's default platform markup is USD $0.30 per transaction unless your accepted customer agreement sets a different rate. The agreed markup is additional to Stripe processing fees and any other charges disclosed in your accepted fee schedule. The schedule must identify the applicable transaction types and total pricing before activation; this page does not change a previously agreed rate.

When a transaction is refunded, RTP99's markup and Stripe processing fees are ordinarily not returned to the merchant, unless the applicable agreement, provider adjustment, or law requires otherwise. A refund of the customer's purchase and a refund of merchant processing or platform fees are separate matters. This fee policy does not authorize a merchant to deduct fees from a customer refund when a full refund is legally or contractually required.

For annual RTP99 subscription cancellation and refund requests, see annual subscription and refund terms. An underlying merchant purchase remains subject to that merchant's policy and applicable law.