Verify the OTP for beneficiary deletion.

Endpoint

POST https://pay2new.in/apis/dmt/v2/beneficiaryDeleteVerify

Authentication

Send both headers on every request:

📘

Account and outlet access

Use an IP address registered on your partner account. The partner account, KYC, wallet, API access and DMT service must be active. The outlet must be enabled for this service.

Send an actual JSON object with Content-Type: application/json.

Request

Use the beneficiary ID and reference from the same deletion request. Check the returned status and then refresh the remitter profile to obtain the current beneficiary list.

Example request

The values below are synthetic. Replace the credential, outlet ID, response references and customer details before sending a request.

curl --request POST \
  --url 'https://pay2new.in/apis/dmt/v2/beneficiaryDeleteVerify' \
  --header 'secret: YOUR_PAY2NEW_SECRET' \
  --header 'outletId: YOUR_PAY2NEW_OUTLET_ID' \
  --header 'Content-Type: application/json' \
  --data '{
  "remitterMobile": "9000000001",
  "otp": "123456",
  "beneficiaryId": "BENEFICIARY_ID_FROM_RESPONSE",
  "referenceKey": "REFERENCE_FROM_PREVIOUS_RESPONSE"
}'

Response

Read the JSON status and message even when the HTTP request completes successfully.

The response data may include the next reference or action. Preserve returned references exactly; do not assume every response has the same nested fields.

📘

OTP and next steps

1 indicates success for the current step, 2 indicates rejection or failure, and 4 means an OTP was sent and the matching verification step is still required. Inspect the message and response data for the next step. A 3 response needs interpretation for this operation; it does not establish that any money was transferred.

Rejections

A missing secret header returns status: 2 and message: "Secret Header not found!". Missing outletId returns "Outlet ID not found!"; an unavailable outlet returns "Invalid OutletId". Invalid or missing JSON returns "Invalid Json!". Field validation failures return "Invalid Parameters" with an errors object containing the field messages. Application failures can be returned in an HTTP-success response.

{
  "status": 2,
  "message": "Invalid Json!"
}

Service-specific response fields and behaviour

After a successful deletion verification, refresh Remitter Profile to confirm the beneficiary is no longer available. Do not infer success solely from message wording. Nested verification data may vary.

Response examples for this operation

Synthetic examples adapted to the Pay2New wrapper. Reference tokens and dates are placeholders. Provider data can omit fields depending on the outcome; the application status and current returned references control the next step.

Deletion verification accepted — illustrative data

{
  "status": 1,
  "message": "Transaction Successful",
  "data": {
    "beneficiaryId": "SAMPLE_BENEFICIARY_ID",
    "validity": "2026-09-26 18:15:00",
    "referenceKey": "REFERENCE_FROM_THIS_RESPONSE"
  },
  "order_id": null
}

Invalid outlet

{
  "status": 2,
  "message": "Invalid OutletId"
}

Service unavailable

{
  "status": 2,
  "message": "Oops, This service is not for you!"
}

Validation error

{
  "status": 2,
  "message": "Invalid Parameters",
  "errors": {
    "remitterMobile": "This required field is missing or invalid."
  }
}

📘

Next step

Refresh Remitter Profile to confirm removal.

See the DMT Integration Flow for all endpoints and Webhook Information for transaction notifications.

Pay2New exposes only status, message, data and order_id: null on a provider-backed result. Upstream statuscode, actcode, timestamp, ipay_uuid, orderid and environment are not top-level fields in this API. Early errors can omit data/order_id.

Provider data-field reference: Instantpay Beneficiary Delete Verify. Use the Pay2New method, headers and request field names on this page; upstream examples use a different envelope.