---
page_title: Other Information
product: lotuspay
platform: web
page_source: https://docs.juspay.io/lotuspay/web/lotuspayjs/other-information
llms_txt: https://docs.juspay.io/llms.txt
product_llms_txt: https://docs.juspay.io/lotuspay/llms.txt
---


# Other Information



After the authorisation process, your customer is redirected back to the return URL provided as a value of `redirect[return_url]`. This happens regardless of whether authorisation was successful or not. If the customer has authorised the source, the `source` object’s status will transition to `submitted` when it is ready to be used in a charge request. If your customer declines the authorisation, the status will remain in `pending` and you should use the Source Withdraw API endpoint to withdraw it if you want to prevent the customer from reusing the same link.

LotusPay populates the `redirect[return_url]` with some parameters - see the Source API section for more details.

_Mobile applications_  The redirect URL can be opened using the device’s native browser or by using in-app web views or containers. To integrate the Source API within a mobile application, provide your application URI scheme as the `redirect[return_url]` value, and pass control back to your app after completing authorisation.

_Testing the redirect process_  When creating a `source` object using your test API keys, you can follow the URL returned in the `redirect[url]` field. This leads to a LotusPay hosted page that displays information about source. Here you can simulate success and error scenarios. Both scenarios redirects you to the URL specified in `redirect[return_url]`.

Once the customer has authorised the source you can create an ACH Debit or subscription using the respective endpoints.

You might like to use our webhook service to be notified of changes in source status.