Begin verification

POST

https://api-dev.myemipay.com/applications/begin-verification

Last modified:2026-09-27 17:56:10

Begin verification

Description: moves started → verifying so KYC is allowed. Calling later steps while still started is the wrong state.

Usage: screen status started, youCanNow action begin_verification. First write after OTP for a new application.

Details: optional body { revision }. Pre-processor also sends If-Match from captured revision.

Next: POST /application/profile (journey update_profile), then PAN KYC.

Auth: Authorization: Bearer {{accessToken}}

Errors: 401 unauthorized | session_expired · 403 Forbidden · 404 Application not found · 409 Revision conflict

Request

Header Params

Body Params application/json

Examples

Responses

🟢200Verification started

application/json

Bodyapplication/json

🟠401Unauthorized

🟠409Revision conflict

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://api-dev.myemipay.com/applications/begin-verification' \
--header 'Authorization: Bearer ' \
--header 'Content-Type: application/json' \
--data '{
  "revision": ""
}'

Response Example

200 - Verification started

{
  "application": {
    "id": "app_1735123456789",
    "reference": "PME-A1B2C3D4"
  },
  "status": "verifying",
  "message": "We are verifying your details.",
  "youCanNow": [
    {
      "action": "update_profile",
      "title": "Update customer profile",
      "submitTo": "/application/profile"
    }
  ],
  "revision": "2"
}

Modified at 2026-09-27 17:56:10

Get current application screen

Verify PAN