Validate an application

Checks whether the records linked to an application (the business, its people, and its payment methods) include everything the application’s requested services need. The response lists any missing or invalid fields by section. Validation doesn’t change the application, and it doesn’t return a validation token. The request has no body.

One owner on the application must be the signer, flagged with isSigner on their business link. If no one is flagged, the people section returns a missingFields entry with field set to people.isSigner, label set to Signer, and reason set to required — choose the person who signs the application. The signer rule isn’t reported when the application has no people.

The people section also checks ownership. At least one person must be the primary controller, flagged with isPrimaryController. If no one is, the entry has field set to people.isPrimaryController, label set to Primary Controller, and reason set to required — at least one principal must be designated. Unless the business’s legalStructure is government or non-profit, at least one owner must have an ownershipPercentage of 25 or more. If no one does, the entry has field set to people.ownershipPercentage, label set to Qualifying Owner, and reason set to at least one principal must have an ownership stake of 25% or more.

Validation also reports required documents that have nothing uploaded. See List application document requirements. The bank statement requirement appears in the business section, with field set to documents.bankStatement. A person document appears in the people section, with field set to people.{personReference}. followed by the requirement’s fieldPath, such as people.01a0014d-ce1a-7110-9bac-c4c59647a88d.person.documents.w9. Submit doesn’t enforce document requirements.