Philippines Social Security sandbox

Sandbox payloads for the Stateless Social Security endpoint.

POST /api/v3/verifications/philippines/social-security-passthrough

When your account is in sandbox mode, these payloads return the outcomes shown below. Any other valid payload is answered as a no-match — HTTP 200 with isValid set to false. Values are case-sensitive. transactionId and createdAt are generated per request, and metadata is echoed back from your request. See Sandbox introduction for the full matching rules.

Verified

VERIFIED — sample 1

Request

{
  "crnSsNumber": "0111111111"
}

Response — HTTP 200

{
  "success": true,
  "message": "Philippines Social Security processed successfully",
  "data": {
    "isValid": true
  },
  "verificationStatus": "VERIFIED",
  "verificationStatusCode": 3,
  "transactionId": "<uuid generated per request>",
  "verificationType": "philippines_social_security",
  "createdAt": "<UTC timestamp of the request>"
}

VERIFIED — sample 2

Request

{
  "crnSsNumber": "0222222222"
}

Response — HTTP 200

{
  "success": true,
  "message": "Philippines Social Security processed successfully",
  "data": {
    "isValid": true
  },
  "verificationStatus": "VERIFIED",
  "verificationStatusCode": 3,
  "transactionId": "<uuid generated per request>",
  "verificationType": "philippines_social_security",
  "createdAt": "<UTC timestamp of the request>"
}

Rejected

A rejection is a completed verification, not an error: success is true and HTTP status is 200. In live mode a rejection is billed.

REJECTED — sample 1

Request

{
  "crnSsNumber": "0999999999"
}

Response — HTTP 200

{
  "success": true,
  "message": "Philippines Social Security processed successfully",
  "data": {
    "isValid": false
  },
  "verificationStatus": "REJECTED",
  "verificationStatusCode": 1,
  "transactionId": "<uuid generated per request>",
  "verificationType": "philippines_social_security",
  "createdAt": "<UTC timestamp of the request>"
}

REJECTED — sample 2

Request

{
  "crnSsNumber": "0888888888"
}

Response — HTTP 200

{
  "success": true,
  "message": "Philippines Social Security processed successfully",
  "data": {
    "isValid": false
  },
  "verificationStatus": "REJECTED",
  "verificationStatusCode": 1,
  "transactionId": "<uuid generated per request>",
  "verificationType": "philippines_social_security",
  "createdAt": "<UTC timestamp of the request>"
}

REJECTED — Not verified, unmatched payload fallback

Request

{
  "crnSsNumber": "0555555555"
}

Response — HTTP 200

{
  "success": true,
  "message": "Philippines Social Security processed successfully",
  "data": {
    "isValid": false
  },
  "verificationStatus": "REJECTED",
  "verificationStatusCode": 1,
  "transactionId": "<uuid generated per request>",
  "verificationType": "philippines_social_security",
  "createdAt": "<UTC timestamp of the request>"
}

This number matches no documented scenario, so it takes the no-match fallback — identical to the documented rejections above apart from transactionId and metadata. Fire it once to confirm that an unknown number never reaches the live SSS source.

Validation failures

All validation failures return HTTP 400 with code set to VALIDATION_FAILED and the same message; only errors differs. Validation runs before any fixture matching, so these behave identically in sandbox and live. transactionId is null and no transaction row is written.

VALIDATION_FAILED — Number missing

Request

{
  "crnSsNumber": ""
}

Response — HTTP 400

{
  "success": false,
  "code": "VALIDATION_FAILED",
  "message": "The request could not be validated. Please check the submitted fields.",
  "errors": {
    "crnSsNumber": ["The crn ss number field is required."]
  },
  "transactionId": null,
  "verificationType": "philippines_social_security",
  "createdAt": "<UTC timestamp of the request>"
}

VALIDATION_FAILED — Number not a string

Request

{
  "crnSsNumber": 111111111
}

Response — HTTP 400

{
  "success": false,
  "code": "VALIDATION_FAILED",
  "message": "The request could not be validated. Please check the submitted fields.",
  "errors": {
    "crnSsNumber": ["The crn ss number field must be a string."]
  },
  "transactionId": null,
  "verificationType": "philippines_social_security",
  "createdAt": "<UTC timestamp of the request>"
}

Send crnSsNumber as a JSON string, not a number.

VALIDATION_FAILED — Trust flow fields sent to a stateless endpoint

Request

{
  "crnSsNumber": "0111111111",
  "trustFlowId": "anything"
}

Response — HTTP 400

{
  "success": false,
  "code": "VALIDATION_FAILED",
  "message": "The request could not be validated. Please check the submitted fields.",
  "errors": {
    "trustFlowId": ["The trust flow id field is prohibited."]
  },
  "transactionId": null,
  "verificationType": "philippines_social_security",
  "createdAt": "<UTC timestamp of the request>"
}

trustFlowId and trustValidationId are prohibited on stateless endpoints. Sending either is a validation failure, not a silently ignored field.

Source unavailable

FAILED — SSS source unavailable, sample 1

Request

{
  "crnSsNumber": "0000000000"
}

Response — HTTP 500

{
  "success": false,
  "code": "PH_GOV_UNAVAILABLE",
  "message": "The Philippine government source is currently unavailable. Please try again later.",
  "verificationStatus": "FAILED",
  "verificationStatusCode": 6,
  "transactionId": "<uuid generated per request>",
  "verificationType": "philippines_social_security",
  "createdAt": "<UTC timestamp of the request>"
}

There is no data key at all. The envelope treats code and data as mutually exclusive, so a coded failure drops data rather than emitting an empty object. Branch on code, not on the presence of data.

FAILED — SSS source unavailable, sample 2

Request

{
  "crnSsNumber": "0000000001"
}

Response — HTTP 500

{
  "success": false,
  "code": "PH_GOV_UNAVAILABLE",
  "message": "The Philippine government source is currently unavailable. Please try again later.",
  "verificationStatus": "FAILED",
  "verificationStatusCode": 6,
  "transactionId": "<uuid generated per request>",
  "verificationType": "philippines_social_security",
  "createdAt": "<UTC timestamp of the request>"
}

Account-level responses

Two further responses are not specific to this endpoint. A missing or invalid Authorization header returns HTTP 401, and an account without the philippines_social_security plan returns HTTP 403 — both enforced in sandbox exactly as in live. See Sandbox introduction for their envelopes.

Stateless API Sandbox

Australia DVS

Philippines Government

Document OCR

Philippines Social Security sandbox

Verified

Rejected

Validation failures

Source unavailable

Account-level responses

​Verified

​Rejected

​Validation failures

​Source unavailable

​Account-level responses

Verified

Rejected

Validation failures

Source unavailable

Account-level responses