| SBJ-0015 | No order with this identifier exists in the institution on the direct channel. | 404 |
| SBJ-0016 | The order conflicts with one the plugin accepted before: the same clientOrderId and orderRevision with another body, or a second order under a key that is already in use. | 409 |
| SBJ-0017 | The plugin already accepted a higher orderRevision of this clientOrderId. | 409 |
| SBJ-0018 | The request body is larger than the plugin accepts. | 413 |
| SBJ-0019 | A field breaks the order schema or a field rule. | 422 |
| SBJ-0020 | The order has a field or block that its operation does not take. | 422 |
| SBJ-0021 | The order lacks a field or block that its operation requires. | 422 |
| SBJ-0022 | The metadata of the order is above the limits, or a key is not valid. | 422 |
| SBJ-0023 | A client key looks like it carries a CPF, a CNPJ, a judicial process number, or a long digit run. Use another key. | 422 |
| SBJ-0024 | responsibleInstitutionCnpj does not match the institution code on the plugin. | 422 |
| SBJ-0025 | The institution does not take orders through the direct channel. | 422 |
| SBJ-0026 | The plugin does not take custody of the child order: no matching parent exists in the institution. Answer the court yourself. | 422 |
| SBJ-0027 | The deployment does not take permanent blocks on the direct channel. Nothing is recorded. | 422 |
| SBJ-0040 | The channel switch to DIRECT is not allowed in a multi-tenant deployment. | 422 |
| SBJ-0041 | The channel switch to DIRECT needs PLUGIN_AUTH_ENABLED on. | 422 |
| SBJ-0042 | The stored institution code is not the 8-character CNPJ root of the responsible grouping. | 422 |
| SBJ-0043 | The institution has an open order, or a block that still holds money, so the channel does not switch. | 409 |
| SBJ-0044 | The caller is an application, or the token is not the token of a person. A person must make this call. | 403 |
| SBJ-0045 | The token carries a tenant. This operation is a platform operation. | 403 |
| SBJ-0046 | Another channel switch won. Nothing moved. Send the request again. | 409 |
| SBJ-0048 | The result is terminal, so there is nothing to re-arm. | 409 |
| SBJ-0049 | The re-arm reason is missing, blank, too long, or holds personal data. | 422 |
| SBJ-0050 | The re-arm is for a single-tenant deployment. | 422 |
| SBJ-0051 | The revision has no open human decision for this operation to resolve. | 409 |
| SBJ-0052 | The resolution, the reason, or the ledger evidence is not valid. | 422 |
| SBJ-0053 | The resolution is for a single-tenant deployment. | 422 |
| SBJ-0054 | The journal shows that money moved, so the resolution is refused. | 409 |
| SBJ-0055 | The journal shows no landed effect, so there is nothing to acknowledge. | 409 |
| SBJ-0056 | The order is not eligible for erasure: it is not concluded, it still holds money or an open decision, its retention period has not ended, or its parent order is not erased. | 409 |
| SBJ-0057 | The order is a permanent block before its end date, or the plugin cannot read its latest revision. Nothing is erased. | 409 |
| SBJ-0058 | The reason, ticket, or note is not valid. On the purge preview, dryRun is not true or limit is out of range. | 422 |
| SBJ-0059 | The erase is for a single-tenant deployment. | 422 |
| SBJ-0060 | The institution is not owned by this plugin. | 409 |
| SBJ-0061 | The permanent-block attempt is not parked, or its order is busy. | 409 |
| SBJ-0062 | The acknowledged amount is above what the permanent block holds. | 422 |
| SBJ-0064 | The evidence is a transaction that the plugin recorded itself for the revision. | 409 |
