Terms of Service
Contractual frameworks, clearing protocols, and key governance covenants governing institutional usage of PayFlow infrastructure.
Executing enterprise custom MSAs, bespoke SLA riders, or institutional corridors?
Acceptance & Institutional Scope
Binding terms governing institutional platform access, APIs, and settlement services.
These Institutional Terms of Service ('Terms') constitute a legally binding agreement between PayFlow Technologies ('PayFlow', 'we', 'us') and the enterprise entity, licensed merchant, or developer ('Client', 'Merchant', 'you') accessing our payment infrastructure, developer documentation, sandboxes, and production gateway endpoints.
By authenticating to the platform, generating cryptographic API credentials, initiating payment dispatches, or submitting onboarding inquiries, you affirm that you possess full legal corporate authority to bind your organization to these Terms.
Payment Infrastructure & Rail Provisioning
Capabilities, corridor routing, and technical mechanics provided by PayFlow.
PayFlow provisions non-custodial and custodial financial routing infrastructure designed for high-concurrency payment collection, fiat-to-stablecoin pegged conversion, and physical cash-on-delivery reconciliation across authorized regional corridors.
Specific operational rails include: (a) Local Bank Transfers with automated virtual account allocation and statement matching; (b) Fiat-to-USDT Pegged Settlement with automated treasury routing; and (c) Managed Cash on Delivery (COD) with digital dispatch handshakes.
PayFlow functions as a technical orchestration gateway and settlement facilitator, operating in alignment with authorized regional banking partner nodes and licensed liquidity desks.
Account Security & Confidential Key Governance
Strict protocol governing confidential server-side credentials and authentication.
Upon onboarding verification, PayFlow provisions an API Key and a cryptographically paired Secret Key used to generate HMAC-SHA256 request signatures ('J-Signature').
Both your API Key and Secret Key are strictly confidential server-side credentials. Under no circumstances may either key be embedded in client-side code, single-page applications (SPAs), public GitHub repositories, mobile application binaries, or accessible browser bundles.
The Client maintains sole legal and financial responsibility for all API calls executed under its provisioned credentials. Any compromised credentials must be revoked immediately via the Admin/Client dashboard.
Both API Key and Secret Key are strictly confidential server-side secrets. All API requests must be orchestrated exclusively from secure, server-side infrastructure behind your dedicated IP whitelist.
Acceptable Use & Anti-Financial Crime Policy
Mandatory compliance standards, prohibited industries, and AML mandates.
Clients shall utilize PayFlow services exclusively for legitimate, licensed commercial operations. The platform strictly prohibits transactions associated with unlawful gambling, unlicensed money transmission, sanctions evasion, child exploitation, terrorism financing, or fraudulent credit card churning.
PayFlow enforces real-time transaction monitoring algorithms. We reserve the absolute right to suspend routing, delay settlements, or freeze processing channels if anomalous, fraudulent, or statutory non-compliant transaction velocity is detected.
Clearing Latency, Reserves & Settlement Finality
Execution timelines, rolling reserves, and ledger balance reconciliation.
Settlement timeframes are governed by the specific corridor and payment rail selected: local bank transfers settle within standard banking clearance windows; USDT stablecoin conversions execute with sub-hour finality; and COD batches settle following physical cash courier deposit confirmation.
To mitigate counterparty default, fraudulent chargebacks, or bank clawbacks, PayFlow may implement a risk-adjusted rolling reserve as delineated in your bilateral Merchant Service Level Agreement.
Transactions recorded in the PayFlow double-entry ledger are deemed final once verified against partner banking nodes and confirmed via immutable HMAC-signed webhook delivery.
Fee Schedules, Peg Spreads & Billing Mechanics
Transparent transactional pricing, zero-spread peg policy, and deduction mechanics.
Processing fees are charged on a per-transaction percentage or fixed interchange basis as specified in your Merchant Integration Schedule. For fiat-to-USDT rails, PayFlow enforces a transparent, direct peg model without predatory broker markups.
Platform fees are automatically deducted at the moment of settlement clearance prior to ledger balance crediting. Detailed monthly reconciliation invoices are available directly through the merchant reporting suite.
API Rate Limits, Gateway SLA & Maintenance
System availability guarantees, throughput caps, and scheduled maintenance windows.
PayFlow guarantees a 99.99% monthly operational uptime SLA for core REST API edge ingestion and webhook dispatch services, excluding Force Majeure events or upstream central banking maintenance.
Standard institutional accounts are provisioned with high-concurrency rate limits. Clients must adhere to published burst thresholds and implement exponential backoff algorithms for transient network retries.
Scheduled platform upgrades requiring brief API maintenance are communicated at least forty-eight (48) hours in advance via platform status telemetry.
Intellectual Property & Proprietary Architecture
Ownership of gateway technology, documentation, interfaces, and algorithms.
All intellectual property rights in the PayFlow platform, routing software, smart clearing algorithms, user interfaces, SDK libraries, and documentation remain the exclusive property of PayFlow Technologies.
Clients receive a revocable, non-exclusive, non-transferable license to interface with our APIs solely to process authorized business payments during the active term of their agreement.
Limitation of Liability & Indemnification
Statutory damage caps, mutual indemnity, and upstream rail exclusions.
To the maximum extent permitted under applicable law, neither party shall be liable for indirect, consequential, punitive, or exemplary damages, including lost profits or business disruption.
PayFlow shall not be held liable for settlement delays directly attributable to upstream partner bank network outages, national clearinghouse downtime, blockchain protocol re-organizations, or client credential compromise.
Total aggregate liability arising out of or related to these Terms shall not exceed the total processing fees paid by the Client to PayFlow during the twelve (12) months preceding the incident.
Term, Suspension & Orderly Offboarding
Mutual cancellation protocols and orderly settlement finalization.
Either party may terminate platform services by providing thirty (30) days advance written notice. PayFlow reserves the right to immediately suspend access in the event of material policy breach, insolvency, or regulatory directive.
Upon termination, outstanding cleared balances will be remitted to the Client's verified corporate treasury destination following standard audit reconciliations, subject to statutory rolling reserve release windows.
Governing Law & Neutral Arbitration
Dispute resolution mechanisms and international commercial framework.
These Terms are governed by and construed in accordance with established international commercial law. Any dispute or claim arising out of these Terms shall be resolved via binding international arbitration under the Rules of the Singapore International Arbitration Centre (SIAC).
Arbitration proceedings shall be conducted in the English language before a single neutral arbitrator, and the decision rendered shall be final and enforceable in any court of competent jurisdiction.
Legal Notices & Operational Communication
Official communication channels for statutory notices and contract adjustments.
Formal legal notices must be delivered via registered electronic transmission to our legal and compliance desk at legal@payflow.io.
Operational alerts regarding corridor updates or API version deprecations will be broadcast through the Merchant Dashboard and registered primary technical contacts.
Ready to onboard your platform?
Speak directly with solutions engineering to obtain sandbox credentials and review customized commercial processing terms.