Changelog
Back to All
Added

Introduce structured rejection and resubmission mechanism for VA opening

August 27th, 2026 by Lauren
  • Effective Date: 2026-08-27 (UTC+8)
  • Scope: VA / BaaS

Added

[API] Get VA rejection records

[API] Resubmit VA attachment

This update introduces a fully structured rejection and resubmission mechanism for the OpenAPI VA account opening flow[cite: 5]. When a VA application submitted via the OpenAPI is rejected by compliance (requiring supplemental or modified materials), the system will issue structured pending tasks broken down by attachment, rather than merely returning a plain-text rejection reason[cite: 5]. Integrating partners must query the specific rejection records, upload new files to obtain new fileIds according to the task requirements, and invoke the dedicated resubmission endpoint for precise replacements[cite: 5]. Once all pending tasks for the current cycle are completed, the VA will automatically revert to the pending_review status[cite: 5].

  • ❗ Strictly Prohibited: Recreating VA Orders: When a VA is in the pending resubmission state (pending_attachment), do not under any circumstances call the account creation endpoint again to attempt to recreate the VA[cite: 5]. The underlying system is equipped with duplication checks; if it detects an existing VA order for the same channel, it will outright reject the request and prompt you to use the dedicated resubmission endpoint[cite: 5].
  • 💡 Strict Attachment Validation: When submitting the replacement files, the file use type (fileUseType) and the exact number of files must perfectly match the requirements of the pending task snapshot. Any attempts at cross-type task clearing will be rejected by the system[cite: 5].

[Guides] VA Application Rejection and Resubmission Guide

To help integrating partners quickly adapt to the new structured rejection mechanism, we have published a comprehensive business integration guide. This guide features end-to-end sequence diagrams covering the entire flow—from receiving the Webhook and querying tasks to routing upload APIs and completing resubmissions. It also breaks down 5 typical resubmission scenarios across different business lines (corporate-level, person-level, private VA) along with troubleshooting tips. We strongly recommend that developers review this document thoroughly prior to integration.


Improved

[API] Get VA details

[Webhook] entity.status.update

In conjunction with the structured rejection mechanism, we have expanded the response payloads for both the VA details query endpoint and the entity status update Webhook[cite: 5]. Whenever the VA status transitions to pending_attachment, a new rejection object containing a batchId and comprehensive pending task details will be included in the response or webhook payload, enabling integrating partners to seamlessly parse and notify users[cite: 5].


Thank you for choosing DogPay! If you encounter any issues or need assistance during integration, please feel free to reach out to the technical support team.