Hosted Handoff
Hosted handoff is the ownership boundary in Hybrid Experience. Your product owns the borrower journey until the borrower selects an offer. After that, Aarthik Labs takes over the selected-offer execution inside Hosted Experience.
Use Hosted handoff after the borrower has chosen a specific offerID in your UI.
Handoff Endpoint
This endpoint returns a short-lived hosted_url for the selected offer.
Your back-end should call this endpoint. Your front-end should receive only the URL it needs to open.
Handoff Flow
What Hosted Experience Handles After Handoff
After your app opens the Hosted URL, Aarthik Labs handles the downstream borrower journey. Depending on the lender and product path, this can include:
- offer detail confirmation
- KFS review
- KYC
- bank mandate or e-mandate
- loan agreement and e-sign
- lender redirects
- lender re-entry after external steps
- disbursal progression
- post-disbursal servicing
This is the same hosted execution layer used by Hosted Experience. Hybrid Experience simply enters it later, after the borrower has selected an offer inside your own product.
Opening The URL
Open the returned URL immediately in the borrower browser, webview, or app shell.
Do not:
- store the URL as a long-term resume link
- expose your API key to the front-end
- attempt to reconstruct the Hosted URL client-side
- reuse old Hosted URLs after expiry
If the borrower returns later, call the Hosted handoff endpoint again for the selected offer and open the fresh URL.
Mobile Applications
If your Hybrid journey runs inside a mobile app, the hosted handoff should use the mobile handling documented under the Hybrid Integrations Guide:
- register the mobile bridge before loading hosted screens
- support external lender pages and return behavior
- allow camera, file, and related permissions when required by the journey
- handle exit events cleanly
Read the mobile application docs for the detailed bridge and permission requirements: