They've just added this to normalize errors from DLocal. We should add code to make it show a field-specific validation error like we do with our direct DLocal connection.

ejegg: Hi Gravy folks, are there plans to do better normalization of processor-side validation errors for DLocal? For example, this transaction failed at DLocal because of an invalid tax ID, but the response we get from you has no structured indication of the bad field, just

"error_code": "invalid_request_parameters",

When there is an error in a specific field, our direct connection with DLocal indicates which field it is so we can highlight it on the form and the donor can correct it.

Piero: A fix for this has been released, mapping was updated to INVALID_TAX_IDENTIFIER for the case of the incorrect payer.document and the rest of the payer attributes to INVALID_BILLING_ADDRESSYou can find more information on the payer attributes on Dlocal's Docs. Please let me know if you encounter any issues.