#Glossary
#Accounts
This is any organisation using the Bridge, and will always be one of the following types:
| Account type | About |
|---|---|
| Parent Bridge account | When you sign up on the Bridge, you provide an organisation name and create an account against it—this becomes the parent account within which you can integrate with multiple Setu products. |
| Child sub-org account | Child sub-org accounts always belong to a parent organisation’s account. When you want to use any product, such as KYC, eNACH, Account Aggregator, or UPI Setu, you need to set up a child sub-org account that contains details for: 1. Your organisation, either reused from sign-up or a relevant subsidiary, for which KYC will be done. 2. The product category you want to use. Here are a few examples: • Account Aggregator FIUs (Financial Information Users): In the AA ecosystem, entities using financial information, such as personal finance apps or loan providers. • UPI merchants: In the UPI ecosystem, entities collecting payments through UPI. • BBPS BOU billers: Entities collecting repeat payments for their services via BBPS-enabled apps. • BBPS COU agents:Entities offering BBPS-enabled platforms to collect bill payments for BBPS billers. |
| Aggregator account (coming soon) | This is a type of parent Bridge account, that is allowed to resell Setu products to its business customers. The Bridge allows additional features for an aggregator—like viewing combined reports and analytics for all their business customers, or managing their corresponding Parent Bridge accounts with a single login. If you want to become an aggregator, please contact onboarding@setu.co for more details. |
#Product categories, and products
Whenever you set up a child sub-org account, you also choose the product category you want to use it for. Setu’s product categories include Account Aggregator, UPI, BBPS BOU and COU, KYC suite and eSign. These categories have multiple product offerings under them and basically, and you can use the same child org account for using one or more products.
-- Discuss about the asset --
#Product instance
If you want to go live with any product, you can set up a product instance, which is basically a set of forms to collect some details we need to enable your integration, along with the child org’s KYC details, that let’s us asses.
-- Discuss about the assest --
#Good to know
Go live process
The go live process is consistent across product categories and includes the following steps:
- Sign up and create Bridge parent account.
- Set up child sub-org for product.
- Set up product instance and fill in details.
- Submit instance to go live.
- Sign agreements with Setu for pricing and services.
- Get approved and start transacting on production using live credentials.
Test and live credentials
As the name suggests, Test credentials are used on sandbox for testing your integration. These are made available to you after you set up a child org account. You can integrate with any required APIs and use Test credentials for authenticating your API requests, along with the instance ID.
You also have access to Live credentials, but you can only use them for production API calls with a LIVE product instance—that is, an instance ID for which your KYC and integration details have been approved by a Setu admin. These credentials are used for live transactions that you will be charged for as per the pricing agreement signed during on-boarding.
2-factor-authentication (2FA)
2FA makes your account more secure, with a 2-step login process (password and OTP sent to registered email). This can be enabled for your account in two ways:
- During sign up, where you are shown the option to enable to enable 2FA for all users of the org and/or just for yourself.
- After sign up, you can enable 2FA for your organisation, by accessing Settings → Org preferences or for yourself by accessing Settings → Your profile.
Was this page helpful?