Integration and Onboarding Policy
Effective Date: 01 July 2025

We are committed to offering a seamless, secure, and efficient onboarding experience for clients integrating with our platform and services. This Integration and Onboarding Policy outlines the necessary procedures, technical guidelines, and responsibilities that govern the integration of our pay-in (collection) and payout (disbursement) APIs and related services.

By initiating integration with our systems, the client (“you,” “your”) agrees to the terms outlined in this policy.

1. Purpose

This policy is designed to:

• Define the structured process for onboarding new clients to the platform

• Ensure consistent and secure integration with APIs and backend systems

• Establish roles, responsibilities, and expectations for both parties

• Minimize delays and avoid technical misalignment during implementation

• Maintain compliance with security, regulatory, and data protection standards

2. Scope

This policy applies to:

• API Integration for services such as UPI collections, vendor disbursements, salary payments, and rewards (RNR)

• Clients across fintech, eCommerce, SaaS, logistics, and financial service sectors

• All systems interacting with the platform’s backend environment

• Businesses engaging in white-label payment or embedded finance solutions

3. Onboarding Process

a. Initial Assessment

• Evaluation of business model, transaction volume, risk exposure, and technical infrastructure

• Submission of KYC documents, business details, and integration requirements

• Completion of legal agreements (NDAs or service contracts) prior to credential issuance

b. Documentation and API Access

• Provision of API documentation, environment endpoints, Swagger specs, and integration guides

• Sandbox (UAT) environment access for development and testing

• Assignment of unique API keys, client IDs, and secrets after due diligence

c. Integration Testing Phase

• Completion of functional and security testing in the sandbox environment

• Test cases must cover transaction validation, failure handling, webhook callbacks, and data encryption

• Technical support provided via email, video calls, or tickets during this phase

d. Go-Live Approval

• Submission of a Go-Live Request Form after successful testing

• Review and verification by QA and Compliance teams

• Live access to production APIs granted upon final approval

4. Integration Guidelines

a. Technical Requirements

• Compatibility with RESTful API protocols and HTTPS (TLS 1.2 or above)

• JSON-formatted payloads with SHA-256 or equivalent hashing for security

• Endpoints must support stable, low-latency performance from the client’s server

b. Data Protection and Encryption

• All personal or financial data must be encrypted at rest and in transit

• Secure storage of API credentials (e.g., environment variables, vaults)

• Unauthorized use or excessive storage of user data is prohibited

c. Rate Limits and Usage

• Adherence to assigned rate limits to prevent system strain

• Throttling or temporary blocks may apply for overuse beyond contractual limits

• Repeated API errors or spamming will trigger system alerts and audits

5. Roles and Responsibilities

a. Our Responsibilities

• Provide integration guides, test APIs, and relevant documentation

• Maintain server uptime during onboarding and integration

• Conduct routine security updates and infrastructure enhancements

• Offer guidance and troubleshooting through onboarding support staff

b. Client Responsibilities

• Assign a dedicated developer or IT contact for integration activities

• Thoroughly review documentation and follow best practices

• Report integration issues or delays within 24 hours

• Refrain from using production APIs before official go-live approval

6. Support During Onboarding

• Support hours: Monday to Friday, 9:00 AM to 6:00 PM IST

• Assistance available for Postman collections, webhook simulations, and authentication setup

• All communication must be routed via the registered business email

7. Termination of Onboarding

The onboarding process may be suspended or terminated if:

• Technical, legal, or operational guidelines are not followed

• There is suspected misuse of credentials or security compromise

• Required documents or information are not submitted on time

All credentials and sandbox access will be revoked upon termination.

8. Post-Onboarding Support

After onboarding is complete:

• You will transition to regular technical support

• API performance audits may be conducted periodically

• Feature updates and changelogs will be shared via email or the client dashboard

9. Policy Updates

This policy may be revised periodically to reflect:

• Changes in technology or service structure

• Updates to legal or compliance requirements

• Operational improvements or feedback

All updates will be communicated via email or posted on the official platform.

10. Contact Us

For integration-related queries, onboarding assistance, or technical documentation, please contact:

Level 5, ITPL Main Rd, Devasandra Industrial, Bengaluru, Karnataka 560048
Email: cbdo@dotpe.co
Phone: +447563009191