Payment Gateways in Colombia (2026): A Comparison for Businesses

Choosing a payment gateway in Colombia is about more than just “accepting cards.” In practice, it determines which payment methods you offer, how user-friendly the checkout process is , how funds are settled, and how automated the accounting reconciliation can be.

In this technical guide, we review how online payments are structured in Colombia, the most commonly used methods, and what to consider when selecting a provider. For a regional overview, see payment gateways in Latin America. If your business operates internationally, see international payments.

PSE is often a key method for determining coverage and costs, but it requires rigorous reconciliation by reference and status.

In assisted sales, the payment link is a product in its own right: it requires tracking, an expiration date, and clearly defined events.

For businesses, the priority is that every payment can be broken down: gross amount, fees, taxes, net amount, and final amount.

How Online Payments Work in Colombia

In a typical e-commerce workflow, your website or app captures the payment intent, sends the transaction to the provider, and the provider handles the authorization (credit card or bank transfer), confirmation, and subsequent settlement. The difference between providers lies not only in “whether they approve” the transaction, but also in how they present events, references, and reports for operating in Colombia.

For businesses, the most critical issues are typically: issuer approval, fraud and chargeback management, settlement times, availability of reports, and consistency of identifiers for reconciliation.

Most Common Payment Methods in Colombia

In PSE, statuses can be: initiated, pending, confirmed, or expired. Check how each one is reflected in reports and automatic notifications (webhooks).

For credit cards, it measures approval rates by issuer and chargebacks. The total cost isn't just the fee.

The mix of methods varies by industry, average order value, and sales channel. In general, it’s usually best to prioritize the methods that maximize conversion without compromising operational control: traceability, reconciliation, and returns management.

• Credit Cards: Relevant for e-commerce and subscriptions; fraud control and issuer approval are critical.
• PSE: Bank transfer for online payments: important for coverage and costs, with reconciliation by reference.
• Cash: Still relevant in some sectors; transactions are processed through networks and reconciled using receipts.
• Payment links: Useful for assisted sales and collections; prioritize traceability and reconciliation.

A best practice is to set up the checkout page to track conversion rates by payment method, rejection rates by issuer, and confirmation times. This allows you to choose a provider based on data, not just on the published rate.

The leading payment gateways in Colombia

Ask for examples of reconciliation: what a settlement looks like and how to identify the transactions that make it up. Without that, the closing process becomes a manual one.

This list is for informational purposes only and is not a ranking. The exact availability of payment methods, terms and conditions, and technical support varies depending on the specific case and volume.

• PayU: A payment gateway with a local presence that supports Colombian cards and payment methods, depending on the integration.
• Wompi (Bancolombia): Local payment gateway supporting cards and PSE; APIs (integrations) and payment links.
• ePayco: A Colombian payment provider offering credit cards, PSE, and local payment options.
• Rebill: A payment platform for Colombia that uses local payment methods and focuses on reconciliation, fund settlement, and operational control.
• PlacetoPay: A business-focused provider offering PSE support and card processing depending on the product.
• Mercado Pago: checkout screen and payment links for merchants; regional coverage.
• PayPal: Wallet option and checkout screen for merchants processing international payments.
• dLocal: Access to local methods for international businesses and platforms.

Before making a decision, request documentation on APIs (integrations), payment events (automatic notifications (webhooks)), examples of settlement reports, and a clear breakdown of what is charged (fees, fixed per-transaction charges, chargebacks, anti-fraud fees, refunds, and exchange rates (FX) if applicable).

How to Choose a Payment Gateway in Colombia

For businesses, the selection process should be based on operational and risk requirements. A practical checklist:

• Required methods: cover the actual payment mix (credit card, bank transfer, cash, digital wallet) without increasing the number of reconciliations.
• Conversion: Delay, Friction, Retry, and Authentication Policies.
• Settlement: schedule, currency, fee discount prior to payment (net settlement), and availability of transaction details.
• Reconciliation: Consistent, exportable IDs; reliable automatic notifications (webhooks); and reports that explain net amounts, commissions, and settlements.
• Risk: additional verification support (3DS), anti-fraud tools, chargeback management, and rules by issuing bank (BIN)/country.
• Scalability: limits, API stability (integrations), agreed-upon response times (SLA), and support for high demand.

In Colombia, PSE is adjusting its cost mix and reducing surcharges, but is requiring compliance with settlement terms.

Payment gateway fees in Colombia

