Availability: Argentina

This operation allows merchants to associate a custom, human-readable alias (CVU alias) with an existing active virtual account in Argentina.

An alias replaces the 22-digit CVU with a short, memorable text string, reducing errors when sharing payment details.

Info

• The alias must be unique at the country level. This is not a platform restriction, but a requirement of the Argentine banking system. If another CVU already uses the same alias, the request will be rejected.
• To update an alias, call this same endpoint with the new value once the required 24-hour waiting period has elapsed.
• Once created or updated, the alias cannot be changed again for 24 hours. There is no limit on the total number of changes.
• The alias is activated asynchronously. An INPROGRESS response does not mean the alias is already active. Verify activation using the Get Virtual Account Status endpoint.
• To check which aliases are currently active on a virtual account, use the Get Virtual Account Status endpoint.

Alias Format Rules

• Only letters (a–z, A–Z), numbers (0–9), and dots (.) are allowed.
• Spaces, hyphens, underscores, at signs (@), and other special characters are not permitted.
• Length must be between 5 and 20 characters.
• Valid examples: alias.example, alias.example2026, alias.example.test

Best Practices

• Use meaningful, consistent aliases to aid in internal reconciliation and support flows.
• Log alias creation responses and associate them with your internal transaction records for easy auditing.
• Use the status check endpoint periodically or before payment collection to verify the alias is active and mapped correctly.