---
page_source: https://juspay.io/in/docs/lotuspay/web/overview/introduction
page_title: Introduction
---


# Introduction  



LotusPay enables businesses to collect recurring payments via NACH Debit physical mandates and eMandates (eNACH). Merchants can use LotusPay via the dashboard or the API.

The LotusPay NACH Debit API is organised around [REST](http://en.wikipedia.org/wiki/Representational_State_Transfer). Our API has predictable, resource-oriented URLs, and uses HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs, which are understood by off-the-shelf HTTP clients. We support [cross-origin resource sharing](http://en.wikipedia.org/wiki/Cross-origin_resource_sharing), allowing you to interact securely with our API from a client-side web application (though you should never expose your secret API key in any public website's client-side code). [JSON](http://www.json.org/) is returned by all API responses, including errors. We have language bindings in Shell (cURL).

/

![Image](https://dth95m2xtyv8v.cloudfront.net/tesseract/assets/lotuspay/LotusPay%20Flows-U8FFy.jpg)
*Mandate Registration Flow*



![Image](https://dth95m2xtyv8v.cloudfront.net/tesseract/assets/lotuspay/LotusPay%20Flows%20(1)-fsSNM.jpg)
*NACH Debit Flow*