Capability Requests

Update capability request

Corrects or adds to the request's kyb_data, and attaches documents. Never changes the status.

kyb_data is shallow-merged into what is stored — top-level keys you send overwrite or add, every other key is kept — and re-validated the way create validates it. Documents attach the same way as on create (multipart/form-data, one files_<purpose> part per document) and are appended to what that key already holds.

During pending_clarification this call alone does not return the request to review — follow it with POST /v1/requests/{id}/resubmit. See the Capability requests API guide.

patch/v1/requests/{id}

Request

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

Path parameters

idstring required

Request ID

Headers

Account-IDstring

Organization ID of a child account to act on behalf of. Requires an enabled linked-transactions relationship in which the authenticated parent FULLY MANAGES that child, and a grant covering this route. Merchant (Basic) auth only.

Request body

Example request

{
  "kyb_data": {
    "business_trade_name": "Acme Home",
    "change_reason": "Rebranding"
  }
}

Response

OK

has_moreboolean

Example response

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

Changes

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