# Home

### Welcome to the Official Browpay Developer Documentation guide. <br>

Browpay is often described as the missing payment aggregator for ecommerce transactions, but in more technical terms, it makes accepting payments for any commodity you are selling on your website or mobile application a walk in the park; where you define the rules of how you get paid while saving your customers the pressure of anxiety after paying and when the product has not been delivered.

Integrating our resources(endpoints) into your website or mobile application offers your customers the freedom to a secured payment experience, and you, as a seller, the flexibility to take charge of sales more conveniently and securely.&#x20;

## Motivation&#x20;

Most ecommerce websites **do not** come with the guarantee that 8 in 10 first-time visitors  will make an actual purchase. However, as much as you would want to  convert your prospective buyers and(or) impress your buyers that you have the best product offering and items in stock, worrying about issues like *what i ordered versus what i got,* returns, moneyback or payment on delivery should be the least of your customers' worries. And yours too as a seller.

## Enough  talk already, So what now!

Take your time to read our Escrow QuickStart guide, if you plan to use Browpay for escrow payments, to understand how we plan to solve problems with ecommerce payments and follow through our outlined breakdown of automated processes.&#x20;

For starters we would love to iterate the following facts:

* This documentation is bound to be updated with fixes concurrently.
* All requests in **Live** and **Test** modes should be made across SSL encrypted or secured connections from your end.
* You are expected to be a developer and have read our [data policy](https://browpay.com/data-policy) and [privacy policy](https://browpay.com/privacy-policy) before you start using our API endpoints.
* You can always reach out to our support channel via a mail to <support@browpay.com> for assistance with integrations.

We cannot wait to see the amazing stuffs you will build with the Browpay API


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.browpay.com/home.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.