Merchants

Merchant details include comprehensive metadata about merchants, such as their company information, contact details, banking information, and associated sites.

Merchants Endpoints

EndpointLink to Documentation
GET /v1/merchants/{mid}Retrieve the details of a specific merchant.
GET /v1/merchantsRetrieve a list of onboarded merchants.

General Information

The Merchant Management API provides partners with the ability to retrieve detailed information about onboarded merchants. These APIs are RESTful and use standard HTTP methods (GET) to perform operations such as fetching individual merchant details or retrieving lists of onboarded merchants.

Some requests use URL parameters to specify the target merchant (mid), while others support optional query parameters for filtering and pagination.


Endpoints

The sandbox environment is a dedicated space for testing. Experiment freely without impacting production systems. When you are ready for live operations, production credentials will provide access to the operational environment.

❗️

Do not use real-world financial data in the Sandbox environment.


Headers

To interact with the Merchant Management API, include the following headers in your requests:

NameDescriptionRequest TypeValue
authorizationEvery request must be authenticated.GETBearer token
content-typeSpecifies the media type of the resource.N/Aapplication/json

Versioning

The Merchant Management API follows the versioning protocol outlined in the base API documentation.

For example, <https://api.flex-charge.com/v1/merchants/> indicates version 1 of the API.

Backward-incompatible changes will result in a version increment, while minor enhancements and fixes will not. Ensure your implementation can handle API updates, including additional, unspecified fields or varying response sizes.


Errors

The Merchant Management API uses standard HTTP response codes to communicate success or failure. Below is a list of common response codes and their meanings:

Response CodeDescription
200 OKThe request completed successfully.
400 Bad RequestThe request is malformed or missing required parameters.
401 UnauthorizedAuthentication failed. Provide valid credentials to proceed.
403 ForbiddenAccess to the resource is denied.
404 Not FoundThe specified merchant could not be located.
405 Method Not AllowedThe HTTP method used is not allowed for this resource.
500 Internal Server ErrorAn unexpected error occurred on the server.
502 Bad GatewayReceived an invalid response from the upstream server.
503 Service UnavailableThe server is temporarily unable to process the request.
504 Gateway TimeoutThe server timed out while attempting to process the request.