Org Web Adapter

Editing pages/mmpy_127_update_fields_for_tax_information_api.org

:PROPERTIES:
:ID:       42cb808d-f6c6-4dc8-bc34-9ddff63a8e3f
:END:
#+title: MMPY-127 Update fields for Tax Information API

- source :: https://multimediallc.atlassian.net/browse/MMPY-127
- tags ::  [[id:7c3bbb4e-d079-42c4-992c-3e76210911f4][Falcon Nest Project]]  [[id:4b532967-a1d9-45f4-b1f0-9a02ad540ff0][Falcon Nest Project Story]]
- epic ::  [[id:3d772010-1c06-4aff-8f18-433518561cb4][MMPY-179 - Tax ID Validation Workflow]]
- sprint ::  [[id:70c22c31-3b17-40b9-b2db-02a5a0b665f4][MM Sprint 24]]
- status ::  [[id:4d41d978-e56f-45c1-88d1-e2c76510972e][Status - Complete]]

* Tasks
** DONE Remove certification for 1099 eConsent `cert_1099_electronic` :chore:work:multimediallc:mmpy179:mmpy127:
:PROPERTIES:
:ID:       91f5c4c0-35ca-db36-4ff4-7d95c979ff58
:END:

- Note taken on [2025-10-24 Fri 13:56] \\

Turns out this was already done by Javier back in February!

https://github.com/multimediallc/mm-pay-internal/blob/main/nest/payee/migrations/0014_remove_taxinformation_cert_1099_electronic.py#L9

And I also confirmed that field is not used anywhere.

Is there additional work need here to use the 1099_format field, or is that work in another ticket?

* Description
In developing MMPY-8: Payee adds new Tax Information, there is a change required to the tax api:

Remove certification for 1099 e consent cert_1099_electronic

We can use the 1099_format field as a consent along with the e-signature based on how the page flow works.