| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Check whether the outlet needs AEPS merchant login.
POST https://pay2new.in/apis/aeps/v1/merchantLoginStatus
Headers
| Header | Required | Description |
|---|---|---|
secret | Yes | Your Pay2New API secret. |
outletId | Yes | Pay2New outlet/customer ID returned after successful onboarding; do not send the provider outlet ID. |
Accept | No | Request a JSON response. |
Requests require an active partner account, approved KYC, active wallet and API access, an allowlisted source IP, and the relevant service enabled.
No request body is required.
Usage notes
- login_status 2 means merchant login is required.
- This endpoint returns the detailed result object when available. No request body is required.
Response
Application status is returned in the JSON status field. A successful HTTP response alone does not confirm a successful operation.
| Field | Description |
|---|---|
status | integer: application status, not HTTP status |
message | string |
login_status | integer when returned by service; 1 normal, 2 login required |
result | provider response object |
Provider-dependent fields may be absent or null. status: 2 indicates a failure. For transaction endpoints, status: 3 indicates pending or uncertain processing and requires status confirmation.
Illustrative response:
{
"status": 1,
"message": "Success",
"login_status": 1,
"result": {}
}
Errors
Validation errors can include an errors object keyed by field name. Authentication, outlet, service and other processing errors can return only status and message. Errors are application-level responses; do not rely on an HTTP 400 status.
{
"status": 2,
"message": "Secret Header not found!"
}