📄️ User registration
To implement user registration, you can follow the flow outlined below.
📄️ Login & Authentication
The Tango platform supports multiple authentication methods and two-factor authentication (2FA) providers. The authentication flow varies based on the endUserTwoFactorProvider value from frontendConfiguration.
📄️ Frontend Configuration
The Frontend Configuration provides essential settings and parameters that control the behavior of your Tango application. This configuration should be fetched before initializing key features like authentication, registration, and transaction flows.
📄️ Manage recipients
To implement recipients management, you can follow the flow outlined below.
📄️ Flags & Tickets
Our system employs flags to monitor user behaviors, and depending on predefined limits, it either provides additional or limits existing functionalities. Every flag can be linked to a corresponding ticket, facilitating communication between managers and users to address and resolve issues.
📄️ KYC Verification
The KYC (Know Your Customer) verification process can be triggered at any point during user registration or account usage. When a KYC flag is raised, users must complete identity verification before continuing with certain operations.
📄️ Inbounds
An inbound represents a payment service that enables users to deposit funds into the Tango system to support their transactions.
📄️ Transactions
Create transaction
📄️ Dynamic Forms
Dynamic forms based on configuration refer to the ability to create and customize forms dynamically by using configuration files or settings, rather than hardcoding the form structure in the source code. This approach allows for more flexibility and easier maintenance of forms, especially in situations where form requirements may change frequently.