Merchant Platform and Payment Terms

1. Platform authority

The merchant appoints Recurrify as its technology service provider and instruction agent for the CRM, checkout, subscription, vault, routing, retry, reporting, dispute, and payment functions the merchant enables or uses. Recurrify may transmit those instructions to the merchant's processors, gateways, banks, commerce providers, and other configured services.

Workspace owners may grant granular permissions to other users. Actions performed through an authorized account, API credential, integration, or processor credential are treated as merchant instructions. The merchant is responsible for user access, credential security, configuration review, and prompt revocation of access that is no longer appropriate.

2. Merchant accounts and funds

The merchant supplies and controls its own merchant identification numbers, gateway accounts, processor relationships, settlement accounts, descriptors, reserves, and credentials. Recurrify is not the merchant of record, a bank, an acquirer, or the owner of settlement funds unless a separate signed agreement expressly says otherwise.

Processors and financial institutions may approve, decline, hold, reverse, reserve, suspend, fine, or terminate processing under their own rules. Recurrify does not guarantee authorization, settlement, availability, or release of funds.

3. Routing, vaulting, retries, and merchant-initiated payments

The merchant expressly authorizes Recurrify to select among enabled merchant MIDs, submit and resubmit transactions, apply published routing rules, run merchant-configured delayed cascades, perform dunning, reconcile uncertain outcomes, and stop or hold attempts when a duplicate-charge or security risk is detected.

When the merchant enables reusable payment methods or recurring billing, the merchant authorizes later merchant-initiated and stored-credential transactions using the vaulted account data or provider reference without collecting CVV again. CVV is used only for the initial customer-present transaction and is never stored. A configured delay schedule is snapshotted when a payment operation begins and controls its later attempts.

The merchant must obtain and retain all customer consent, notices, mandates, and proof required for stored credentials, recurring charges, trial conversion, amount or timing changes, resubmission, and cancellation.

4. Merchant representations and prohibited activity

The merchant is solely responsible for its products, claims, prices, taxes, fulfillment, customer service, refunds, cancellation practices, privacy disclosures, sanctions screening, and compliance with law, processor agreements, card-network rules, and advertising requirements.

The merchant will not use Recurrify for unlawful, deceptive, unauthorized, abusive, or network-prohibited activity; submit a transaction without a valid commercial basis and customer authorization; disguise the merchant or transaction; factor another party's payments; test stolen credentials; or instruct Recurrify to evade a processor control.

5. Merchant risk allocation

To the maximum extent permitted by law, the merchant assumes the commercial and operational risk of transactions and account configuration, including declines, retries, duplicate submissions caused by merchant systems, refunds, returns, fraud, disputes, chargebacks, retrieval requests, reserves, negative balances, processor fees, assessments, fines, credential compromise, and processor or bank action.

The merchant is responsible for reviewing payment operations, reconciliation flags, dispute deadlines, routing versions, user activity, and processor statements. The merchant must immediately report suspected duplicate processing, account takeover, credential exposure, or an incorrect configuration and must not resubmit an indeterminate payment until it is reconciled.

To the maximum extent permitted by law, the merchant will defend, indemnify, and hold Recurrify and its personnel harmless from third-party claims, losses, assessments, penalties, and reasonable costs arising from the merchant's products, instructions, customer relationship, breach of these Terms, or violation of law or network rules.

6. Recurrify safeguards and discretion

Recurrify may reject, pause, limit, reconcile, or block any instruction; disable a route or credential; require additional evidence; preserve records; or suspend a workspace when reasonably necessary for security, legal compliance, network compliance, platform integrity, suspected fraud, or prevention of duplicate or unauthorized charges.

No setting, permission, risk acceptance, or merchant instruction requires Recurrify to perform an unlawful act, violate card-network or processor requirements, store prohibited authentication data, conceal an uncertain payment outcome, or remove a safety control.

7. Data and security

The merchant will provide only data it is authorized to provide, will maintain accurate privacy notices, and will not place full card numbers, CVV, authentication secrets, or other prohibited sensitive data in CRM notes, dispute descriptions, URLs, reports, or support messages.

Recurrify may use subprocessors to provide hosting, authentication, communications, payment connectivity, and other platform functions. Each party remains responsible for the security obligations that apply to it.

8. Availability and beta infrastructure

The service may use free-tier or scale-to-zero infrastructure during an early-access period and may experience cold starts, quotas, provider outages, or scheduled maintenance. Unless a signed order states an SLA, the platform is provided without an uptime commitment. The merchant must maintain business-continuity procedures and access to its processor portals.

9. Disclaimers and limitation

To the maximum extent permitted by law, the service is provided as available and without implied warranties. Recurrify is not liable for indirect, incidental, special, consequential, exemplary, or punitive damages, loss of profit, loss of goodwill, or processor, bank, network, or customer decisions.

Nothing in these Terms excludes responsibility that cannot lawfully be excluded, limits a person's non-waivable rights, or transfers to the merchant a legal duty that applicable law places exclusively on Recurrify. Any liability cap, fees, governing law, and dispute forum stated in a signed order or master agreement also apply.

10. Versioning, evidence, and updates

Recurrify records the accepted Terms version, document digest, account, user, timestamp, network address, and user agent as evidence. Acceptance applies account-wide; individual payment routes do not require separate waivers.

A material update will receive a new version and may require a workspace owner to accept it before continued use. Configuration snapshots and previously initiated payment operations may continue under the version and instructions recorded when they began, where technically and legally appropriate.