Update a business
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
The business reference (businessUuid).
Request
A free-text description of the business.
The merchant category code (MCC) that classifies the business.
The seasons the business operates in. Values are case-insensitive on input and returned capitalized.
A non-empty addressDetails is rejected on update. Manage a business’s
addresses through the /v2/businesses/{businessReference}/addresses
endpoints instead. An omitted field or an empty array is accepted as
“no address change requested.”
Key-value data to merge into the business’s stored customData.
Payabli stores the applicant’s answers to a boarding template’s
custom questions under the templateAnswers key.
When you update a business, Payabli merges customData into the
stored value, following JSON Merge Patch (RFC 7396). Keys you
don’t send are kept at every depth, and nested objects merge key
by key. Strings, numbers, Boolean values, and arrays replace the
stored value, and arrays aren’t merged. Send a key as null to
delete it, such as {"crmId": null}. A customData that isn’t
an object, such as an array, replaces the stored value whole.
Leave out customData to keep it as is.
The customData you send can be up to 65,536 bytes serialized.
The limit applies to the request, not to the merged result.
Whether the business is foreign-owned.
Whether the business is tax-exempt.
The business’s tax-exempt classification, such as 501(c)(3).
Response
A human-readable result message.
Non-blocking warnings.