Discover the latest feature releases, product improvements and bug fixes of Appian - Submerchant Register. Stay up to date with changes and updates to the batch submerchant onboarding endpoint POST /onboarding/v1/submerchants/batch in Ecuador 🇪🇨.We use the ISO 8601 standard (YYYY-MM-DD) for dates, and Semantic Versioning (MAJOR.MINOR.PATCH) for version numbers, increasing the:1.
MAJOR version when we make incompatible API changes,
2.
MINOR version when we add functionality in a backward-compatible manner, and
3.
PATCH version when we make backward-compatible bug fixes.
IMPROVEMENTS for changes in existing functionality.
DEPRECATED for soon-to-be removed features.
REMOVED for now removed features.
SECURITY in case of vulnerabilities.
Latest#
1.2.0 - 2026-08-31#
🆕 Batch submerchant onboarding available in Ecuador (Card Not Present only)#
The batch submerchant onboarding endpoint POST /onboarding/v1/submerchants/batch is now available in Ecuador 🇪🇨, allowing multiple submerchants to be created in a single request. Ecuador supports Card Not Present only; there is no Card Present variant.Each batch item uses the single Card Not Present model directly (no variant selection).
Point‑of‑sale fields are not applicable and are omitted.
Because Ecuador is Card Not Present only, requests do not select a request model — send Card Not Present items directly.
🆕 Nationality fields for legal representative and beneficial owners#
Three nationality properties were added to the submerchant model to support identity and compliance requirements.| Field | Description | Required |
|---|
legalRepresentativeNationality | Nationality of the legal representative. ISO 3166‑1 alpha‑3 country code. | Yes |
uboNationality | Nationality of the ultimate beneficial owner (UBO). ISO 3166‑1 alpha‑3 country code. | Yes |
ubo2Nationality | Nationality of the second UBO. ISO 3166‑1 alpha‑3 country code. Nullable when there is no second UBO. | No |
Nationality values must be valid ISO 3166‑1 alpha‑3 codes (for example ECU, COL, PER, MEX, CHL). Send ubo2Nationality as null when a second beneficial owner does not apply.
🆕 submerchantName rules#
The submerchantName value follows a defined specification for accepted values and normalization.Maximum length of 18 characters.
The value is normalized to uppercase and trimmed of leading/trailing spaces.
Must contain at least one letter (A–Z).
Allowed characters: A–Z, 0–9, &, -, and single spaces between words.
Accented characters and Ñ are not allowed.
Values that exceed 18 characters after normalization, or that contain unsupported characters, are rejected. Remove accents and Ñ before sending (for example, use PENA instead of PEÑA).
Got a suggestion on this documentation? Contact us.
