1. Platform service
Experia360 is technology infrastructure for onboarding, integration and operational workflow orchestration. EXPERIA360 PRIVATE LIMITED is not presented as a bank and does not itself guarantee account opening, credit, settlement, clearing or another regulated financial service.
2. Eligibility and authority
An organization and each user must provide accurate information, act within documented authority and maintain current KYC, bank and beneficial-ownership evidence. Registration does not guarantee approval or product activation.
3. Bank and provider services
Bank features depend on separate agreements, technical certification, credentials, limits and provider availability. Displayed bank marks identify configurable profiles only and do not imply endorsement or an active commercial relationship.
4. Security obligations
Customers must protect credentials, use least-privilege roles, maintain approved devices and endpoints, verify beneficiaries, review maker-checker decisions and report suspected compromise promptly. Secrets and OTPs must never be sent through public channels.
5. Acceptable use
The platform may not be used for unlawful activity, sanctions evasion, deception, unauthorized access, credential testing, prohibited goods or services, or attempts to bypass bank, KYC, approval, rate-limit or security controls.
6. Instructions and records
Authorized API and dashboard actions may be treated as organization instructions subject to approval policy and provider acceptance. Idempotency, trace IDs and audit records support operations but do not override bank records or applicable law.
7. Availability and changes
Capabilities may change due to security, law, provider requirements or maintenance. Production service levels, fees, support, confidentiality, liability and termination must be governed by the executed customer agreement rather than this public draft.
8. Governing documents
The executed master services agreement, data processing terms, order form, bank agreements and applicable law prevail where they conflict with public website content. Verified jurisdiction and notice details must be inserted before production use.