Terms of Service

These draft terms are intended, once approved, to govern access to and use of Radok Pay’s website, dashboard, and payment infrastructure. Until counsel issues an approved version, nothing on this page is an offer, acceptance, or binding agreement.

The contracting entity, its legal name, and any related entities will be confirmed by counsel.

Who may open a Radok account, in which jurisdictions, and under what business-verification requirements, will be set by the approved Terms. Live operations on Radok are expected to require business verification (KYB), as described on the product pages.

Radok provides a dashboard in which a business can invite team members and assign roles. Product behavior currently described on the site includes session management, two-factor authentication, and role-aware access — for example, Finance review of payouts and Developer access to API keys and webhooks.

Contractual responsibility for account credentials, authorized users, and activity on an account will be defined by counsel. This draft does not impose those obligations.

Subject to the approved Terms, Radok’s services are expected to include:

• Money in: collections and virtual accounts
• Money out: payouts by bank transfer
• Developer infrastructure: API keys, webhooks, and a sandbox / test environment
• Business operations: KYB, team roles, and security controls

A product overview is on the Products page. These Terms will not expand Radok’s services beyond what the approved product documentation supports.

Collections, virtual accounts, and payouts are product features. Fees, settlement timing, reversals, failed-transaction handling, and related payment rules are not documented in this repository and are not stated in this draft.

Radok provides API keys, webhooks, and a test environment so businesses can build payment flows into their own systems. Technical documentation lives on the Developers page and is not duplicated here.

Rate limits, production access conditions, and prohibited API use will be set in the approved Terms if counsel includes them.

A prohibited-use list has not been approved. This draft does not enumerate restricted activities. Counsel will supply the official restrictions, if any.

Information about Radok’s security and compliance product behaviors is available on the Security page. These Terms do not repeat marketing security copy and do not add certifications or guarantees.

Ownership of the Radok platform, merchant content, trademarks, and any license to use the API will be defined in the approved Terms.

If Radok relies on banks, infrastructure providers, or other third parties to deliver the services, the approved Terms will describe that relationship. This draft does not name processors or allocate their liability.

When Radok may suspend or terminate access, and what happens to funds, data, or API access afterward, will be set out by counsel.

Warranty disclaimers, including any “as is” or availability language, have not been approved. This draft does not disclaim warranties.

Limitation of liability, including any caps, exclusions of consequential loss, or related language, must be drafted by counsel. This page does not limit anyone’s liability.

Indemnification obligations, if any, will appear only in the approved Terms.

How Radok may update these Terms, and any notice Radok will give, has not been determined.

Governing law, venue, and dispute-resolution procedures are not stated in this draft. They will not be inferred from where Radok’s product is used.

Questions about these Terms should be sent through the contact page. No legal email or postal address is published here because none is documented in the project.