{"section":"known-issues","requestedLocale":"en","requestedSlug":"operations-cannot-be-performed-correctly-due-to-null-documenttype-field","locale":"en","slug":"operations-cannot-be-performed-correctly-due-to-null-documenttype-field","path":"docs/en/known-issues/Payments/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md","branch":"main","content":"## Summary\n\n\nSome providers necessarily need `documentType` to be different from `null`, that is, to be correctly filled in to carry out some payment operations.\n\nSo far we have two known scenarios:\n\n1. The absence of this field does not allow the payment to be correctly analyzed by anti-fraud, which causes the transaction to be at risk.\n2. The absence of the field prevents the payment from being authorized and consequently leads to the transaction being canceled.\n\n\n##\n\n## Simulation\n\n\nThis issue occurs when a client uses information from a company to complete an order.\nIf the company name is used to complete the transaction, the `documentType` field is left unfilled, causing problems with the approval for the payment.\n\n\n##\n\n## Workaround\n\n\n\nFor the first scenario, it is possible to use an internal API to skip the anti-fraud analysis step.\nDespite being strongly discouraged, it is a possible operation."}