Curated market guide
Uruguay PSP routes to verify first
Which PSPs, acquirers, gateways, and local payment routes should a merchant ask first for Uruguay?
acquirer_or_processor
Prioritize an acquirer or processor when card authorization, local acquiring, POS plus e-commerce, or card operations control are central to the launch.
Do not claim that a Uruguay entity is or is not required. Provider role matters: a gateway model, payfac model, direct acquirer contract, e-money route, or payment/collection provider can each have different applicant, RUT, bank-account, and settlement requirements. Confirm with the provider and counsel.
- Are you the acquirer, processor, switch, POS network administrator, gateway, or payfac in this route?
- Can a foreign company onboard directly, or is a Uruguay entity, RUT, local bank account, or local representative required?
- Which card brands, installments, refunds, chargebacks, 3DS, recurring payments, and reporting features are supported for my use case?
payment_gateway_or_payfac
Prioritize a gateway or payfac when you want a single integration that can route cards, cash, bank transfer, wallets, or multiple acquirers.
Do not claim that a Uruguay entity is or is not required. Provider role matters: a gateway model, payfac model, direct acquirer contract, e-money route, or payment/collection provider can each have different applicant, RUT, bank-account, and settlement requirements. Confirm with the provider and counsel.
- Is my integration payfac, gateway, or bring-your-own-acquirer?
- Which payment methods are available in Uruguay for my merchant category and applicant entity?
- Who handles settlement, disputes, refunds, reconciliation, customer support, and production approval?
cash_collection_or_bank_transfer_provider
Prioritize cash collection, bank transfer, or wallet routes when customers may prefer Abitab, Redpagos, online bank transfer, or local account-funded payment methods.
Do not claim that a Uruguay entity is or is not required. Provider role matters: a gateway model, payfac model, direct acquirer contract, e-money route, or payment/collection provider can each have different applicant, RUT, bank-account, and settlement requirements. Confirm with the provider and counsel.
- Is the route online, offline cash collection, bank-transfer based, wallet based, or PCT?
- What customer identifier, document field, voucher flow, expiry, reconciliation, and refund path are required?
- Can this route be offered to my customer segment and merchant category?
Cards via registered acquirer, processor, or gateway
BCU's institution register identifies payment-system roles such as acquirers, processors, switches, and POS network administrators, which helps merchants avoid confusing a gateway conversation with acquiring eligibility.
Do not claim that a Uruguay entity is or is not required. Provider role matters: a gateway model, payfac model, direct acquirer contract, e-money route, or payment/collection provider can each have different applicant, RUT, bank-account, and settlement requirements. Confirm with the provider and counsel.
- Use the provider's official merchant or developer channel and ask which registered role applies to the product you will use.
- Are you the acquirer, processor, switch, POS network administrator, gateway, or payfac in this route?
- Can a foreign company onboard directly, or is a Uruguay entity, RUT, local bank account, or local representative required?
Gateway/payfac orchestration for multi-method checkout
Some Uruguay-focused gateway documentation distinguishes payfac and gateway models, which affects who owns acquiring contracts, settlement, and merchant underwriting.
Do not claim that a Uruguay entity is or is not required. Provider role matters: a gateway model, payfac model, direct acquirer contract, e-money route, or payment/collection provider can each have different applicant, RUT, bank-account, and settlement requirements. Confirm with the provider and counsel.
- Ask whether you can use the payfac model or must bring your own acquirer contract before production.
- Are you the acquirer, processor, switch, POS network administrator, gateway, or payfac in this route?
- Can a foreign company onboard directly, or is a Uruguay entity, RUT, local bank account, or local representative required?
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 merchant form, developer support, or contact page 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
Bamboo Payment vs Mercado Pago in Uruguay
How local customers usually pay
Uruguay should be researched from the customer's payment habit first, not from a generic global checkout menu. Current public records point to Cash collection, General commerce and Digital wallet, while provider discovery may include Abitab, Bamboo Payment Uruguay, dLocal Uruguay, Handy, InSwitch and Mercado Pago Uruguay. For a small merchant, the practical question is which of those routes a real customer recognizes and which provider can legally onboard the merchant entity. Cards may be enough for some cross-border testing, but local conversion often depends on domestic bank rails, wallets, QR, payment links, cash-style collection or local debit schemes. Ask providers to separate live local methods from roadmap items, then confirm payment status timing, refund mechanics, settlement currency and support coverage before committing engineering work.
- Cash collection acceptance through a provider that can onboard your merchant entity. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
- Digital wallet acceptance through a provider that can onboard your merchant entity. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
Payment methods to check first
For Uruguay, begin with the methods that match real customer behavior, then map each one to a provider that can actually onboard your merchant. Current public records point to Cash collection, General commerce and Digital wallet, but availability can vary by PSP, entity type and industry.
- Start with the payment method customers already recognize, not the provider with the longest logo wall.
- Check whether the method supports online checkout, payment links, QR, app redirects, refunds and clear transaction references.
- Keep one fallback method for buyers who cannot or will not use cards.
- Document which method is mandatory for launch and which can wait for phase two.
What to do if you do not have a local company
Do not assume a foreign company can use the same route as a local merchant in Uruguay. Some PSPs can onboard overseas entities, some require a local company and local bank account, and some support only selected industries. The cleanest first email states your incorporation country, product, website, expected volume, average order value, customer location, settlement currency and refund model.
- Ask whether foreign entities are accepted directly or only through a local subsidiary, distributor or merchant-of-record arrangement.
- Confirm local company, tax ID, local bank account, local director, licence and proof-of-address requirements.
- Ask which settlement currencies and payout countries are supported for your entity.
- Get the onboarding answer in writing before promising a local method to customers.
PSP and four-party provider screening
Use provider discovery to separate customer-facing payment brands from the companies that can legally process and settle funds. Public PSP/contact leads for Uruguay currently include Abitab, Bamboo Payment Uruguay, dLocal Uruguay, Handy, InSwitch and Mercado Pago Uruguay. Compare them by eligibility, method coverage, operational support and documentation quality rather than headline pricing alone.
- Abitab: Payment provider. Verify live coverage for Cash collection, Bill payment and Agent network, entity eligibility, pricing, settlement and support before treating it as a launch option.
- Bamboo Payment Uruguay: PSP / aggregator. Verify live coverage for Cards, Cash, Bank transfer, Wallets, Payfac and Gateway, entity eligibility, pricing, settlement and support before treating it as a launch option.
- dLocal Uruguay: PSP / aggregator. Verify live coverage for Cards, Bank transfers, Cash, Wallets, Payins and Payouts, entity eligibility, pricing, settlement and support before treating it as a launch option.
- Handy: PSP / aggregator. Verify live coverage for POS, Handy Link, QR, Online payment gateway, Cards and Bank transfers, entity eligibility, pricing, settlement and support before treating it as a launch option.
- InSwitch: Payment gateway. Verify live coverage for Wallet platform, Card issuing, Payment processing, QR and Payouts, entity eligibility, pricing, settlement and support before treating it as a launch option.
- Mercado Pago Uruguay: Wallet operator. Verify live coverage for Cards, Mercado Pago wallet, Payment links, QR and Installments, entity eligibility, pricing, settlement and support before treating it as a launch option.
- Paganza: Wallet operator. Verify live coverage for Bill payments, Wallet payments, QR and Bank account payments, entity eligibility, pricing, settlement and support before treating it as a launch option.
Settlement, currency, refunds and disputes
Treat all pricing and settlement information for Uruguay as preliminary until confirmed by the official provider or contract. Fees, payout timing, rolling reserves, FX, chargeback costs and refund rules can change by industry, volume, risk review, settlement currency and integration route.
- Ask for transaction fee, fixed fee, refund fee, chargeback fee, payout fee, FX spread, reserve policy and minimum monthly or setup charges.
- Confirm payout timing, settlement currency, settlement account country, failed-payout handling and reconciliation file fields.
- Check whether refunds must return through the original method and whether partial refunds are supported.
- For cards, confirm dispute workflow, evidence deadlines, chargeback fees and fraud-monitoring rules.
Compliance and operating checks
Before launch in Uruguay, prepare KYB and risk material as if the provider will ask for it. Most delays for new merchants come from unclear ownership, unsupported industries, missing licences, incomplete websites, weak refund policies or settlement accounts that do not match the merchant record.
- Prepare company registration, ownership, director ID, website/app URL, product description, terms, privacy policy and refund policy.
- Disclose regulated products, digital content, subscriptions, marketplace activity, high-risk categories and cross-border fulfilment.
- Ask how the provider screens sanctions, fraud, AML risk, chargebacks and customer complaints.
- Keep sensitive or restricted markets at compliance-review level; do not use unofficial workarounds.
Questions to ask service providers
Send a concise written checklist to every Uruguay PSP or aggregator so responses can be compared side by side. The goal is to expose hidden entity, settlement, support and technical gaps before engineering work begins.
- Which payment methods are live today for my exact merchant entity, industry and customer geography?
- Do you support hosted checkout, API, plugin, payment links, webhooks, sandbox, refunds and reconciliation exports?
- Who is the merchant of record, who handles chargebacks and who owns customer support for failed payments?
- What documents are requested, how is approval reviewed, and what would cause rejection?
- Can you provide official links for pricing, settlement terms, developer docs and support escalation?
Common beginner mistakes
The most common mistake in Uruguay is treating payment acceptance as a logo checklist. Local conversion depends on customer habit, provider eligibility, settlement flow, refund support and operational reliability. A cheaper-looking route can become expensive if it cannot settle where you need, cannot refund cleanly or cannot support the methods buyers expect.
- Choosing cards only when wallets, mobile money, bank transfer, QR or cash-style routes are normal for local buyers.
- Building against an API before KYB, entity and settlement eligibility are confirmed.
- Ignoring refund and dispute flows until the first customer complaint arrives.
- Comparing providers without asking the same written questions of each one.
Questions merchants ask
Which payment methods should a new merchant check first in Uruguay?
Start with Cash collection, General commerce and Digital wallet. Then confirm which provider can support your entity, industry, customer geography, settlement currency and refund model.
Can a foreign merchant accept local payments in Uruguay without a local company?
Sometimes, but it must be verified provider by provider. Ask whether a local entity, local bank account, tax ID, licence, local director or merchant-of-record route is required.
Which PSPs or aggregators are worth screening for Uruguay?
Public leads include Abitab, Bamboo Payment Uruguay, dLocal Uruguay, Handy, InSwitch and Mercado Pago Uruguay. Treat them as a shortlist for outreach, not as confirmed eligibility or complete market coverage.
Can I use public fee pages as a final quote?
No. Public fees are screening context only. Final pricing can vary by country, industry, volume, risk review, settlement currency, FX, reserves and contract terms.
What operational questions should I ask before integration?
Ask about onboarding documents, restricted industries, live payment methods, checkout flow, webhooks, sandbox, refunds, disputes, chargebacks, reconciliation files, settlement timing and support escalation.
What should I do if the provider has no public sales email?
Use the official contact form, support page or developer contact route, and send a short brief with your entity country, product, volume, currencies and required payment methods.