Business Agreement Template
Proposed template between OKIAS (SMC-PRIVATE) LIMITED (“OKIAS”) and [Customer legal entity] (“Customer”) for business use of the Service.
1. Agreement documents and Service
The final order form should identify the customer, products, scope, catalogue or quoted charges, authorised users and effective date. The Terms of Service, AML / KYC Policy, Privacy Policy, Refund & Credits Policy and, where applicable, an executed DPA form part of the final agreement as stated there. OKIAS provides decision-support; Customer remains responsible for its onboarding decisions and legal obligations.
2. Customer obligations and applicant rights
- Provide required notices, establish valid legal bases and obtain explicit consent where required.
- Use access, supported correction, consent-withdrawal and deletion routes for applicant requests, and maintain appropriate human review and appeal channels.
- Do not misuse, resell without approval, circumvent controls or submit data without authority.
Reusable identity requires applicant authentication and explicit consent for Customer’s specific merchant flow. Customer receives only permitted fields, and verification webhooks are PII-free by default. Every reuse is a separate verification with fresh liveness, a live selfie and any additional selected checks; an earlier approval is not carried forward.
3. Charges and disabled proposals
Verification pricing and billing triggers are catalogue- or quote-controlled. Current AI KYC, Manual KYC and BYOK platform fees consume Credits only on approval; declined, expired and errored verifications do not consume them. Custom contract, setup or implementation fees require an explicit written description and agreement. There is no signing fee.
Additional-customer-attempt charging is DISABLED until owner-approved activation and is not currently charged. The future proposal would include three customer attempts; fourth and later attempts would consume 3 credits only after quote, explicit customer confirmation and actual processing. Refresh, polling, idempotent replay, webhook activity, internal failure and provider failure would not trigger it. No retrospective charges would apply.
KYB scopes and package, stakeholder, registry and provider pricing remain catalogue- and quote-controlled and NOT_FOR_SALE until required approval and activation. An estimate alone authorises no processing or charge.
4. Data processing and providers
The final agreement should identify controller/processor roles, permitted fields, retention configuration, provider and sub-processor processing, international transfers and deletion arrangements by reference to the current Privacy Policy and executed DPA. No data-residency, security-certification or service-level commitment is created by this template.
5. Final negotiated terms
Term, termination, support, confidentiality, intellectual property, warranties, indemnities, liability, notices and governing law must be settled in the final agreement. Contact support@okias.io to begin review. This public template is not an order form and does not activate Service access.