Online Payments in Colombia: PSE, Cards, and Payment Gateways
You have the product, you have the site, and you have customers ready to buy. All that's missing is the one thing that turns visits into money: getting paid online. And that's where a decision trips up most business owners in Colombia, because every payment gateway promises the same thing at similar prices: which one do I choose, what will it actually cost me, and what does integrating it into my system involve? This guide answers with practical criteria and real numbers from the Colombian market.
The payment methods that actually matter in Colombia
Before choosing a provider, you need to understand which methods you need. Local buying behavior isn't the same as in other countries:
- PSE (bank debit). It's the biggest differentiator in the Colombian market. Many people shop online without a credit card, and PSE lets them pay directly from their bank account. If you don't offer it, you're leaving sales on the table.
- Credit and debit cards. Essential, and the gateway to installment payments, which noticeably changes conversion on higher-ticket purchases.
- Digital wallets. Very widespread for small amounts and quick purchases from a phone.
- Cash at physical locations. Still relevant for part of the audience, especially outside major cities.
- Cash on delivery. Common in some sectors, but handle it carefully: it increases returns and logistics costs.
The rule is simple: always offer PSE and cards; everything else depends on your audience and your average ticket.
How to compare gateways without getting lost
Almost all of them advertise a similar fee, which is exactly why comparing on that number alone is the classic mistake. These are the six criteria that actually make a difference:
1. The full fee. Don't just look at the percentage: there's almost always a percentage + a fixed amount per transaction + VAT. On low-ticket purchases, the fixed amount weighs a lot more than the percentage.
2. Settlement time. How many days it takes them to transfer the money to you. The difference between getting paid in 2 days versus 15 is pure cash flow, and for a small business it can matter more than half a percentage point of fees.
3. Onboarding requirements. Documentation, business structure, industry. Some sectors get rejected or need special approval.
4. Quality of technical documentation. This is what almost nobody evaluates and what drives up integration cost the most. A well-documented API, with a sandbox environment and reliable webhooks, can mean weeks of difference in development time.
5. Real, local support. When a payment gets stuck in limbo on a Friday, it matters a lot to have someone to write to.
6. Recurring billing. If you sell subscriptions, you need tokenization and automatic charges. Not every provider handles this equally well.
As a general reference for the Colombian market, fees typically run between 2.5% and 4% plus a fixed amount per transaction, with PSE usually cheaper than cards. Always ask for a formal quote based on your estimated volume: the percentages on the public pricing page are usually negotiable above a certain amount.
Payment button, hosted checkout, or API integration
Here's the technical decision that defines cost, timeline, and the buying experience.
| Option | How it works | When it makes sense |
|---|---|---|
| Payment button / link | You generate a link and share it | Sales via WhatsApp or social media, low volume, immediate launch |
| Hosted checkout | The customer leaves for the provider's page and comes back | Most e-commerce sites: fast to integrate and with less compliance burden |
| API integration | The payment happens inside your own site or app | When the experience matters: subscriptions, marketplaces, mobile apps |
The honest recommendation for most businesses: start with hosted checkout. It reduces your exposure to handling card data, integrates in days, and works well. Move to API integration once volume justifies polishing every point of conversion.
One important nuance: if you're going to handle card data inside your own platform, you enter PCI DSS compliance territory, which adds requirements and costs. Delegating that to the provider is, in most cases, the smart call.
How much it costs to integrate payments into your software
2026 ranges for the Colombian market, covering development only:
| Integration scope | Investment range (USD) | Typical timeline |
|---|---|---|
| Hosted checkout on a standard e-commerce site | $1,200 – $3,500 | 1-3 weeks |
| API integration with reconciliation and webhooks | $3,500 – $10,000 | 3-7 weeks |
| Recurring subscriptions or marketplace with split payments | $10,000 – $30,000+ | 6-14 weeks |
On top of that come per-transaction fees, which are a permanent variable cost, and don't forget electronic invoicing: every sale needs to end in a valid invoice with the DIAN (Colombia's tax authority). We cover that in what your electronic invoicing software needs to comply with. If you're putting together the full budget for your store, also check how much an e-commerce website costs in Colombia.
The mistakes that cost you sales (and money)
- Not offering PSE. The most expensive mistake of all in Colombia. You're excluding customers who don't use a credit card.
- Ignoring webhooks. If your system only marks a sale as complete when the customer returns to the site, you'll lose orders: people close their browser. Confirmation should arrive via webhook from the provider, not through the redirect.
- Not handling intermediate states. A PSE payment can sit pending. Your system needs to know what to do in the meantime, and not ship or cancel by mistake.
- A checkout with too many fields. Every extra field costs you conversion. Ask for only the bare minimum.
- Not reconciling. What the gateway charges, what hits the bank, and what your system says all need to match. Without automatic reconciliation, someone loses a day a month to spreadsheets — and gaps show up that nobody can explain.
- Locking yourself into one provider. If you design the integration with your own abstraction layer, switching gateways or adding a second one later is a matter of days, not months.
At BigBoc, we integrate payments into e-commerce sites, apps, and custom platforms with Node.js and Next.js, leaving the payment, order, invoicing, and reconciliation all connected.
Frequently asked questions
Can I use two payment gateways at the same time? Yes, and it's good practice once volume justifies it: it gives you a backup if one fails and leverage to negotiate fees.
How long does it take to receive the money? It depends on the provider and the payment method. Confirm it before signing, because it directly affects your cash flow.
Do I need to be a registered company? Most providers require formal business documentation. Requirements vary by entity type and industry.
Can I charge automatic subscriptions? Yes, with card tokenization. Keep in mind that PSE isn't designed for automatic recurring charges.
How long does the most common integration take? Between 1 and 3 weeks for a hosted checkout, including testing in the sandbox environment.
Get paid right from day one
The payment gateway isn't a detail you leave for the end of the project: it determines how much you sell, when you receive the money, and how much time your team loses reconciling accounts. Choosing based on fees alone is the fastest way to regret it. At BigBoc, we build and integrate payment platforms for companies across Colombia and Latin America with React, Next.js, Node.js, and artificial intelligence.
Need to start accepting online payments or improve the integration you already have? Request your free quote at bigboc.com/cotizacion and get a proposal with scope, timeline, and cost in less than 24 hours. Want to review your case first? Write to us through the contact form.