PApaymongo
Internal Capability Requests

Process capability request to completion (S2S only)

Transitions request status to processing and writes the approved data to the account. For account_update only the fields and documents named in kyb_overrides are written — omit them and nothing is saved. Optionally change assignee via assignee_email parameter (omit to keep existing assignee, empty string to unassign, or provide valid email to reassign).

post/v1/internal/requests/{id}/process

Request

  • Base URL
    https://api.paymongo.com
  • URL
    https://api.paymongo.com/v1/internal/requests/{id}/process
  • Auth
    HTTP bearer

Path parameters

idstring required

Request ID

Request body

assignee_emailstring

AssigneeEmail is optional. If provided:

  • Empty string ("") or null: unassigns the request (sets AssigneeEmail to nil)
  • Valid email: assigns the request to that email If not provided (nil): keeps existing assignee unchanged (backward compatible)
kyb_overridesobject

KybOverrides names the fields and documents the reviewer approves, and carries the values to approve them with. Accepted on both /process and /complete.

Semantics differ by product, deliberately:

  • account_update: ONLY the keys named here are written to the account. Nil or empty writes NOTHING — the request just moves status. An unchecked field in the reviewer's UI is an unsaved field.
  • every other product: nil means "write all sections from kyb_data" (backward compatible), an empty map skips the organization update entirely, and a populated map overrides those specific fields before the write.

Accepted keys match the internal PATCH endpoint: E-Wallet / Card, Standard Wallet and Account Update take any key naming a real kyb_data PROFILE field, while DOCUMENT keys (files_<purpose>) stay gated to the purposes the product collects. Account Activation and Tax Document keep curated lists. GET /v1/internal/requests/{id} returns the effective list for a request in allowed_kyb_override_keys.

Overrides are folded into the request's kyb_data BEFORE the outbound write, so the reviewer's value is what reaches the account — not the merchant's original. The keys that were actually written come back in applied_kyb_override_keys.

Example: {"business_type": "corporation", "business_address.city": "Manila"}

Example request

{
  "assignee_email": "ops@paymongo.com"
}

Response

OK

has_moreboolean

Example response

{
  "data": {
    "account_id": "acct_01hzy8n3k2b5xq9m4p7r6t8w1v",
    "id": "req_01hzy8n3k2b5xq9m4p7r6t8w1v",
    "product_code": "prd_svc_paymongo_ewallet_gcash",
    "request_type": "onboarding",
    "requester_id": "org_01hzy8n3k2b5xq9m4p7r6t8w1v"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.