SFSimpli-FI Pay

Simpli-FI Pay Pilot Terms of Use

Readiness date: 2026-06-23.

These pilot/readiness terms are for counsel, store-review preparation, and the public terms page. Final production language still requires counsel approval before public store submission or live money movement.

Current status

Simpli-FI Pay is in controlled sandbox, store-review, and pilot preparation. Live ACH transfers, recurring money movement, and direct QuickBooks writeback must not be treated as generally available until provider approval, counsel review, production authentication, durable encrypted storage, support operations, and verified client payee facts are complete.

Paid app access

Simpli-FI Pay is intended to be sold as a one-time paid app download. The app does not require a payer subscription. Store commissions, store refunds, taxes, regional pricing, family sharing, and platform payment rules are controlled by Apple or Google as applicable.

External payment costs

The one-time app purchase does not remove costs charged by banks, ACH operators, payment processors, payees, or other financial-service providers. Any applicable ACH, return, insufficient-funds, expedited-payment, processor, or bank charges must be disclosed by the relevant party.

Verified payment requests

Users may use approved builds to review or rehearse verified payment requests created by approved payees. When production money movement is enabled by the release owner, a QR code or link should resolve to a payment request object, not raw bank-account or routing data. Stale, paused, cancelled, expired, already-paid, draft, or unverified requests should not be payable.

ACH authorization

Before any live payment is submitted, the payer must review and authorize the amount, payee, linked account, timing, and recurrence details. For any approved recurring schedule, the payer must receive the recurrence terms and a route to cancel future payments before the next scheduled debit.

Prohibited uses

Production use should prohibit:

Refunds, returns, and support

ACH returns, refunds, reversals, disputes, and recurring-schedule changes are subject to payment-network rules, banking partner requirements, payee policies, and applicable law. Users should contact support with the receipt ID, payee name, amount, and date.

No production transfers in review builds

Store-review and demo builds should use mock or Plaid sandbox rails unless a release owner intentionally enables production money movement with approved credentials, legal clearance, and partner approval.

Production launch gates

Before these terms are published for store submission, complete counsel review, add entity details, add payment-partner terms, add final dispute/refund language, add jurisdiction and arbitration terms if appropriate, and deploy the terms at the URL configured in the mobile app.