Terms and conditions

1. Provider and applicable agreements

OrkenFlow is the technology brand of Levanta Payments LLC. These general website terms describe our technology-service relationship and responsible use of the site and platform.

Your applicable signed client agreement, order and data processing agreement (DPA) control specifically agreed matters. Applicable mandatory legal rights remain protected. Service access, commercial terms and specific obligations are governed by the executed documents applicable to your account. Website descriptions, inquiry preparation and roadmap statements do not create an executed service agreement or override individually agreed terms.

For current published software pricing, see OrkenFlow pricing; connector options are explained on How connectors work. Your applicable signed agreement or order controls your agreed charges. Website updates do not retroactively amend signed contracts or rates.

2. Technology licence and white-label use

During the applicable contract, the client receives a limited, nonexclusive, nontransferable technology licence within the agreed scope. White-label use is permitted only as authorized by that scope. Sublicensing or resale requires written authorization.

Access is not a sale or assignment of the platform. Payment for subscriptions, integration or development work does not transfer source code or intellectual-property ownership unless a separate written agreement expressly provides otherwise. Clients must ensure their users and any authorized resellers comply with the agreed access and use restrictions.

3. Ownership and client information

Clients retain ownership of their branding, content, business records and customer data. They must have the rights, permissions and lawful basis needed to supply and use those materials and information.

Levanta Payments LLC retains ownership of the platform, master API, connectors, integrations and custom code unless a separate written agreement states otherwise. Any rights needed to process client materials or data to deliver the service are limited by the applicable agreement, documented instructions and data-protection obligations.

4. Technology only; payment-partner responsibilities

OrkenFlow does not receive, hold, control or settle merchant or end-customer funds at any point. Acquiring, payment processing, fund handling and settlement are the responsibility of the relevant PSP or payment provider under its direct agreement.

A connector is a MID banking integration brought by a PSP/Admin and connected to OrkenFlow’s master API. The PSP/Admin assigns the integrated MID to merchants. Shared solution availability, buy rates and commercial terms are agreed directly between the requesting and providing PSPs/Admins. OrkenFlow provides technical connectivity only and is not a party to their agreement.

A software licence is not a payment-services licence or authorization to conduct regulated activity. Clients must determine and maintain the permissions and licences applicable to their own operations; nothing here states that a licence is unnecessary.

5. Client operational responsibilities

Clients maintain the applicable provider contracts, merchant agreements, permissions and licences, and are responsible for lawful merchant activity and their allocated KYC, AML, underwriting and monitoring obligations.

Clients also remain responsible for payment-scheme compliance, their own pricing, merchant communications and support, complaints and disputes, and settlement responsibilities under the relevant direct agreements. Platform review controls and reporting do not replace those obligations or promise automated compliance or approval.

6. Prohibited use

Do not use the website or services to facilitate:

• Unlawful activity, sanctions evasion, fraud or use of stolen card data.
• Exploitation, counterfeit goods or infringement of intellectual-property or other rights.
• Unauthorized access, credential misuse, malware or interference with platform or partner systems.
• Unlicensed regulated services or activity contrary to applicable laws, merchant/provider agreements or payment-scheme rules.

Do not misrepresent your identity, permissions or business activity, or provide data you are not lawfully entitled to process. Applicable written service restrictions may impose additional requirements.

7. Access security and integration cooperation

Protect credentials, API keys and authorized-user access; promptly use the agreed support channel for suspected compromise. Follow the security responsibilities in your contract, including your allocated domain, DNS and SSL configuration obligations. OrkenFlow uses PCI Vault for payment-card tokenization. Card details are stored in PCI Vault and represented by token references for the configured payment workflows. Access to and usage of token references and applicable limited transaction/payment metadata are subject to configured permissions, lawful client instructions and service agreements. Card-data storage is distinct from handling merchant funds; the payment-partner responsibilities above remain unchanged.

Cooperate with integration work by providing accurate documentation, authorized access and testing resources through secure agreed channels. Do not submit credentials through this website’s inquiry form. Readiness and delivery depend on required assets, documentation, access, testing and partner participation.

8. Availability and service commitments

Except for express commitments in a signed agreement, the website and technology are provided as-is and as-available, subject to applicable law. Service levels and support commitments exist only as specified in the applicable signed contract.

We do not guarantee payment processing outcomes, approval rates, provider availability or roadmap dates. Planned capabilities are not current service commitments. Processing and underwriting decisions belong to the relevant partners; technology configuration does not guarantee bank acceptance or merchant activation.

9. Confidentiality and personal data

Each party must protect confidential information according to the signed agreement and applicable law. We apply reasonable safeguards appropriate to the information and service; clients must meet their own confidentiality and security obligations.

Personal-data processing is subject to applicable law, documented lawful instructions and the agreed DPA where relevant. Our Privacy policy explains the distinction between website/business contact handling and instructed platform processing.

10. Suspension, termination and transition

Access may be suspended for security risks, unlawful activity, partner requirements or material breach, consistent with the signed agreement and applicable law. Notice and an opportunity to remedy will be provided when practicable and as required by the contract; urgent protection needs may require prompt action.

Termination, cancellation, notice obligations and data transition follow the applicable signed agreement. Return or deletion of data is subject to the contract, DPA, lawful retention and agreed backup procedures. See our Refund policy for the contract-led review of OrkenFlow service charges.

11. Liability, governing law and disputes

Warranties, liability allocation and indemnities are governed by the executed agreement, subject to rights and obligations that applicable law does not allow the parties to exclude.

Service governing law and dispute resolution follow the applicable signed client agreement. Applicable mandatory rights remain preserved. For service or website questions, contact support@orkenflow.com or your agreed account support/contact channel.