Payment Rail Terms

Effective date: July 2, 2026. These Payment Rail Terms supplement the Monocrat Terms of Service when Monocrat prepares, routes, or executes customer-authorized outbound payment instructions through a supported payment rail.

1. Scope

Monocrat may support accounts payable, vendor, customer, partner, contractor, owner reimbursement, payroll-adjacent, or tax-remittance payment workflows when the relevant provider, legal, custody, tax, payroll, source-evidence, and action-gate requirements are satisfied. These terms apply to payment-rail workflows for your business. They do not govern Monocrat's own subscription billing, which is covered by the Billing Terms.

2. No Custody

Monocrat does not create or maintain a Monocrat-owned wallet, stored balance, pooled customer account, tax reserve, payroll reserve, escrow account, customer-funds ledger, or Monocrat-owned FBO account. Payment instructions may use only a customer-owned funding account, a provider account governed by the customer's and provider's terms, or a manual customer-side bank, payment, or agency action.

If a provider flow would require Monocrat to take custody of customer funds or operate a custody-changing balance model, that flow is blocked until a separate written legal, provider, and human-gate approval exists.

3. Provider Relationship

Moov is the selected initial outbound payment rail adapter where approved and configured. Other rails require a separate source-backed provider decision. Payment providers own only the rail capability they expose. Monocrat owns the product semantics for source evidence, payment recommendations, approval packages, timing recommendations, status normalization, manual fallback, and reconciliation.

You may need to accept provider terms, complete provider onboarding, pass KYB/KYC or underwriting, satisfy funding-account and recipient readiness, and maintain provider access before any payment rail can be used.

For Moov specifically, production money movement requires the applicable Moov production setup, provider agreement and fee-plan state, customer platform-agreement acceptance, account profile and beneficial-owner verification where required, sanctions screening, capability enablement, and underwriting completion before the relevant capability is used. If any of those provider requirements are not complete or current, Monocrat blocks live rail execution and routes the workflow to manual fallback or support review.

4. Owner Approval Required

Monocrat may prepare payment packages, readiness checks, funding impact, recipient information, source evidence, cutoff timing, duplicate-risk checks, and recommended actions. A payment instruction is not submitted unless the verified owner or authorized payment authority approves the exact payment package through an authenticated app/web review flow and the action gate allows the action.

Email, push, app-link previews, or unauthenticated notices may notify or deep-link to review. They do not approve, schedule, submit, reverse, or complete payment instructions.

5. Readiness And Blocking

Monocrat may block payment execution or create manual fallback instructions if source evidence is stale, incomplete, conflicting, or low-confidence; if payment authority is missing; if cash impact is unsafe; if recipient or funding-account readiness is incomplete; if the provider is unavailable; if underwriting, limits, cutoff, capability, webhook, return, reversal, legal, custody, or provider-contract checks fail; or if a payment appears duplicative, fraudulent, unsupported, or otherwise unsafe.

6. Manual Fallback

If live rail execution is unavailable, delayed, unsafe, or unapproved, Monocrat may provide manual customer-side instructions such as bank bill pay, wire, check, provider dashboard, payroll provider, or agency portal steps. You are responsible for executing manual fallback instructions outside Monocrat and for confirming completion evidence before Monocrat marks the workflow fulfilled or reconciled.

7. Returns, Reversals, Failures, And Disputes

Payment rails can fail, return, reverse, be delayed, be rejected, trigger provider review, miss cutoff windows, or require additional recipient, funding, bank, tax, payroll, or compliance information. Monocrat may notify you, create support or review cases, pause related workflows, reconcile provider events, or route to manual fallback. Provider rules, banking rules, network rules, and applicable law may control whether a payment can be cancelled, returned, reversed, corrected, or disputed.

8. Taxes, Payroll, And Professional Review

Monocrat may surface tax, payroll, contractor, owner-payment, or payment classification context, but it does not provide legal, tax, accounting, payroll, employment, banking, or money-transmission advice. You are responsible for professional review and for confirming that payment instructions, recipients, tax forms, withholding, payroll obligations, remittance obligations, and accounting treatment are correct.

9. Fees

Provider, network, bank, return, reversal, wire, same-day, account, chargeback, dispute, or other payment rail fees may apply. Monocrat will disclose Monocrat-controlled fees and estimates where required by the product flow or order form. Provider fees may be governed by your provider account terms.

10. Support

Payment rail questions, failures, returns, reversals, duplicate-risk concerns, disputes, and manual fallback support can be routed through the product support surface or support@monocrat.ai. Payment support is a non-billable control-plane action.