acquirer_or_processor · curated
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 · curated
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 · curated
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 · curated
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 · curated
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?
KYB prepDocuments 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.
Due diligenceQuestions 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?
Contact route fallbackIf 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?
Compare nextRoute comparisons
Bamboo Payment vs Mercado Pago in Uruguay
Bamboo Payment Uruguay vs dLocal Uruguay
See all compare candidates for Uruguay