Curated market guide
Argentina PSP routes to verify first
Which PSPs, acquirers, gateways, and local payment routes should a merchant ask first for Argentina?
PSP or aggregator checkout for cards, payment links, and plugins
Argentina has a mature PSP ecosystem and BCRA maintains public PSP/role registries, so the first shortlist should separate regulated role, merchant onboarding path, and integration model.
Do not claim that an Argentina entity is or is not required. Argentina PSP, tax, banking, and foreign-exchange onboarding can vary by provider role and merchant category; ask each provider whether a local company, CUIT/tax profile, Argentina bank account, local representative, and local-currency settlement are required, then confirm with counsel.
- Use the provider's official business signup, developer portal, or contact form first; ask for the exact legal applicant requirements before starting integration work.
- Which BCRA PSP function or acquiring/aggregator role applies to the product I am using?
- Can my current non-Argentina company onboard directly, or do you require an Argentina tax ID, local bank account, or local contracting entity?
Direct or bank-linked card acquiring
A direct acquiring route may matter for merchants that need stronger control of underwriting, card operations, installments, dispute handling, or enterprise reconciliation.
Do not claim that an Argentina entity is or is not required. Argentina PSP, tax, banking, and foreign-exchange onboarding can vary by provider role and merchant category; ask each provider whether a local company, CUIT/tax profile, Argentina bank account, local representative, and local-currency settlement are required, then confirm with counsel.
- Ask whether the provider is the acquirer, aggregator, or gateway layer and request the official merchant-services application path.
- Which BCRA PSP function or acquiring/aggregator role applies to the product I am using?
- Can my current non-Argentina company onboard directly, or do you require an Argentina tax ID, local bank account, or local contracting entity?
Interoperable QR and payment-by-transfer acceptance
BCRA describes interoperable wallets and payment-by-transfer/QR infrastructure, so QR can be a meaningful route when wallet or account-funded payments matter.
Do not claim that an Argentina entity is or is not required. Argentina PSP, tax, banking, and foreign-exchange onboarding can vary by provider role and merchant category; ask each provider whether a local company, CUIT/tax profile, Argentina bank account, local representative, and local-currency settlement are required, then confirm with counsel.
- Do not assume every QR route fits e-commerce, recurring payments, or foreign applicants; verify merchant eligibility and operational support with the provider.
- Which BCRA PSP function or acquiring/aggregator role applies to the product I am using?
- Can my current non-Argentina company onboard directly, or do you require an Argentina tax ID, local bank account, or local contracting entity?
Documents to prepare
- Company registration certificate and operating entity details.
- Beneficial-owner, director, and signatory identity documents.
- Business website/app URLs, product description, refund policy, terms of service, and restricted-category explanation where relevant.
- Bank account, settlement currency, tax/VAT/GST information, and expected processing volume.
Questions to ask
- Can my current merchant entity onboard, or is a local company or bank account required?
- Which local payment methods are live for my business category and customer flow?
- What documents are required for KYB, technical review, and production approval?
- How are refunds, chargebacks, reconciliation files, reserves, FX, and payout currencies handled?
- Which public email, form, dashboard, or partner manager should be used for merchant onboarding?
If the official contact route is unclear
Use the provider's official business signup, merchant portal, developer support, or contact form first; if there is no public sales inbox, use LocalPayMap WhatsApp fallback for routing help.
- Which local payment methods are live for my business category and customer flow?
- What documents are required for KYB, technical review, and production approval?
- How are refunds, chargebacks, reconciliation files, reserves, FX, and payout currencies handled?
- Which public email, form, dashboard, or partner manager should be used for merchant onboarding?
Route comparisons
Mercado Pago vs MODO Comercios in Argentina
Payway vs Decidir in Argentina: Merchant Shortlisting Checklist
How customers pay
Argentina is wallet-heavy, transfer-friendly, and sensitive to currency and instalment terms. Mercado Pago is the default consumer habit for many online buyers. Transferencias 3.0 and bank-led wallet flows support account payments, while cards remain important for instalments and higher-value orders. Cash networks can still help, but merchants should design around slower confirmation, currency movement, and provider-specific settlement rules.
- Inspect Mercado Pago, Ualá, MODO, Rapipago, Pago Fácil and Naranja X before assuming international cards are enough.
- Map each method to the checkout moment: instant confirmation, delayed cash confirmation, card authorisation, wallet redirect, QR scan, or bank-app approval.
- Ask providers how failed payments, refunds, disputes, and reconciliation events are returned to your order system.
Starter payment mix for a first launch
For a first launch in Argentina, keep the stack narrow enough to operate, but broad enough to match how local buyers actually pay. The first version should cover the highest-reach local method, one reliable card or bank route, and one fallback for buyers who cannot complete the primary flow.
- Mercado Pago or a PSP route that includes it
- Transferencias 3.0 or bank-transfer coverage
- Local cards with instalment support
- Cash networks only when the audience needs them
Local PSP and provider routes to consider
Compare Mercado Pago direct, Payway/Decidir-style card gateways, local PSPs, and regional PSPs. Ask how the provider handles instalments, currency conversion, refunds, and settlement timing.
- Shortlist Coelsa, Decidir / Payway Ventas Online, Increase Pay, Mercado Pago Argentina, Mercado Pago and Ualá only after confirming the methods are available for Argentina.
- Separate customer-facing payment methods from the provider route that gives you access to them.
- Use official contact forms, sales pages, developer docs, or published support routes when no direct email is available.
Can you accept payments without a local company?
Cross-border routes exist, but local settlement, domestic card approval, instalment products, and tax handling can depend on local entity status. Verify availability against official provider onboarding rules.
- Ask whether the provider can onboard a merchant incorporated outside Argentina.
- Confirm whether local settlement in ARS, a local bank account, tax registration, licence, or representative is required.
- Verify restricted industries, sanctions screening, consumer protection obligations, and data or invoice rules with the provider and qualified advisers.
Documents and KYB to prepare
Before contacting providers in Argentina, prepare a concise merchant profile. Most PSPs will ask for company registration details, ownership or director information, identity documents for responsible people, website or app URLs, product description, target customer country, expected monthly volume, average order value, refund policy, and current payment stack. Regulated sectors may need licences, extra compliance explanations, or source-of-funds information.
- Company registration, tax details, beneficial-owner or director information, and signing authority.
- Website, app, checkout flow, pricing page, refund policy, fulfilment model, and customer support route.
- Expected volume, average order value, currencies, settlement needs, chargeback history, and launch timeline.
- Licences or compliance documents for financial services, gaming, digital assets, lending, adult, healthcare, or other restricted categories.
Settlement, pricing and FX questions
Published pricing should be used only for initial screening. Actual pricing in Argentina can change by industry, entity country, payment method, volume, refund rate, chargeback risk, settlement currency, reserve policy, and contract term. Before implementation, verify current official pricing, written provider quotes, tax treatment, payout fees, FX spread, rolling reserves, minimum fees, and the calendar used for settlement cutoffs.
- Which currencies can you collect and settle, and can funds be paid out in ARS or another currency?
- Does the quoted price include fixed fees, percentage fees, refund fees, chargeback fees, payout fees, taxes, and FX markup?
- When does settlement start for delayed methods such as cash vouchers, bank slips, or offline collection?
- Are reserves, rolling holds, minimum monthly fees, or volume commitments part of the contract?
Questions to ask providers before integration
Use the first provider call to remove operational ambiguity, not only to ask for a rate card. A useful answer should state which entity signs the agreement, which payment methods are live, what documents are needed, how long risk review takes, how refunds and disputes work, how webhooks or callbacks behave, and what support is available after launch.
- Which payment methods are live for my merchant category, entity country, and target customers?
- Who provides the merchant account, acquiring, wallet access, settlement, compliance review, and technical support?
- Can I test the exact checkout flow, callback payloads, refund flow, and reconciliation reports before going live?
- What happens when a payment is pending, expired, duplicated, reversed, disputed, or manually reviewed?
Industry notes
Retail should model instalments and wallet checkout together. Digital goods should avoid exposing long voucher delays for instant-delivery products. Services should confirm invoice, refund, and currency conversion handling.
- E-commerce needs conversion coverage, refund rules, fraud controls, and delivery evidence.
- SaaS and subscriptions need recurring support, card lifecycle handling, tax invoices, and dunning rules.
- Games, top-up, and digital content need instant confirmation, low-value economics, limits, and failed-payment retry logic.
- Services and B2B payments need invoices, references, manual review rules, and predictable settlement reporting.
Questions merchants ask
Which payment methods should I check first in Argentina?
Start with Mercado Pago or a PSP route that includes it, Transferencias 3.0 or bank-transfer coverage and Local cards with instalment support. Then add cards, wallets, bank transfers, cash options, or BNPL only where they match your customers and your provider can support them in production.
Can a foreign merchant accept payments in Argentina without a local company?
Sometimes, but it depends on the PSP, payment method, industry, risk review, settlement currency, and local compliance rules. Ask providers whether they can onboard your existing entity before you build the checkout.
What documents should I prepare before contacting providers in Argentina?
Prepare company registration details, owner or director information, identity documents for responsible people, website or app URLs, product description, expected volume, average order value, refund policy, settlement currency needs, and any licences for regulated activities.
Are public payment fees enough to choose a PSP in Argentina?
No. Public fees are useful for shortlisting only. Verify official pricing or a written quote, including percentage fees, fixed fees, refund fees, chargeback fees, payout fees, tax treatment, FX spread, reserve policy, and contract term.
What settlement questions matter most in Argentina?
Ask when the payout clock starts, which currencies can be settled, whether funds can be paid in ARS or another currency, how holidays affect payout, and how reserves or rolling holds are applied.
Should I connect directly to each local method in Argentina?
Small merchants usually start with a PSP, gateway, acquirer, or aggregator that bundles several methods. Direct connections can make sense at higher scale, but they add contracts, compliance review, settlement operations, and maintenance work.
What should I test before going live in Argentina?
Run small live payments for each method, then test cancellation, refund, failed payment, duplicate payment, expired payment, webhook delivery, reconciliation export, customer support handoff, and dispute or reversal handling.
What if a provider has no public merchant email for Argentina?
Use the official contact form, sales page, developer documentation, or support route. Send a concise brief with country, entity location, business model, payment methods needed, monthly volume, currencies, and launch timeline.