Home

Welcome to the Official Browpay Developer Documentation guide.

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 escrow payment experience, and you, as a seller, the flexibility to take charge of sales more conveniently and securely.

Motivation

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 QuickStart guide to understand how we plan to solve problems with ecommerce payments and follow through our outlined breakdown of automated processes.

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 and privacy policy before you start using our API endpoints.

• You can always reach out to our support channel via a mail to [e-mail] for assistance with integrations.

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