Payment Terms & Conditions
Terms governing the use of Veyro's software orchestration layer, provider integrations, dynamic routing rules, webhook protocols, and zero-custody settlement architecture.
1. Introduction
These Payment Terms and Conditions ("Payment Terms") govern the use of payment-related features, application programming interfaces (APIs), software development kits (SDKs), routing engines, and operational functionality provided through Veyro.
Veyro is a developer-first payment orchestration and payment operations platform that enables businesses to connect and manage their own payment service provider accounts through a unified software layer.
Veyro provides software infrastructure for payment routing, provider integrations, transaction management, payment status tracking, and related operational workflows. These Payment Terms supplement the Veyro Terms of Service and other applicable platform agreements. By accessing, configuring, or initiating payment-related operations through Veyro, you agree to be bound by these Payment Terms.
2. Definitions
Capitalized terms used in these Payment Terms have the specific meanings set forth below:
A business or individual using Veyro's Services.
A Customer that uses Veyro to manage or orchestrate payment operations for its own business, storefront, or platform services.
An individual or commercial entity purchasing goods, subscriptions, or services directly from a Merchant.
A third-party payment gateway, processor, acquiring bank, card network, or financial institution directly integrated with or connected to Veyro.
A payment request initiated by a Merchant or its authorized application through a connected payment provider via Veyro's routing layer.
The software-based coordination of payment requests, dynamic routing configurations, provider integrations, transaction status tracking, and related operational workflows.
A decision by a relevant payment provider, acquiring institution, or issuing bank to approve or decline a payment request.
The process by which an authorized payment transaction is submitted for settlement completion through the relevant payment provider.
The transfer of commercial funds by the relevant payment provider or financial institution directly into the Merchant's designated commercial bank account.
A transaction initiated to return previously collected funds to an End Customer through the relevant connected payment provider.
A formal payment dispute or reversal initiated through a card issuer, bank, payment scheme, or applicable consumer protection mechanism.
Information relating to a Payment Transaction, such as provider references, idempotency keys, timestamps, routing parameters, error codes, and operational status.
3. Nature of Veyro's Services
Veyro provides payment orchestration software and related operational tools. Depending on the Customer's subscription tier, contractual order form, and technical configuration, the Services may include:
The availability of these features depends on the relevant subscription tier, integration specifications, provider capabilities, and technical configuration. Veyro is not an acquiring bank, card network, or money transmitter, and is not a substitute for the Customer's contractual relationship with its connected payment providers.
4. Veyro's Role in Payment Transactions
Veyro operates strictly as a software orchestration layer. Under the intended service architecture:
The Merchant connects its own existing payment service provider account(s) using their direct provider credentials or tokens.
The Merchant configures payment methods, currency mappings, fallback hierarchies, and business routing rules.
The Merchant's application or checkout backend submits a payment request to Veyro's API, accompanied by an idempotency key.
Veyro evaluates configured routing policies and coordinates transmission of the request to the designated connected provider.
The upstream PSP processes the transaction under its own banking rails, risk algorithms, and network clearing rules.
Veyro receives provider status callbacks, normalizes response payloads, and streams webhook notifications to the Merchant.
The payment provider handles financial clearing, chargebacks, and settles net proceeds directly into the Merchant's bank account.
The exact operational responsibilities of each party depend on the integration method and applicable provider agreements. Veyro does not independently guarantee payment authorization, successful settlement, or the availability of any particular payment method.
5. No Custody or Settlement of Merchant Funds
Veyro's intended business model is to provide payment orchestration software rather than act as the holder, escrow agent, or custodian of Merchant transaction funds. Under this model:
- Merchants maintain direct commercial and contractual relationships with payment providers.
- Payment providers process payment transactions and manage acquiring bank settlement flows.
- Payment providers determine authorization, fraud clearance, and settlement outcomes.
- Settlement is executed directly into the Merchant's designated bank account without routing through Veyro accounts.
- Refunds and chargeback debits are initiated through the applicable provider's financial balance.
- Veyro provides software functionality, routing logic, and transaction-related telemetry only.
Veyro does not receive, pool, hold, intermediate, or independently settle Merchant transaction funds. However, the legal and regulatory classification of Veyro's activities depends on actual technical operations, contractual arrangements, data flows, and handling of funds. Nothing in these Payment Terms overrides applicable law or changes the legal classification of an activity where actual facts indicate otherwise.
6. Merchant Responsibilities
Merchants remain fully responsible for their payment activities, commercial offerings, and underlying transactions with End Customers. You represent, warrant, and covenant that you will:
You remain solely liable for all goods, physical and digital services, subscriptions, and commercial promises offered to End Customers.
7. Payment Provider Accounts and Integrations
Merchants may connect supported third-party payment provider accounts to Veyro via API keys, OAuth tokens, or credential handshakes. By connecting any provider account, you expressly confirm that:
- You are legally authorized to access, configure, and bind that merchant account.
- You have accepted and comply with that provider's applicable commercial and technical agreements.
- You have explicit authorization to connect the account to Veyro's orchestration infrastructure.
- All API credentials, secret keys, webhook secrets, and configuration details supplied are accurate and up to date.
- Your utilization of the integration complies with provider rate limits, network tokenization policies, and security mandates.
You are solely responsible for maintaining valid provider credentials and ensuring that secret keys are rotated periodically and never exposed. Veyro may modify, suspend, or discontinue an integration where necessitated by upstream provider API deprecations, security concerns, regulatory restrictions, or contractual obligations.
8. Payment Routing
Veyro provides advanced payment routing functionality that enables Merchants to configure how payment requests are directed across connected providers. Depending on your tier and configuration, routing criteria may include:
The Merchant is solely responsible for establishing, auditing, and maintaining routing rules. Veyro does not guarantee that a particular routing strategy will result in a successful payment, higher authorization rates, lower processing fees, or uninterrupted processing. Routing operations may be impacted by upstream provider outages, unsupported payment methods, network latency, or external bank filtering.
9. Payment Authorization
Payment authorization is determined exclusively by the relevant payment provider, acquiring institution, issuing bank, card network, or applicable payment rail. Veyro transmits authorization requests and relays provider responses through its software layer.
- Veyro does not independently approve, decline, or authenticate payment transactions.
- A successful HTTP 200 API response does not mean that funds have cleared or been settled.
- An authorization does not mean that the transaction has been captured or completed.
- Pending transactions may remain unresolved until the upstream provider delivers an authoritative final status.
- Authorization approvals may be reversed, voided, or subject to post-authorization risk holds by card issuers.
10. Payment Capture
Where supported by connected payment providers, Veyro facilitates capture operations (manual capture, automated auto-capture, or partial captures). The availability and execution of capture depend on provider capabilities, authorization validity windows (e.g. 7-day card hold limits), and payment scheme constraints. Merchants are responsible for ensuring that capture requests are legally authorized, timely, and compliant with upstream provider schedules.
11. Payment Settlement
Settlement is conducted directly between the connected payment provider and the Merchant according to their bilateral commercial contract. Settlement timing, deposit cadences (T+1, T+2, rolling weekly), reserve withholdings, and processing deductions are dictated entirely by the provider.
Veyro has no access to settlement escrow accounts and does not control deposit timelines. Questions regarding settlement delays, rolling reserves, or withheld balances must be escalated directly to the relevant payment provider.
12. Failed, Declined, and Pending Transactions
Transactions may fail, decline, or remain in an indeterminate pending state due to insufficient funds, issuer security restrictions, network timeouts, downtime, or risk blocklists.
A network timeout or HTTP communication failure must never be treated as conclusive evidence that a payment failed. Upstream payment providers may have successfully captured funds prior to the connection interruption. Merchants must verify transaction state via status lookup APIs, reconcile webhook events, and utilize Veyro's supported Idempotency-Key headers before initiating retries to prevent duplicate consumer debits.
13. Payment Retries and Failover
Veyro may offer smart retry and automated failover orchestration to route transactions to secondary providers upon encountering specific soft declines. When configuring retry policies, Merchants must:
- Ensure customer consent covers potential multi-gateway retry sequences.
- Strictly adhere to card network rules regarding retry limits on hard declines (e.g. stolen card, invalid account).
- Configure exponential backoff and timeout thresholds to prevent duplicate authorizations.
- Never configure retries to circumvent fraud filters, regulatory velocity caps, or card network prohibitions.
14. Refunds
Refunds for customer transactions are processed through the connected payment provider holding the original capture. Merchants are responsible for establishing and honoring refund policies, initiating refund requests, and ensuring sufficient merchant balances exist on upstream gateways to satisfy refund debits.
Veyro provides software APIs to dispatch and track refund requests. Actual settlement of refunds to consumer cards is executed by the provider and card schemes. Note: Refunds for direct Veyro SaaS subscription billing are governed separately by the Veyro Refund and Cancellation Policy.
15. Chargebacks and Payment Disputes
Disputes and chargebacks are adjudicated under card scheme guidelines (Visa, Mastercard, RuPay, Amex) and administered by acquiring banks. Merchants are responsible for monitoring dispute queues, submitting proof of fulfillment within strict representment deadlines, and maintaining dispute ratios below scheme thresholds (typically under 0.9%).
Veyro may provide transaction metadata and integration logs to support dispute representment. Veyro does not determine dispute outcomes and is not liable for dispute fees, penalties, or reserve withholdings levied by upstream providers.
16. Transaction Records and Status Information
Veyro displays operational transaction telemetry (references, amounts, currencies, timestamps, latency metrics, error codes, and routing hops) to assist engineering and finance operations.
Information reflected in Veyro depends on upstream data transmitted by providers. Merchants should maintain their own operational logs and treat the connected provider's settlement statement as the authoritative financial record for tax and accounting audits.
17. Webhooks and Event Notifications
Veyro delivers webhook notifications to communicate payment state transitions. To ensure secure and dependable processing, Merchants must:
Validate HMAC cryptographic signatures on all incoming webhooks using your assigned endpoint secret.
Design webhook handlers to gracefully process duplicate delivery events without double-crediting orders.
Rely on event timestamps and state machines rather than delivery order, which may vary across networks.
Never fulfill high-value commercial shipments without verifying final status via Veyro or provider APIs.
18. Fees and Charges
Veyro charges subscription and operational software fees as specified on our pricing page or applicable enterprise order form.
Veyro operates a Bring-Your-Own-Provider (BYOP) model with a 0% transaction cut on merchant gateway volumes. Upstream PSP processing fees (e.g., interchange, gateway cut, international card markup, refund fees) are billed directly by your connected payment providers under your separate merchant contracts. Veyro neither determines nor controls independent PSP fees.
19. Currency and Foreign Exchange
Veyro supports multi-currency transaction metadata where supported by connected providers. Foreign exchange conversions, cross-border settlement rates, and currency conversion fees are executed by the processing bank or PSP. Veyro does not provide currency exchange or guarantee conversion rates.
20. Payment Security and Sensitive Information
Merchants must protect payment-related information and strictly adhere to PCI-DSS standards. You must never transmit, ingest, log, or store sensitive card authentication data through Veyro unless a specific PCI-certified vault integration has been expressly provisioned. Prohibited data elements include:
- Full card verification values (CVV, CVC, CID, CVV2).
- Card PIN blocks or online banking access passwords.
- Unencrypted Primary Account Numbers (PANs) outside tokenized fields.
- One-time passwords (OTPs) and biometric authentication tokens.
Merchants must secure their server infrastructure, enforce TLS 1.3 encryption, and promptly rotate compromised API keys. Veyro reserves the right to immediately suspend endpoints violating data security standards.
21. Fraud Prevention and Risk Management
Veyro provides operational tooling—such as velocity routing rules, provider risk score forwarding, and anomaly alerts—to assist Merchants in mitigating fraud. However, Veyro does not guarantee the detection or prevention of all fraudulent attempts.
Merchants remain solely responsible for configuring fraud screening, implementing 3D-Secure authentication, and monitoring account activity. Veyro must never be utilized to facilitate card testing, transaction laundering, unauthorized billing, or sanctions evasion.
22. Prohibited Payment Activities
Merchants must strictly refrain from using Veyro's orchestration services for any of the following activities:
23. Payment Provider Availability
Third-party payment gateways, acquiring banks, and card networks experience scheduled maintenance, unscheduled outages, latency spikes, and regional service degradations.
While Veyro facilitates dynamic failover routing to mitigate disruptions, Veyro does not warrant continuous, uninterrupted availability of third-party processing networks, which operate entirely outside our direct control.
24. Third-Party Payment Provider Terms
Each connected provider maintains separate terms governing merchant eligibility, prohibited industries, reserves, and security audits. Merchants must review and strictly observe all upstream PSP agreements. If an upstream provider denies or restricts processing for a specific product category, the Merchant must not use Veyro to circumvent that restriction.
25. Regulatory and Legal Compliance
Merchants are responsible for complying with all statutory laws and sectorial mandates applicable to their commercial operations, including anti-money laundering (AML) guidelines, sanctions enforcement (OFAC, UN), the Digital Personal Data Protection Act (DPDP), General Data Protection Regulation (GDPR), and electronic commerce consumer protection rules.
26. Payment Transaction Errors and Technical Limitations
While Veyro commits commercially reasonable efforts to maintain high reliability across our routing and API tier, Veyro does not guarantee:
- Successful authorization or clearing of every submitted payment request.
- Unbroken uptime across all third-party banking networks.
- Instantaneous cross-network status synchronization under degraded ISP conditions.
- Availability of specific local payment methods across all geographic regions.
27. Suspension of Payment Functionality
Veyro reserves the right to restrict, throttle, or suspend payment routing functionality where reasonably necessary to mitigate platform security threats, prevent suspected fraud, address upstream PSP abuse notices, or comply with statutory court orders. Suspension of Veyro routing does not modify or terminate the Merchant's independent contract with its payment provider.
28. Limitation of Veyro's Payment Responsibilities
To the maximum extent permitted under applicable law, Veyro shall not be liable for decisions or operational actions independently executed by issuing banks, acquiring institutions, card networks, or connected PSPs, including transaction declines, account closures, reserve holdbacks, chargeback assessments, or settlement delays.
29. Changes to Payment Services
Veyro may periodically update, refine, or retire payment connectors, SDK methods, or routing algorithms to accommodate provider API versioning, enhance performance, or satisfy regulatory requirements. Material breaking API updates will be accompanied by migration guides and advance notice through developer documentation.
30. Relationship with Other Veyro Policies
These Payment Terms are incorporated into and governed by the wider Veyro compliance ecosystem. They must be read in conjunction with:
31. Governing Law and Disputes
These Payment Terms and any operational disputes arising out of payment orchestration services shall be governed by and construed in accordance with the laws of India, subject to mandatory local consumer rights. Disputes will be adjudicated under the arbitration and dispute resolution frameworks set forth in the Veyro Terms of Service.
32. Changes to These Payment Terms
Veyro reserves the right to amend these Payment Terms to reflect modifications to provider interfaces, legal obligations, or service features. Revisions will be published on our website with an updated Effective Date. Continued use of Veyro following notification constitutes acceptance of the amended terms.
33. Contact Information
For technical, commercial, or compliance questions regarding these Payment Terms, reach out to our dedicated operations and legal teams:
Entity: Veyro Labs Private Limited
Country: India
Registered Office: Bangalore, Karnataka, India
Website: https://veyro.com
Payment Support: support@veyro.com
Billing Inquiries: billing@veyro.com
Legal & Compliance: legal@veyro.com
For specific transaction settlements, chargebacks, or processor-side declines, Merchants should contact their respective connected payment provider.