There is no such thing as a “single commission.” The total cost typically consists of: a variable rate (percentage), a fixed fee per transaction, costs related to chargebacks, refunds, and fraud prevention, and—for international transactions—the exchange rate (FX) and bank fees.

To compare providers, request a breakdown of the net amount settled per transaction (settlement example) and simulate different payment method mix scenarios. A payment gateway with a slightly higher rate may be more efficient if it improves approval rates and reduces chargebacks.

Operations and Reconciliation: What Data You Need in Colombia

Beyond the checkout screen, the problem usually arises in the back office: reconciliation, refunds, adjustments, and reporting. A minimum set of data per transaction includes: merchant ID, order ID, payment method, gross amount, fee, taxes, net amount, currency, authorization date, settlement date, and final status.

If the provider doesn't offer a consistent model for events (automated notifications (webhooks)) and reports, the team ends up having to make up for it with spreadsheets. That's why, for companies, “integration” doesn't end with an approved payment: it ends when you can close out the month without any discrepancies.

Implementation: Technical Checklist for Businesses

If you work with an enterprise resource planning (ERP) system or business intelligence (BI) dashboards and reports, confirm from day one the format of export files (fields, delimiters, time zone) and how changes are versioned. A change to a column can disrupt automated processes.

Define the returns process: who initiates the refund, how the customer is notified, how it is reflected in the settlement, and how it is recorded in the accounting system (reversal of revenue vs. credit memo).

Agree with support on the incident handling process: which logs to share, response times, and how resolution is verified. In payments, time matters because it affects conversion rates and reputation.

If you plan to use more than one provider, establish from the outset the “payment method selection process” and the governance framework: when to use each method, how to compare metrics, and how to avoid duplicate reconciliations.

Before integrating, define the data model you want to maintain: internal order, customer, method, status, net amount, commissions, and dates. The finance department will use this model to close the books each month.

Determine from the outset how you will handle protection against duplicate charges (idempotence) (retry without duplicate charges), how you will store tokens, and what retry strategy you will use in the event of authorization failures.

In QA, test “unfavorable” scenarios: reverse transactions, partial refunds, chargebacks, pending payments, and expired payments. The important thing is that each case leaves a consistent audit trail in reports and events.

At the operational level, set up alerts for: automatic notifications (webhooks), rejection rates by issuer, fraud spikes, discrepancies between settled net and expected net, and settlement delays.

Red flags to watch for when evaluating a gateway

These signs often foreshadow operational and reconciliation issues, even if the provider “charges fairly” or promises high conversion rates.

• The reports do not show the net amount per transaction or the IDs vary between the dashboard, API (integration), and exportable files.
• There are no reliable automatic notifications (webhooks), or there is no way to reprocess events.
• The settlement statement is provided in aggregate form without sufficient detail for reconciliation.
• Refunds get "lost" in adjustments, and there is no way to track why a certain amount was deducted.
• The payment terms are unclear depending on the method (credit card vs. bank transfer vs. cash).

Common mistakes when implementing payment gateways

These errors occur when the focus is solely on launching the checkout screen and the operational aspects—such as reconciliation, returns, and adjustments—are underestimated.

• Failure to define a unique and persistent order ID throughout the entire workflow (checkout screen, automated notifications (webhooks), reports).
• Reconcile using bank totals without reconstructing the net amount per transaction.
• Do not test statuses that are not "Happy" (pending, expired, partial refunds, chargebacks).

Operational example: For transfers, confirmation may be delayed. If your fulfillment depends on confirmed payment, you need reliable events and expiration rules to avoid processing deliveries without payment.

Frequently Asked Questions About Payment Gateways in Colombia

Which payment method should typically be prioritized for e-commerce in Colombia?

It depends on your audience and ticket type. Generally, credit cards are the standard; adding bank transfers or local payment methods can improve coverage. Track conversion rates by payment method.

How does the reconciliation statement affect accounting reconciliation?

Define which identifiers and reports you receive. Make sure each transaction has unique IDs and that the reports break down net amounts, fees, and settlements.

What should I look for in the clearance sale?

Calendar, currency, fee discount before payment (net settlement), and transaction details. Also, whether there are any withholdings or adjustments shown on the statement.

What do I need to make international payments to Colombia?

In addition to the payment method, you need clarity on exchange rates (FX), crediting times, and reconciliation between the supplier, the bank, and the accounting department. See the guide to international payments.

When is it usually a good idea to use more than one supplier?

When you need redundancy, better rates per method, or a range of methods that a single provider cannot offer. The cost is greater operational and reconciliation complexity.