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 Peru 🇵🇪.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#
🆕 Card Present and Card Not Present request variants#
Each item in the batch request now accepts one of two named request models. The documentation renders them as separate tabs (Card Present and Card Not Present) so you can pick the model that matches how the submerchant operates.Card Present (CP): for submerchants that accept in‑person, terminal‑based payments. Includes the point‑of‑sale fields (usesKushkiPos, operationMode, emails, paymentOptions, paymentTypes, terminalCount, storeName, storeAddress).
Card Not Present (CNP): for submerchants that accept online / remote payments. Point‑of‑sale fields are not applicable and are omitted.
A single batch call can mix CP and CNP items — each array element is validated against the variant it declares.
The variant is selected per item. Send the fields that belong to the chosen model; fields from the other model are not accepted.
🆕 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 PER, COL, MEX, CHL, ECU). Send ubo2Nationality as null when a second beneficial owner does not apply.
⬆️ submerchantName rules clarified#
The submerchantName specification was rewritten to remove ambiguity about 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).
Previous release notes#
1.1.0 - 2026-01-01#
🆕 Batch submerchant onboarding#
Initial release of the batch submerchant onboarding endpoint POST /onboarding/v1/submerchants/batch in Peru 🇵🇪, allowing multiple submerchants to be created in a single request.
Got a suggestion on this documentation? Contact us.
