diff --git a/api-playground/products.json b/api-playground/products.json index 93ab8886..b2df3a5f 100644 --- a/api-playground/products.json +++ b/api-playground/products.json @@ -30,10 +30,6 @@ "name": "PAN verification", "path": "data/pan" }, - { - "name": "Aadhaar KYC", - "path": "data/okyc" - }, { "name": "BAV Reverse Penny Drop", "path": "data/bav/reverse-penny-drop" @@ -63,10 +59,6 @@ { "name": "Insights", "path": "data/insights" - }, - { - "name": "Auto OKYC", - "path": "data/auto-okyc" } ] } diff --git a/content/data/okyc/aadhaar-redundancy.mdx b/content/data/okyc/aadhaar-redundancy.mdx deleted file mode 100644 index 865c5b45..00000000 --- a/content/data/okyc/aadhaar-redundancy.mdx +++ /dev/null @@ -1,6 +0,0 @@ ---- -sidebar_title: Aadhaar Redundancy -page_title: Redundancy for Aadhaar OKYC -order: 5 -visible_in_sidebar: false ---- diff --git a/content/data/okyc/aadhaar-redundancy/api-integration.mdx b/content/data/okyc/aadhaar-redundancy/api-integration.mdx deleted file mode 100644 index 9665954c..00000000 --- a/content/data/okyc/aadhaar-redundancy/api-integration.mdx +++ /dev/null @@ -1,237 +0,0 @@ ---- -sidebar_title: API Integration -page_title: Aadhaar OKYC Redundancy API Integration -order: 1 -visible_in_sidebar: false ---- - -## Aadhaar OKYC Redundancy API Integration - -The following guide describes the redundancy implementation of our Aadhaar OKYC APIs. Due to intermittent issues on our supply partner's end, we have introduced an Aadhaar Redundancy -API, which uses either supply partner to perform Aadhaar Verification and fetch a user's Aadhaar details, depending on uptimes. -You will need the following 2 APIs— - -- **Create Aadhaar Verification Request**—This lets you initiate a verification request. -- **GET Aadhaar Verification Details**—This lets you check the status associated with the verification request, and if complete, fetch the verification details. - -Here are the URLs you would need for this integration— - -- Sandbox—`https://dg-sandbox.setu.co` -- Production—`https://dg.setu.co` -- Headers—Contact Setu for providing the credentials required to successfully call Setu APIs. This contains: - - `x-client-id` - - `x-client-secret` - - `x-product-instance-id` - -
-
- You get an id
associated with the Aadhaar
- verification request, which you can use to check verification
- status in the Get Aadhaar Verification Details
API.
-
- If status
is pending.
-
- If status
is complete.
-
Internal Server Error.
-Upstream Service Error.
-
-
- Use the request id
in this response for all
- subsequent API calls.
-
-
- id
. Your customer has successfully received an OTP.
-
-
If an incorrect aadhaar number is filled in by your customer, they would need to call the verify AUTO-OKYC request API again.
- > - ), - }, - { - key: "3", - label: "400", - content: ( - <> -
-
status
associated with request id
is failed
.status
associated with request id
is complete
, i.e, this request has already been completed. This also means that the Aadhaar number provided with this request id
is already processed and is confirmed as either verified or incorrect. You should instead call the Get AUTO-OKYC request status API to proceed.
-
- id
provided by you was not found—it is either incorrect or has expired, i.e, is past the time of the validUpto
time in the Create AUTO-OKYC request API’s response. Create a fresh request to do KYC for the same customer.
-
-
-
- id
and correct otp
as per UIDAI.
-
otp
is incorrect, you would need to redirect your customer to the screen you use to collect OTP. Your customer can retry entering the same OTP up to 3 times.
-If the status
of the AUTO-OKYC request is complete
, Setu will respond with details from your customer’s Aadhaar XML file.
If the unmasked phone and email of the user are available from UIDAI, we return it in the userProfile
field of the response. userProfile
contains
- two fields, unmaskedPhone
and unmaskedEmail
.
-
status
associated with request id
is complete
, i.e, this request has already been completed. This also means that the Aadhaar number provided with this request id
is already processed and is confirmed as either verified or incorrect. You should instead call the Get AUTO-OKYC request status API to proceed.
- id
provided by you was not found—it is either incorrect or has expired, i.e, is past the time of the validUpto
time in the Create AUTO-OKYC request API’s response. Create a fresh request to do KYC for the same customer.
-
-
status
is incomplete
, call the{" "}
- Complete AUTO-OKYC request API with a correct{" "}
- otp
input to mark request status
as{" "}
- complete
.
-status
{" "}
- associated with a particular request id
.
-
- status
associated with this AUTO-OKYC request id
is complete
.
-
- When status
is complete
, you will get
- all customer KYC details included in the XML, and the URL for
- the zip file.
-
If the unmasked phone and email of the user are available from UIDAI, we return it in the userProfile
field of the response. userProfile
contains
- two fields, unmaskedPhone
and unmaskedEmail
. If both are not available, userProfile will be an empty dictionary.
- status
associated with this AUTO-OKYC request id
is incomplete
.
-
-
- id
is expired
, ie, is past the time of the provided validUpto
time. You would need to create a fresh request to do KYC for the same customer.
-
You will get status
as expired
.
-
-
- Use the request id
in this response for all
- subsequent API calls.
-
-
-
- As part of the response, you will receive a captchaImage
that is base-64
encoded. This image data is passed on to you by Setu, after we receive it from UIDAI. You would need to convert this to an image and display it on subsequent screens to let your customer enter text from the captcha.
-
captchaRetriesRemaining
indicates the number of times you can call this API with the same request id
to generate a new captcha.
- status
associated with request id
is complete
, i.e, this request has already been completed.
-
-This also means that the Aadhaar number provided with this request id is already processed and is confirmed as either verified or incorrect. You should instead call the Get OKYC request status API to proceed.
-
- id
.
-
-
id
upto 5 times, including the first captcha fetched.
-
- id
provided by you was not found—it is either incorrect or has expired, i.e, is past the time of the validUpto
time in the Create OKYC request API’s response. Create a fresh request to do KYC for the same customer.
-
-
- id
and correct captchaCode
. Your customer has successfully received an OTP.
-
-
If an incorrect captcha text is filled in by your customer, they would need to get a new captcha and try again. You would need to call the Initiate OKYC request API again to get a fresh captcha image to display it to your customer.
-id
upto 5 times, including the first captcha that was fetched.
-
-
id
. Call the Initiate OKYC request API to proceed.status
associated with request id
is complete
, i.e, this request has already been completed. This also means that the Aadhaar number provided with this request id
is already processed and is confirmed as either verified or incorrect. You should instead call the Get OKYC request status API to proceed.
- id
provided by you was not found—it is either incorrect or has expired, i.e, is past the time of the validUpto
time in the Create OKYC request API’s response. Create a fresh request to do KYC for the same customer.
-
-
shareCode
on
- your end, as Setu will not store it and will simply pass on the value you
- provide to UIDAI.
-
- id
and correct otp
as per UIDAI. Additionally, it has the correct shareCode that was previously set by your customer.
-
otp
is incorrect, you would need to redirect your customer to the screen you use to collect OTP. Your customer can retry entering the same OTP up to 3 times.
-If you pass the correct value of the shareCode
to Setu, and if the status
of the OKYC request is complete
, Setu will respond with details from your customer’s Aadhaar XML file.
If the value of the shareCode
is incorrect, the status
associated with this OKYC request id
will remain in incomplete
state. Please retry the API to move the status
to complete
.
If the unmasked phone and email of the user are available from UIDAI, we return it in the userProfile
field of the response. userProfile
contains
- two fields, unmaskedPhone
and unmaskedEmail
.
-
id
. Call the Initiate OKYC request API to proceed.status
associated with request id
is complete
, i.e, this request has already been completed. This also means that the Aadhaar number provided with this request id
is already processed and is confirmed as either verified or incorrect. You should instead call the Get OKYC request status API to proceed.
- id
provided by you was not found—it is either incorrect or has expired, i.e, is past the time of the validUpto
time in the Create OKYC request API’s response. Create a fresh request to do KYC for the same customer.
-
-
status
is incomplete
, call the{" "}
- Complete OKYC request API with a correct otp
{" "}
- input to mark request status
as complete
.
-status
{" "}
- associated with a particular request id
.
-
- id
and 4-digit{" "}
- shareCode
.
-
- When status
is complete
, you will get
- all customer KYC details included in the XML, and the URL for
- the zip file.
-
If the unmasked phone and email of the user are available from UIDAI, we return it in the userProfile
field of the response. userProfile
contains
- two fields, unmaskedPhone
and unmaskedEmail
. If both are not available, userProfile will be an empty dictionary.
- id
-
- When status
is complete
, you will get
- the URL for the zip file. You can use the share code to decrypt
- the zip file and access the Aadhaar XML file.
-
- status
associated with this OKYC request id
is incomplete
.
-
-
- id
is expired
, ie, is past the time of the provided validUpto
time. You would need to create a fresh request to do KYC for the same customer.
-
You will get status
as expired
.
-
- redirectURL
and Setu has processed your request
- successfully.
-
response.url
as the link.
-
- Share a redirectURL
to send your customers to,
- after the OKYC journey is completed by your customer, on Setu
- screens.
-
- You will get a unique URL from Setu—OKYC details will be - collected here—where you will have to redirect your customer. -
-
- url
is a Setu generated URL, that is unique to a
- particular request id
. This is where you should
- redirect the customer to, to complete their KYC. You can
- generate a new url as many times as you want without additional
- charges.
-
- redirectURL
-
-
-
- The screen on the left shows Setu’s UI. This is what your customers see - when filling in details to complete their OKYC. -
-redirectURL
that you provided in the Create OKYC request API.
- Setu will append the share code provided by the customer, and the
- request id
to the provided URL. You should store both these
- values on your system to access the XML file at a later stage.
- status
{" "}
- associated with a particular request id
.
-
- id
and 4-digit{" "}
- shareCode
.
-
- When status
is complete
, you will get
- all customer KYC details included in the XML, and the URL for
- the zip file.
-
- id
-
- When status
is complete
, you will get
- the URL for the zip file. You can use the share code to decrypt
- the zip file and access the Aadhaar XML file.
-
-
- id
is expired
, ie, is past the time of the provided validUpto
time. You would need to create a fresh request to do KYC for the same customer.
-
You will get status
as expired
.
-
- Simply redirect your customer to pre-built screens with carefully designed - UX, and collect Aadhaar details. Theme screens to match your brand. Look - at the{" "} - - pre-built screens guide - {" "} - to proceed. -
-- Integrate directly with our APIs and build your own UI. Look at the{" "} - - API integration guide - {" "} - to proceed. -
-