After a merchant is successfully on boarded to the Processor there are only certain values that can cannot be updated. This resource provides a list of values that cannot be updated after successful merchant onboarding:
Merchant Entity Class:
The entity class is used by the processor for TIN validation. Once that validation has been completed then the following fields cannot be updated:
| Note |
|---|
|
...
|
Can only be changed by a Facilitator after the batch cutoff time of 9:30PM ET, changing this will cause any active auth to fail capture.
Merchant Members Class:
The members class associates an owner to a merchant entity and is used for owner validation. Once a merchant is boarded the following fields for the primary owner cannot be updated:
First Name (members.first)
...
Fields on the /members class can be changed until the merchant TIN is validated by the processor
...
. Once the TIN is marked as “valid” from the processor then it is no longer updatable.
...
| Note |
|---|
|
After the merchant TIN is validated by the processor then this is no longer updatable.
Address (members.address)
|
Merchant Class:
The merchant class associates the sub-merchant with the legal entity. Once a merchant is boarded the following fields for the primary owner cannot be updated:
...
| Note |
|---|
|
...
MCC (merchant.mcc)
...
Amex (merchant.amex)
|