Curated market guide
Colombia PSP routes to verify first
Which PSPs or bank routes should a merchant ask first for PSE, wallets, cash collection, and cards in Colombia?
Colombian PSP / gateway shortlist
Use when you need PSE, cards, wallets, and alternative payment methods through a localized gateway.
Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.
- Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
- Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
- Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
Bank, PSE, or acquiring route
Use when PSE or direct acquiring control is central and you can complete local bank/acquirer due diligence.
Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.
- Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
- Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
- Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
Wallet and cash-collection route
Use when customer conversion depends on wallets or cash-in/cash-out networks and the merchant can verify direct or partner access.
Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.
- Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
- Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
- Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
Regional PSP route
Use when the merchant wants a regional PSP or orchestration layer, while separately verifying Colombian onboarding and settlement rules.
Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.
- Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
- Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
- Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
Documents to prepare
- Company registration and tax details
- NIT or foreign-entity onboarding question
- Beneficial-owner and signatory ID
- Website/app URL and customer-support policy
- Bank account and settlement-currency requirements to verify
Questions to ask
- Can my current merchant entity onboard for this market, or is a local company required?
- Which local payment methods are actually enabled for my merchant category and transaction model?
- Which documents are required for KYB, website/app review, tax review, and beneficial-owner checks?
- Which checkout flows, APIs, plugins, hosted pages, refunds, disputes, webhooks, and reconciliation files are supported?
- Which payout currencies, FX handling, reserves, chargeback process, taxes, and support SLAs should be confirmed before launch?
If the official contact route is unclear
If public contact details are not specific enough, ask LocalPayMap to identify the right official form, PSP sales route, or local acquiring partner before committing engineering work.
- Which local payment methods are actually enabled for my merchant category and transaction model?
- Which documents are required for KYB, website/app review, tax review, and beneficial-owner checks?
- Which checkout flows, APIs, plugins, hosted pages, refunds, disputes, webhooks, and reconciliation files are supported?
- Which payout currencies, FX handling, reserves, chargeback process, taxes, and support SLAs should be confirmed before launch?
Route comparisons
Merchant questions before choosing a provider
Use these questions to separate customer payment fit from PSP onboarding, settlement, pricing, support, refunds, disputes, and compliance details.
How customers may pay locally
Cards, bank-transfer methods, cash or voucher options, wallets, and payment-link flows can all matter. The mix depends on ecommerce category, trust level, ticket size, and whether buyers are comfortable with cards.
Local entity and settlement checks
Confirm whether a Colombia entity, local tax details, or local bank account is required. Ask about COP settlement, FX conversion, reserves, payout timing, and cross-border settlement availability.
PSP selection notes
Compare Colombian PSPs, LATAM aggregators, acquiring gateways, marketplace routes, and global PSPs. The right route should match customer coverage with merchant eligibility and operational clarity.
Documents and KYB checks
Prepare registration documents, ownership details, bank or settlement details, website and product description, refund policy, expected volume, and customer support contact.
Integration checklist
Confirm these items before committing engineering time or signing provider terms.
Merchant checklist before integration
Use these questions before committing engineering time or signing a provider contract.
- Confirm cards, bank-transfer, wallet, voucher, and payment-link support.
- Ask whether Colombia entity, tax, or local banking is required.
- Verify COP settlement, FX, reserves, and payout timing.
- Check refunds, disputes, failed payments, and reconciliation exports.
- Confirm sandbox, API, hosted checkout, webhooks, and support coverage.
- Request official pricing or a written provider quote.
How customers actually pay here
Colombia checkout can involve bank-transfer flows such as PSE, cash or voucher networks, wallets, cards, and instalments. These routes do not behave the same way for every merchant or provider. Before prioritising PSE, Efecty, Baloto, Sured, Nequi, DaviPlata, cards, or BNPL, confirm eligibility, payment confirmation, expiry, refunds, disputes, payout timing, reconciliation files, and support ownership with the provider.
- Evaluate PSE where bank-account payment behavior matters, and confirm confirmation, refund, dispute, and reconciliation rules.
- Cash and voucher routes can reach buyers who prefer offline payment, but unpaid references and expiry handling must be modeled.
- Wallets such as Nequi and DaviPlata may matter by segment; verify whether they are included in your PSP route.
- Cards and instalments can still matter for higher-ticket baskets, subject to acquiring setup and contract terms.
- Do not infer settlement speed or final cost from the payment method name alone.
Questions merchants ask
Is Colombia card-only checkout enough?
Card acceptance can matter, but local bank-transfer, voucher, wallet, and payment-link routes may improve coverage depending on customer segment.
Should merchants use a LATAM PSP for Colombia?
A LATAM PSP can help if the merchant needs Colombia plus other regional markets, while a local PSP may provide deeper local support.
Do foreign merchants need local setup?
It depends on the provider. Confirm local entity, tax, bank-account, and settlement requirements before integration.
What should be tested before launch?
Payment confirmation, failure handling, refunds, disputes, reconciliation exports, webhook events, and customer support escalation.
Are provider rates fixed publicly?
No. Public pricing is only a screening signal; final pricing depends on merchant profile and contract.
Do I need a Colombian company to accept payments in Colombia?
It depends on provider route, merchant entity, product category, risk review, settlement currency, tax requirements, and contract model. Some regional or local providers may support selected foreign entities, while other routes may require Colombia-specific registration, tax details, or local banking. Confirm entity requirements per method in writing before integration.
Which payment method should I add first in Colombia?
Evaluate PSE early when bank-transfer behavior matters, then compare cash networks, cards with instalments, wallets, and BNPL against buyer segment and provider eligibility. Confirm confirmation timing, pricing, refunds, disputes, reconciliation, payout handling, and support ownership before treating any method as the launch default.
How long does settlement take for PSE and cash payments in Colombia?
Do not rely on rail-level confirmation as your payout calendar. Ask the provider to confirm payment confirmation timing, payout schedule, cash-reference expiry, unpaid-reference handling, settlement currency, failed payout process, refunds, disputes, and reconciliation files in writing.