Custom software development in Argentina
We have a platform in production for the Argentine market: it charges in pesos through Mercado Pago, verifies identity with ID and selfie, and was built knowing gross income tax is settled province by province.
What we run in Argentina today
We operate here. Our veterinary marketplace is built for Argentina: pesos, Mercado Pago, Rioplatense Spanish and identity verification. The legal and tax study behind it covers ARCA, gross income tax, the Central Bank and data protection.
Taking software to Argentina is not translating into voseo. It is charging through the payment method people actually use — Mercado Pago, not an international card —, modelling a tax that is provincial rather than national, and absorbing that the gateway will apply withholdings and surcharges that arrive later, in a file, and that if the system does not account for them bank reconciliation never balances.
How you get paid
The payment method decides the checkout.
Currency: Argentine peso (ARS). A checkout copied from another country fails here before it fails anywhere else.
Mercado Pago
It is the dominant payment method and the one we integrate for Argentina. In our veterinary marketplace it is resolved per country in code: Argentina creates a Mercado Pago preference in pesos, Spain a Stripe session in euros.
Bank transfer · CVU/CBU
Instant transfers between accounts and wallets are identified by CBU or CVU, and the alias is what people actually use. A form that only accepts IBAN is useless.
Instalments
Interest-free instalments are a buyer expectation, not an occasional promotion. They change the displayed price and the remaining margin, and must be decided before writing the checkout.
Tax obligations
What the tax authority demands from the software.
It is not a module bolted on at the end. It shapes the data model, and redoing it later costs far more than getting it right from the start.
| Framework | What it means for the system |
|---|---|
| ARCA (formerly AFIP) | The national tax authority. Electronic invoicing with types depending on issuer and recipient status, and reporting regimes for platforms intermediating sales: if the software connects buyer and seller, reporting duties apply regardless of whether money is touched. |
| Gross income tax (IIBB) | A provincial tax, not a national one. There are twenty-four jurisdictions with their own rates and a Multilateral Agreement to apportion the base when selling across several. A tax calculation with a single rate applied nationwide is wrong by design. |
| Withholdings and surcharges | Gateways and collection agents deduct amounts in advance against VAT and gross income tax. The money landing in the account is not the sale amount, and that difference must be recorded as a tax credit, not as an unexplained loss. |
| Monotributo (simplified regime) | Many professionals and small businesses invoice under a simplified regime with categories based on annual turnover. The receipt type they issue and the tax credit they grant the buyer differ, and the software has to know before issuing. |
Experience
What breaks imported ERPs
A system designed for a country with a national consumption tax assumes the amount charged equals the amount sold. In Argentina it does not: between the sale and the money landing there are VAT and gross income tax withholdings and surcharges, applied by the gateway and by provincial collection agents, arriving in a later file. If the software has nowhere to put those entries, every month leaves a mismatch the accountant fixes by hand. Modelling it from the start costs a few days. Discovering it in production costs the client's trust.
Regulatory framework
Who regulates the product.
SENASA
National food safety and animal health service. It registers veterinary products and sets withdrawal times for meat and milk — the figure a digital vademecum uses to compute the actual slaughter date.
ANMAT
National administration for drugs, food and medical technology. It regulates human medicines, food and medical equipment, including what is sold on a marketplace.
BCRA
Central Bank. It draws the line between intermediating a payment and being a regulated payment service provider — a distinction that decides whether a platform may hold third-party funds, and one worth settling before writing the code, not after.
Data protection
Personal data protection act 25.326. In our marketplace, identity verification uses ID document and selfie, which is biometric data: processed with an explicit legal basis, a retention period and a named processor — not stored just in case.
Other markets
The figures behind all of the above are on the pricing page, and the terms used here are in the glossary.
FAQ
Custom software in Argentina
Do you integrate Mercado Pago?
Yes, it is in production. Gateway choice is resolved per country in code: Argentina creates a Mercado Pago preference in pesos, Spain a Stripe session in euros, each with its own confirmation webhook.
Does the software handle gross income tax per province?
It is a design decision we take per project, and we raise it before starting. Applying a single rate nationwide is the costliest and most frequent mistake in software brought in from abroad.
Can you work with an Argentine company from Spain?
Yes. Development is remote and we already do it: the veterinary marketplace is built from Spain for the Argentine market, with the tax and legal study done for that jurisdiction.
How do you handle seller identity verification?
With ID document and selfie against a verification provider. It is biometric data and treated as such: legal basis, retention period and named processor in the privacy policy.
A project in Argentina?
Tell us what you need and we will say what it involves in this market and what we do not know yet.