Colombia Payments Guide

Payments in Colombia: Bank Transfers, Wallets, and a Growing Digital Consumer Market A merchant enters Colombia with a modern checkout. Prices are displayed in Colombian pesos. Visa and Mastercard are accepted. The payment page is encrypted, responsive, and technically sound. Yet a large group of customers still does not complete the purchase. Some do not want to enter card details with an unfamiliar international seller. Some have a deposit account or wallet but not a suitable credit card. Some expect PSE and leave when it is missing. Others worry that a generic decline message means their bank account has been charged. A customer who does complete payment may later struggle to understand the refund process in Spanish. Finance may receive the settlement days later without a clean connection to the original order. The merchant appears to have a card-performance problem. It actually has a checkout-trust and payment-access problem. That distinction is increasingly important in Colombia. The IMF’s April 2026 country profile estimates Colombia’s population at approximately 53.4 million and projects real GDP growth of 2.3% in 2026. Colombia remains one of Latin America’s largest consumer economies, although the editorial brief’s 38th-place nominal-GDP ranking should be reconfirmed against the exact IMF dataset and year selected for publication. (IMF)

Its ecommerce sector is expanding faster than those headline economic figures alone suggest. The Colombian Chamber of Electronic Commerce reported more than COP 105 trillion in online sales during 2024, a 26.7% annual increase, alongside 21% growth in transaction count. In the first quarter of 2025, online sales reached COP 27.3 trillion, 16.4% higher than a year earlier. These are ecommerce-industry measures, not national-accounts estimates of the digital economy, and should be presented as such. (Cámara de Comercio Electrónico) Financial access is also broadening. At the end of 2024, 96.3% of Colombian adults had at least one deposit or credit product, while 95.8% had a deposit product. Access does not mean that every account is actively used for online shopping, nor does it eliminate geographic, income, or digital-use gaps. It does, however, explain why account-based checkout can reach consumers who do not follow a conventional credit-card path. (Superintendencia Financiera) The merchant implication is direct: Colombia should not be launched as a card market with local methods added later as decoration. It should be launched as a mixed payment environment where cards, PSE, wallets, instant bank payments, cash-linked behavior, installments, fraud concerns, and customer trust serve different segments. Colombia Payment Snapshot Category Colombia payment-market profile Region Latin America; northern South America Population Approximately 53.4 million in the IMF’s 2026 profile Currency

Colombian peso, COP Economic position One of Latin America’s largest economies; verify the publication-year nominal-GDP rank Ecommerce direction More than COP 105 trillion in 2024 online sales, up 26.7% Financial access 96.3% of adults had a deposit or credit product in 2024 Core payment categories PSE, cards, wallets and digital deposits, bank transfers, instant payments, and selected cash-linked methods Important local infrastructure ACH Colombia, PSE, Transfiya, Bre-B and domestic low-value payment systems New instant-payment layer Bre-B entered operation in October 2025 and is expanding interoperable payments Mobile relevance High for bank authentication, wallets, transfers, marketplaces, gaming, travel, and on-demand services Recurring readiness Cards are the main portable foundation; local debits and wallet recurring products require provider-specific validation Local-acquiring relevance Potentially important for domestic cards, installments, COP settlement, issuer performance, and local methods Priority verticals Marketplaces, gaming, education, travel, fashion, digital media, SaaS, and on-demand services Primary takeaway Combine cards with trusted bank-based payment and transparent Spanish-language communication Colombia’s Digital-Economy Maturity Colombia does not have one universally comparable, current percentage that captures its entire “digital economy.” DANE’s digital-economy satellite work distinguishes between: * Industries that produce ICT goods and digital services

* Products significantly affected by digitalization * Digital uses across consumption, investment, intermediate inputs, and exports That framework is broader than ecommerce sales and should not be reduced to a single unsourced share of GDP. (DANE) A more reliable merchant-facing maturity profile combines: * Rapid ecommerce growth * High access to deposit products * Rising use of electronic channels * Established account-based ecommerce payment through PSE * Digital wallets and simplified deposits * Mobile-oriented marketplaces and services * The launch of interoperable instant payments through Bre-B * Continued cash relevance and uneven active use of financial products Banco de la República has documented substantial growth in electronic-payment channels since the pandemic while emphasizing persistent gaps in access, usage, and merchant acceptance. (Banco de la República) For merchants, Colombia’s digital maturity should therefore be understood as fast expansion across several payment rails, not a completed transition from cash to cards. The Colombia Checkout-Trust Diagnostic Diagnostic 1: Can the Customer Access the Offered Payment Method? The first question is not whether a method is technically available. It is whether the target customer can and wants to use it. A Colombian customer may have: * A bank deposit account * A simplified digital deposit * A mobile wallet * A domestic debit or credit card * An internationally enabled card * Access to PSE * Access to an instant-payment application

* Cash but no preferred digital instrument * Credit but a preference for installments * A financial product that is used for transfers but not card ecommerce A card-only checkout can therefore exclude customers who are financially included but not card-oriented. Merchant implication Segment payment access by: * Deposit-account ownership * Card availability * International card capability * PSE eligibility * Wallet or digital-deposit use * Mobile device * Customer age * Region * New versus returning customer * Transaction value * Merchant familiarity Do not infer digital-payment readiness from bank-account ownership alone. Diagnostic 2: Does the Merchant Look Trustworthy Before Payment Begins? An unfamiliar international merchant creates additional perceived risk. Customers may ask: * Is the price really in Colombian pesos? * Will my bank charge an international fee? * Will the product arrive? * Who handles returns? * Can I reach support in Spanish? * Is the payment page connected to a recognized bank? * Will I be charged twice if the page stalls? * How will I receive a refund? * Are taxes, duties, or delivery fees included? The checkout must answer these questions before asking for credentials. Trust-building elements Use: * COP pricing * Spanish-language checkout * Recognized PSE, card, bank, or wallet branding * Clear merchant identity * Delivery information * Return and cancellation terms * Tax and fee transparency * Secure-payment signals * Support contact * Statement-descriptor explanation

* Payment-status communication * Refund expectations Fraud-aware communication Messages should protect the customer without creating panic. For example: * Explain that the merchant will not request bank passwords. * Explain when the customer will be redirected to a bank. * Warn customers to verify the merchant name and amount. * State whether the payment is complete, pending, or failed. * Advise against sending credentials or OTPs to support agents. * Explain how official refund communication will occur. Diagnostic 3: Is PSE Available and Correctly Implemented? PSE is one of Colombia’s defining ecommerce payment services. It enables customers to initiate payment from an eligible financial institution through a bank-authenticated flow. The customer generally selects PSE, identifies the relevant customer or account context, chooses a participating financial institution, authenticates with the bank, confirms payment, and returns to the merchant. PSE sits within ACH Colombia’s payment ecosystem and is used for purchases and collections across merchants, enterprises, and public or private services. (ACH Colombia) Why PSE matters PSE can serve customers who: * Have a bank or eligible deposit account * Prefer not to enter card information * Trust their bank more than an unfamiliar merchant * Want to pay directly in COP * Lack a suitable credit card * Are paying a larger invoice, educational fee, service, or marketplace order * Are accustomed to bank-authenticated online payments

Commercially strong use cases PSE may be particularly relevant for: * Marketplaces * Education * Travel * Fashion and retail * Digital services * On-demand services * Utilities or bill-like payments * B2B collections * Account funding * Government or institutional payments Customer journey A simplified flow is: 1. Customer selects PSE. 2. Merchant or PSP creates a payment request. 3. Customer selects or confirms the financial institution. 4. Customer moves to the bank’s authentication environment. 5. Customer approves or rejects the payment. 6. The financial institution and payment infrastructure process the result. 7. The merchant receives status. 8. Customer returns to the checkout or confirmation page. 9. Order is fulfilled only after verified success. PSE is not simply a bank-transfer button A well-integrated PSE flow should support: * Order-specific payment request * Amount control * Bank selection * Customer classification where required * Return URLs * Server-side status * Duplicate-event protection * Expiration or timeout handling * Reconciliation reference * Refund operations * Spanish customer communication Common PSE implementation failures * Customer completes bank authentication but the order remains unpaid. * The redirect fails after the bank approves payment. * A pending response is treated as a decline. * The customer retries and creates a duplicate transaction. * The provider notification arrives later than the browser return.

* Finance receives a payment reference that cannot be matched to the order. * Refunds require a different operational process than cards. * The merchant offers PSE but hides it below card fields. Recurring suitability PSE should generally be treated as customer-initiated, one-time account payment. A successful PSE transaction does not automatically authorize recurring debits. Subscription merchants need a separate recurring instrument such as: * Stored card * Valid debit mandate * Provider-supported account debit * Recurring wallet authorization * Another compliant payment agreement Merchant implication For mainstream Colombian ecommerce, PSE should be evaluated as a potential launch-essential method—not as a late-stage optimization. Diagnostic 4: Are Cards Serving the Right Segments? Cards remain important in Colombia. They are particularly relevant for: * SaaS * Subscriptions * Travel * International customers * Cross-border retail * Gaming * Digital media * Higher-income segments * Card-on-file * Installments * Repeat payments Card categories to distinguish * Colombian-issued credit cards * Colombian-issued debit cards * Internationally enabled domestic cards * Foreign-issued cards * Corporate cards * Prepaid products * Wallet-funded cards * Stored cards A provider’s support for Visa or Mastercard does not establish identical acceptance for every Colombian card product or issuer. Domestic versus cross-border processing

Cross-border card acceptance can support demand testing, but performance may vary because of: * Issuer treatment * Merchant location * Processing route * Currency * Fraud rules * Authentication * Card product * Merchant category * customer behavior Local acquiring or domestic processing may help some merchants through different issuer relationships, local settlement, installment support, or broader domestic-card compatibility. It should be tested, not assumed. Installments Credit-card installments can be commercially relevant for: * Travel * Education * Fashion * Electronics * Higher-value retail * Services Before offering installments, verify: * Eligible cards and issuers * Number of installments * Minimum amount * Customer interest * Merchant fee * Who finances the plan * Settlement timing * Partial-refund handling * Cancellation * Merchant-category eligibility * Customer disclosure Do not use “installments” and “BNPL” interchangeably. Issuer installments, merchant installments, revolving credit, and third-party BNPL are separate products. Recurring payments Cards are generally the most portable starting point for: * SaaS * Streaming * Memberships * Gaming subscriptions * Subscription retail * Education subscriptions Support: * Initial authentication * Tokenization * Stored-credential indicators * Merchant-initiated transactions * Account updater where available * Failed-payment recovery * Renewal notice * Cancellation * Refunds Diagnostic 5: Are Wallets and Digital Deposits Treated as Distinct Products?

Colombia’s wallet market is connected to banks, fintech companies, simplified deposits, mobile transfers, cards, QR initiatives, and instant-payment infrastructure. A customer may describe several of these products as “wallets,” even when their legal and technical structure differs. The merchant should distinguish: * Stored-value wallet * Simplified deposit account * Bank application * Card wallet * Instant-transfer app * QR payment service * Provider checkout wallet * Marketplace balance Commercial value Wallet and digital-account payments may be relevant for: * Gaming * Digital media * Marketplaces * On-demand services * Social commerce * Small repeat purchases * Younger or mobile-first customers * Customers without conventional credit cards Evaluate every product separately Confirm: * Merchant eligibility * Customer reach * Funding source * COP support * Authentication * App switching * Payment finality * Refunds * Partial refunds * Recurring capability * Settlement * Transaction limits * Provider reporting * Disputes * Customer support Financial inclusion does not mean uniform use The 2024 inclusion report shows broad access to deposit and credit products, but active transactional use and product depth can vary. Merchants should measure what their customers actually select and complete. (Superintendencia Financiera) Diagnostic 6: How Does Bre-B Change the Bank-Payment Landscape? Bre-B is Colombia’s interoperable instant-payment system.

It launched in October 2025 and connects participating payment systems and financial institutions through common rules, technical standards, and aliases known as “keys” or llaves. Banco de la República describes it as a build-on-existing-infrastructure initiative designed to increase interoperability, competition, financial access, and immediate electronic payments. (Banco de la República) By early 2026, Bre-B was processing millions of transactions on high-volume days, and Banco de la República reported rapid adoption of payment aliases and growing use across households, merchants, and firms. (Banco de la República) What Bre-B may mean for merchants Potential merchant benefits include: * Faster account-to-account payment * More interoperable bank and wallet access * Simplified identifiers * Reduced fragmentation between participating institutions * New person-to-business payment options * Improved merchant acceptance * Better account-based checkout products over time What merchants should not assume Bre-B does not automatically mean: * Every provider supports ecommerce acceptance * Every key is suitable for order-specific collection * Dynamic merchant requests are universally available * Refunds are standardized * Recurring payment is supported * All institutions expose the same API * Merchant reconciliation is automatic * PSE is immediately replaced * Local acquiring becomes unnecessary PSE and Bre-B PSE and Bre-B should not be treated as identical.

PSE is an established ecommerce payment experience with bank authentication and merchant-oriented collection workflows. Bre-B is interoperable instant-payment infrastructure that can support broader transfer and payment use cases. Their merchant roles may overlap or evolve, but current implementation should be evaluated product by product. Merchant action Track: * Which PSPs support Bre-B merchant acceptance * Whether payments are order-specific * Dynamic QR or request-to-pay capability * Alias use * Transaction limits * Confirmation events * Refunds * Reconciliation * Merchant protection * Recurring functionality * PSE coexistence Diagnostic 7: Are Cash-Based Options Commercially Justified? Cash remains relevant in Colombia, but its role varies by customer, region, value, and merchant model. Cash-linked ecommerce can include: * Cash on delivery * Voucher or payment-reference methods * Payment at a participating retail or agent location * Cash deposit * Assisted collection These methods can serve customers who: * Do not want to prepay * Lack a preferred digital method * Distrust an unfamiliar merchant * Have limited digital use despite financial-product access * Prefer an agent or physical location * Are ordering physical goods Operating costs Cash-linked methods can create: * Delayed payment confirmation * Expiration * Abandoned vouchers * Delivery refusal * Fraudulent orders * Courier collection * Cash remittance * Manual reconciliation * Refund complications * Higher support volume * Slower access to funds

Merchant decision rule Add a cash-based method only when: * A defined segment requires it * The product is suitable * Incremental completed orders justify the cost * Fulfillment can wait for payment where necessary * Refunds are possible * Finance can reconcile it * Fraud and abandonment are measured Do not retain cash simply because it has historically been common. Measure migration from cash to: * PSE * Wallet * Bre-B * Card * Other account-based payment Diagnostic 8: Does the Mobile Journey Survive Authentication and App Switching? Colombian payment flows may move the customer between: * Merchant browser * Merchant application * PSE page * Bank website * Bank application * Wallet * OTP screen * Card 3-D Secure * Merchant return page Every handoff can fail. Common failure points * Bank app does not open * Return link is broken * Browser session expires * Customer returns to the product page instead of confirmation * Customer sees a pending result and retries * Merchant receives the callback but customer does not return * Customer returns before the server receives confirmation * A duplicate attempt is created * Spanish instructions are incomplete * Authentication times out Required controls Use: * Durable payment-intent ID * Separate attempt ID * Provider transaction ID * Idempotency * Authenticated webhooks * Duplicate-event detection * Status retrieval * Pending state * Safe retry rules * Expiration * Mobile deep-link testing * Browser fallback * Localized customer communication

The merchant should never fulfill solely because the customer reached a “success” URL. Diagnostic 9: Are Payment States Explained Correctly? Colombia’s mixed-method checkout requires precise status communication. Possible states include: * Method selected * Authentication required * Payment initiated * Bank processing * Awaiting customer action * Payment pending * Payment approved * Payment declined * Payment expired * Outcome unknown * Order paid * Refund requested * Refund submitted * Refund completed * Settlement pending Why “payment failed” is not enough A generic failure message can cause: * Duplicate payment * Support contact * Abandonment * Customer fear * Unnecessary method switching * Dispute * Loss of trust Better customer communication Explain: * Whether funds were submitted * Whether the customer should retry * Whether the order is reserved * Whether another method can be used * When the merchant will update the status * How to contact support * What reference to provide All critical messages should be available in clear Colombian Spanish. Payment-Method Priority Matrix Payment category Marketplaces Gaming and digital media Education and SaaS Travel and fashion Merchant guidance PSE Launch essential High-value addition Launch essential for education and one-time SaaS Launch essential or high-value addition Strong trusted bank-based checkout Colombian and international cards Launch essential Launch essential Launch essential Launch essential Important for recurring, installments, and cross-border customers

Wallets and digital deposits High-value addition Launch essential or high-value addition Segment-specific High-value addition Evaluate reach, limits, refunds, and recurring support Bre-B-enabled payments Emerging high-value addition Segment-specific Useful for collections and B2B as products mature Segment-specific Verify production merchant functionality Bank transfer outside PSE Useful for B2B or high-value orders Usually limited Important for B2B and education Useful for selected bookings Requires payment-reference matching Installments High-value addition Segment-specific Useful for education High-value addition Verify issuer and local-processing requirements Cash-linked payment Segment-specific Usually unnecessary for digital goods Segment-specific Segment-specific for physical retail Measure abandonment and refund complexity Cash on delivery Segment-specific Not suitable Not suitable Segment-specific for physical goods Include delivery-refusal economics Carrier billing Usually limited Segment-specific for low-value digital goods Usually limited Usually unnecessary Limits and product restrictions matter Currency and Pricing Colombia’s official currency is the Colombian peso, COP. Local-currency pricing COP pricing is generally commercially important for domestic customers because it provides: * Familiar price comparison * Reduced FX uncertainty * Better installment understanding * Clear PSE and wallet amounts * More transparent refunds * Stronger local trust Display conventions Colombian price presentation commonly uses:

* Peso symbol * Period or space for thousands grouping * Comma for decimal fractions where decimals are used High-value ecommerce amounts are normally displayed without unnecessary minor-unit precision. Use one format consistently across: * Product page * Cart * Checkout * Bank redirect * Confirmation * Invoice * Refund message Currency distinctions Separate: * Presentment currency: what the customer sees * Processing currency: what is submitted to the provider * Settlement currency: the provider’s accounting currency * Payout currency: what reaches the merchant * Reporting currency: the merchant’s internal currency A merchant may charge in COP but receive settlement in USD or another currency. This can create: * FX fees * Refund differences * Accounting complexity * Treasury exposure * Settlement delays Local Acquiring and Cross-Border Processing A merchant can enter Colombia through several models: * Cross-border card processing * Global PSP * Local gateway or PSP * Colombian acquirer * Merchant of Record * Local wallet or bank integration * Payment orchestration Cross-border card model Useful for: * Market testing * SaaS * International customers * Travel * Higher-income cardholders * Cross-border retail Potential limitations include: * Domestic issuer treatment * Installments * Domestic debit products * COP settlement * PSE * Wallet access * Local refunds * Merchant eligibility Local acquiring May provide: * Domestic issuer relationships * COP settlement * Installments * Local debit or credit products

* Different authorization economics * Local operational support It may require: * Local entity * Colombian bank account * Contracting documentation * Local tax registration * Additional integration * Separate settlement and reconciliation * Merchant-category review Evaluation method Compare matched cohorts by: * Issuer * Card product * Domestic versus foreign card * Currency * Order value * Installment plan * Authentication * Fraud policy * Customer type * Provider route * Time period Use language such as: * “May improve” * “Can reduce” * “Should be tested” * “Depends on issuer and merchant mix” Do not promise a universal approval-rate increase. Authentication and Customer Verification Colombia does not follow the European PSD2 Strong Customer Authentication regime. Authentication can involve: * Bank login * OTP * Bank application * Wallet authentication * Biometric confirmation * Card 3-D Secure * Security questions * Device recognition * Identity-document data * Customer-type selection * Risk-based controls Merchant controls Merchants can improve: * Data quality * 3-D Secure integration * PSE redirect handling * Mobile presentation * Return state * timeout recovery * error messages * fraud thresholds * customer education Merchants cannot guarantee: * Bank or issuer approval * OTP delivery * A frictionless flow * Wallet balance * Provider uptime * Exemption or authentication outcome Data collection Do not collect identity-document information unless it is necessary for: * Payment * Fraud prevention * Tax * Fulfillment * Regulation

* Customer support Document the purpose of every field. Recurring Payments and Subscriptions Recurring merchants should distinguish acquisition from collection. Cards Cards are usually the main foundation for: * SaaS * Streaming * Gaming subscriptions * Memberships * Education plans * Subscription retail Support: * Stored credentials * Tokenization * Initial authentication * Merchant-initiated transactions * Account updater where available * Failed-payment recovery * Renewal notices * Cancellation * Refunds PSE PSE is well suited to customer-initiated payment. Do not describe it as an automatic recurring method unless a distinct provider product creates a valid recurring authorization. Wallets Some wallets or digital accounts may support repeat or recurring payment. Confirm: * Customer consent * Token lifecycle * Balance handling * Reconfirmation requirements * Cancellation * Refunds * Provider portability Bank debit A recurring account debit requires a mandate or authorized debit product. Verify: * Consent * Notification * Return rights * failure handling * cancellation * reconciliation Refunds, Reversals, and Disputes A method is not launch-ready until the merchant can refund it. Cards Confirm: * Full refunds * Partial refunds * Reversals * Multiple partial refunds * Currency handling * Issuer posting * Chargebacks * Dispute evidence PSE and bank payments Refunds may not operate like card reversals. Verify: * Whether provider API refunds are supported * Whether customer bank details are needed * Whether funds return automatically

* Partial-refund support * Timing * Failed refunds * Reconciliation references * Customer communication Wallets Confirm whether refunds return to: * Wallet balance * Deposit account * Linked card * Original source * Another destination Cash-linked methods Refunds may require: * Bank transfer * Wallet transfer * Cash collection point * Customer identity * Manual approval Installments A partial refund may affect: * Customer balance * Remaining installments * Issuer credit * Merchant settlement * Interest * Reconciliation Test before launch. Settlement and Treasury A completed customer payment is not the same as merchant access to funds. Confirm: * Processing currency * Settlement currency * Payout currency * Payout frequency * Minimum payout * Local bank-account requirements * Entity requirements * Provider fees * FX * Reserves * Refund deductions * Chargeback deductions * Tax withholding where applicable * Settlement reports * Bank references * Reconciliation Reconciliation model Connect: Order → payment intent → payment attempt → PSE, card, wallet, or Bre-B reference → payment result → fee → refund or dispute → settlement batch → bank receipt Immediate bank confirmation does not remove the need for financial reconciliation. Fraud and Risk Colombia should not be characterized as inherently high risk. Risk varies by: * Merchant vertical * Payment method * Account history * Order value * Device * Customer location * Merchant familiarity * Delivery model * Cross-border exposure * Refund policy Relevant patterns * Card-not-present fraud

* Account takeover * Phishing * Social engineering * Fake payment confirmation * Wallet compromise * Refund abuse * Friendly fraud * Marketplace seller fraud * Promotion abuse * Cash-order fraud * Subscription disputes * Cross-border card fraud PSE and bank-payment risk Bank authentication can reduce exposure to stolen card credentials. It does not eliminate: * Compromised bank accounts * Customer deception * Phishing * Fake merchant sites * Account takeover * Refund fraud * Delivery disputes Bre-B risk Alias-based instant payments may improve convenience but also require: * Recipient verification * Merchant-name display * Order-specific references * duplicate detection * refund-recipient checks * scam warnings * controlled customer support Cards Monitor: * Issuer country * Device * account age * velocity * authentication * order value * delivery address * card testing * refund behavior Marketplaces Monitor: * Seller identity * payout changes * fake sales * collusion * account takeover * prohibited products * refund abuse * delivery disputes Gaming and digital media Monitor: * Account takeover * virtual-goods transfer * purchase velocity * credential changes * refund history * household-payer disputes * card testing Fraud performance should be evaluated alongside false declines and retained revenue. Regulation and Provider Roles

Colombia’s payment environment includes regulated financial institutions, specialized electronic-deposit and payment companies, payment-system administrators, acquirers, gateways, wallets, banks, and payment intermediaries. The Superintendencia Financiera supervises financial institutions and maintains information on specialized electronic-deposit and payment entities and low-value payment-system administrators. (Superintendencia Financiera) A Colombian legal definition does not necessarily treat every “payment gateway” as a distinct regulated entity category. The Superintendencia Financiera has noted that Colombian regulation does not contain one general definition covering all payment gateways. The actual obligations depend on the activities performed and the institutions involved. (Superintendencia Financiera) Distinguish responsibilities Merchant Responsible for matters including: * Product and service * Customer terms * Order fulfillment * Refund policy * Checkout disclosures * Fraud decisions under its control * Tax and invoicing obligations PSP or gateway May provide: * Technical connection * Payment page * Method aggregation * Reporting * Fraud tools * Reconciliation Its regulatory role depends on its activities. Acquirer May manage: * Merchant acceptance * Card-network relationship * Settlement * Merchant underwriting * Chargebacks Bank or financial institution May control: * Account * Authentication * Payment execution * Customer financial relationship Wallet or electronic-deposit provider

May control: * Account or stored value * Customer verification * Balance * Wallet authentication * Transfer functionality Marketplace May face additional responsibilities if it: * Receives money for sellers * Controls payouts * Holds balances * Splits funds * Provides regulated payment functions Merchant of Record May assume specified seller, tax, payment, refund, and customer obligations under contract. Provider country coverage does not prove merchant or product eligibility. Educational disclaimer: This article provides general information and does not constitute legal, regulatory, tax, accounting, foreign-exchange, privacy, security, or compliance advice. Merchants should confirm applicable obligations with qualified advisers and relevant payment partners. Tax and Invoicing Context Colombia operates a VAT system, with the general rate and reduced, exempt, or excluded treatments depending on the product, service, customer, and transaction. Foreign providers of specified services can have Colombian VAT registration, filing, and payment obligations. DIAN provides a process for VAT declarations by foreign service providers and maintains guidance for providers operating from abroad. (DIAN) Merchants should review: * Colombian VAT * Foreign digital-service rules * Significant economic presence where applicable * Electronic invoicing * Consumer price display * Withholding * Marketplace obligations * B2B versus B2C treatment * Imports * Refund-related tax adjustments * Merchant of Record responsibilities

Do not assume that use of a PSP eliminates the merchant’s tax obligations. Checkout Localization Language Use clear Colombian Spanish for: * Product and checkout * Payment-method names * PSE instructions * Card authentication * Wallet or bank-app handoff * Payment pending * Declines * Refunds * Installments * Delivery * Subscription terms * Customer support Avoid machine-translated financial language. Currency Use COP consistently. Clearly explain: * Total amount * Installment amount * Fees * Tax * Delivery * International charges where applicable * Refund currency Names and identification Colombian customer records may include: * Given names * Multiple surnames * Document type * Document number * Mobile number * Email * Address * City or municipality * Department Collect only fields required by the actual flow. Addresses Support: * Department * City or municipality * Neighborhood where relevant * Street address * Apartment or unit * Delivery instructions * Phone contact Do not force US state or ZIP assumptions. Method ordering A mainstream Colombian B2C checkout might prioritize: 1. PSE 2. Card 3. Relevant wallet or digital account 4. Bre-B-enabled or other instant-payment product where mature 5. Cash-linked method for eligible segments A subscription checkout might prioritize: 1. Card 2. Verified recurring wallet or debit 3. PSE for one-time or initial payment 4. Bank transfer for B2B Provider and Operating Models Global PSP Useful for: * International cards * Market testing * Central integration * Multicountry reporting * Tokenization

* Cross-border settlement Verify: * Colombian-issued cards * PSE * Wallets * COP processing * COP settlement * Installments * Local acquiring * Recurring payments * Refunds * Merchant category Colombian PSP or Gateway May offer: * PSE * Domestic cards * Wallets * COP settlement * Local fraud knowledge * Spanish support * Domestic reconciliation * Bre-B or transfer products Verify its legal role, financial partners, settlement model, contractual entity, merchant eligibility, and refund process. Local Acquirer Potential value: * Domestic card reach * Installments * Issuer relationships * COP settlement * local chargeback operations Potential cost: * Contracting * Entity or bank account * Integration * Separate reporting * Additional reconciliation * Provider governance Merchant of Record May assume specified responsibilities for: * Seller status * Payment * Tax * Invoicing * Refunds * Chargebacks * Customer support * Merchant payout Verify whether it supports PSE, local wallets, COP pricing, installment use, and the relevant merchant category. Payment Orchestration May become useful when a merchant coordinates: * Cross-border cards * Local acquiring * PSE * Wallets * Several providers * Several countries * Complex routing It is not required merely because Colombia has several relevant payment methods. Merchant-Vertical Recommendations Marketplaces Payment needs * PSE * Cards * Wallets * Instant payments * Seller payouts * Refund allocation * Split reconciliation * Fraud controls * Seller verification Key risks * Account takeover * payout changes

* fake sellers * buyer-seller collusion * refund abuse * delivery disputes Launch recommendation Use PSE and cards as a foundation, add wallets by customer evidence, and complete legal review before collecting or holding seller funds. Gaming and Digital Media Payment needs * Cards * Wallets * PSE * Small repeat purchases * Mobile checkout * Tokenization * Fast digital fulfillment Key risks * Account takeover * payment testing * virtual-item fraud * refund abuse * household-payer disputes Launch recommendation Offer at least one trusted account-based method alongside cards and measure payment completion by device and customer cohort. Education Payment needs * PSE * Bank transfer * Cards * Installments * Invoice references * Parent or student payer * Partial payments Key risks * Payment matching * cancellation * installment adjustments * refund timing * identity mismatch Launch recommendation Make PSE prominent, support cards where recurring or installment payment matters, and model enrollment, deposit, tuition, and refund states separately. Travel Payment needs * Cards * PSE for domestic customers * Wallets * Installments * Foreign-issued cards * Deposits * Partial refunds Key risks * Booking fraud * cancellations * long service delay * traveler versus payer * FX * chargebacks Launch recommendation Combine strong card acceptance with PSE and segment domestic from foreign-issued card performance. Fashion and Retail Payment needs * PSE * Cards * Wallets * Installments * Selected cash methods * Mobile checkout * Partial refunds Key risks

* Return abuse * delivery fraud * reshipping * installment adjustment * COD refusal Launch recommendation Prioritize PSE and cards, add installments or wallet options according to average order value, and compare prepaid and cash-linked orders after returns and logistics costs. SaaS Payment needs * Cards * Tokenization * Recurring billing * PSE for one-time invoices * Bank transfer for B2B * COP and potentially foreign-currency invoicing Key risks * Trial abuse * card testing * recurring declines * cancellation disputes * FX Launch recommendation Use cards for recurring self-service plans and PSE or transfer for one-time, annual, educational, or business invoices. Payment-Performance Measurement PSE visibility rate Eligible Colombian sessions showing PSE ÷ eligible Colombian sessions × 100 PSE selection rate Sessions selecting PSE ÷ sessions in which PSE was shown × 100 PSE completion rate Confirmed PSE payments ÷ initiated PSE payment requests × 100 Bank-return recovery rate Customers returning to a recoverable merchant payment state ÷ customers leaving for bank authentication × 100 Card authorization rate Approved card authorizations ÷ submitted card authorization attempts × 100 Segment by: * Issuer * Domestic versus foreign card * Debit versus credit * Installment plan * Authentication * Provider route Wallet completion rate Completed wallet payments ÷ initiated wallet payments × 100 Instant-payment match rate Instant payments automatically matched to the correct order ÷ instant payments received × 100 Refund completion rate

Completed refunds ÷ valid refund requests submitted × 100 Reconciliation-exception rate Records requiring manual investigation ÷ records expected to reconcile × 100 Cost per completed order Payment, provider, fraud, FX, installment, cash, refund, and relevant operational costs ÷ completed paid orders Retained revenue Successfully collected revenue remaining after: * Refunds * Chargebacks * Fraud * Failed installment adjustment * Payment fees * Relevant direct variable costs Do not rely on one blended Colombian payment-success rate. Merchant Recommendations by Stage Merchant testing demand Launch with: * COP * Spanish checkout * Cards * PSE * Complete refunds * Basic settlement and reconciliation One suitable wallet may be added when target-audience evidence supports it. Merchant launching Colombia Prepare: * PSE bank-return handling * Colombian-issued card testing * Mobile authentication * Spanish support * Payment-status recovery * Refund testing * COP settlement review * Tax and regulatory review * Fraud communication Merchant scaling volume Evaluate: * Local acquiring * Installments * Additional wallets * Bre-B merchant products * Routing * Provider costs * COP treasury * Local fraud models * Cash replacement Merchant optimizing performance Segment by: * Method * Provider * Issuer * Domestic versus foreign card * Device * Customer region * New versus returning customer * Order value * Installment count * Authentication * Checkout version Merchant introducing subscriptions Prioritize: * Cards * Tokenization * Account updating

* Recurring indicators * Failed-payment recovery * Renewal messaging * Cancellation * PSE only for initial or one-time payments unless a recurring product is explicitly supported Merchant expanding regionally Reuse: * Stable payment intent * Card tokenization * Bank-redirect connector * Wallet connector * Refund states * Reconciliation identifiers * Multicurrency logic Keep Colombian: * PSE * Bre-B products * Wallets * Installments * COP * Tax * Settlement * Spanish support as configurable local components. Colombia Launch Checklist Market and customer * Confirm the target Colombian customer segment. * Reconfirm nominal GDP and global rank for the publication year. * Validate the latest ecommerce sales and transaction data. * Confirm product and merchant-category eligibility. * Identify whether trust, card access, bank access, or cash preference is the primary payment barrier. Checkout and methods * Price in COP. * Localize checkout in Colombian Spanish. * Offer PSE where relevant. * Support major international cards. * Test Colombian-issued debit and credit cards. * Evaluate one or more wallets by customer segment. * Track Bre-B merchant-payment developments. * Offer installments only with verified issuer and provider support. * Add cash-linked methods only where incremental economics justify them. * Make payment, delivery, refund, and support information visible before submission. Technical readiness * Preserve payment state through PSE, bank, wallet, and 3-D Secure redirects.

* Use internal payment-intent and attempt identifiers. * Implement idempotency. * Authenticate provider callbacks. * Deduplicate events. * Support status retrieval. * Handle pending and unknown outcomes. * Prevent duplicate fulfillment. * Test mobile deep links and browser fallback. * Localize every error state. Recurring and refunds * Separate one-time PSE payment from recurring authorization. * Tokenize eligible cards. * Configure failed-payment recovery. * Test full and partial card refunds. * Test PSE and bank-payment refunds. * Test wallet refunds. * Define cash-method refunds. * Test installment cancellations and partial refunds. Settlement and finance * Confirm processing, settlement, and payout currencies. * Confirm local bank-account and entity requirements. * Validate provider fees and FX. * Reconcile order through bank receipt. * Monitor settlement delays. * Create a manual exception queue. * Define refund and chargeback ownership. Regulation, tax, and risk * Verify the provider’s regulatory and contractual role. * Review Colombian VAT and foreign-service obligations. * Review electronic invoicing. * Review marketplace and payout responsibilities. * Prepare method-specific fraud controls. * Provide fraud-aware Spanish customer communication. * Assign payment, finance, fraud, tax, compliance, support, and treasury owners. * Establish a post-launch review date. Final Merchant Recommendation

Colombia should be prioritized by merchants that can serve a growing digital consumer market without assuming that every valuable customer wants to enter card details. The strongest immediate opportunities include: * Marketplaces * Gaming * Education * Travel * Fashion * Digital media * SaaS * On-demand services The recommended initial proposition for most domestic B2C merchants is: 1. COP pricing 2. Colombian Spanish checkout and support 3. PSE 4. Major card acceptance 5. Reliable mobile and bank-return recovery 6. Transparent fraud-aware communication 7. Complete method-specific refunds 8. COP settlement and reconciliation readiness Marketplaces and retail merchants should make PSE prominent and evaluate wallets, installments, and cash-linked methods according to customer and order economics. Gaming and digital-media merchants should combine cards with at least one trusted account- or wallet-based option and protect the customer account as carefully as the payment credential. Education merchants should prioritize PSE, transfer references, cards, and installment handling. Travel merchants should combine domestic bank payment with strong Colombian and international card acceptance. SaaS and subscription merchants should use cards for recurring collection while offering PSE or bank transfer for one-time, annual, educational, or B2B invoices.

Bre-B should be monitored closely as interoperable instant-payment products mature, but merchants should not assume that infrastructure availability already equals complete ecommerce acceptance. Colombia’s core payment problem is not simply whether a payment can be processed. It is whether the customer can access a trusted method, understand what is happening, recover from uncertainty, receive a clear refund, and believe that the merchant will still be accountable after the money moves.

The Colombia guide below follows the uploaded brief’s controlling angle: a checkout-trust diagnostic showing why card acceptance alone can leave substantial demand unreached. It places PSE, wallets, instant payments, Spanish-language communication, fraud awareness, refunds, and settlement around the central question of whether the customer trusts the merchant enough—and has the right access—to complete payment. Editorial Interpretation Country-specific evidence anchor Colombia’s ecommerce market surpassed COP 105 trillion in online sales during 2024, increasing 26.7% from the previous year, while the number of online transactions rose 21%. At the same time, bank-based payments, digital deposits, wallets, cards, cash, and new interoperable instant-payment infrastructure remain commercially relevant. (Cámara de Comercio Electrónico) Editorial position Merchants should combine cards with trusted bank-based access and strong, fraud-aware customer communication. A card-led proposition may serve internationally oriented and recurring-payment customers. It should not be mistaken for a complete Colombian checkout strategy. Common assumption being challenged “If a merchant accepts major international cards in Colombian pesos, it can reach most commercially valuable online customers.” Merchant decision being supported This guide helps merchants decide: * Whether PSE should be essential at launch

* How cards, wallets, Bre-B, bank transfers, cash-linked methods, and installments fit different customer journeys * When local acquiring or a local PSP may be justified * How trust, Spanish-language communication, authentication, and fraud controls affect conversion * Which methods are suitable for subscriptions * What refund, settlement, reconciliation, and tax operations must be ready before significant investment Selected structure A checkout-trust diagnostic sequence: 1. Can the customer access the offered methods? 2. Does the merchant appear trustworthy? 3. Is a familiar bank-based option available? 4. Can cards work for the relevant segment? 5. Does mobile authentication preserve the checkout? 6. Are payment states explained correctly? 7. Can every method be refunded? 8. Can finance trace the transaction to usable funds? Can the merchant recover legitimate revenue without weakening fraud controls?

Editorial Recommendations Package SEO Recommendations Recommended SEO title Payments in Colombia: PSE, Cards and Merchant Guide Alternative title options 1. Colombia Payment Methods for Global Merchants 2. How to Accept Payments in Colombia 3. Payments in Colombia: PSE, Wallets and Cards 4. Colombia Ecommerce Payments and Market Entry Guide 5. Colombian Payment Methods, PSE and Local Acquiring Recommended H1 Payments in Colombia: Bank Transfers, Wallets, and a Growing Digital Consumer Market Meta description Learn how Colombian customers pay with PSE, cards, wallets, Bre-B and cash methods, plus guidance on COP, fraud, refunds and settlement. URL slug /payments-in-colombia Primary keyword Payments in Colombia Secondary keywords * Colombia payment methods * Accept payments in Colombia * PSE payments * Colombia ecommerce payments * Colombia digital wallets * Bre-B payments * Colombia payment gateway * Colombia local acquiring * COP payments * Colombian card installments * Colombia bank transfer payments Related entities * Colombian peso * COP * PSE * ACH Colombia * Bre-B * Banco de la República * Superintendencia Financiera de Colombia * Digital deposits * Wallets * Bank transfer * Instant payments * Installments * Local acquiring * VAT * Electronic invoicing Search intent Market research, payment-method selection, checkout localization, and Colombia market entry. Article excerpt

Colombia’s ecommerce market is growing quickly, but valuable customers do not all follow a card-first payment journey. This guide explains how PSE, cards, wallets, Bre-B, installments, fraud communication, refunds, and settlement affect merchants. Social description A card-only checkout can miss Colombia’s bank- and wallet-based customers. Learn how PSE, Bre-B, cards, installments, refunds, and trust shape payment strategy. Structured-Data Recommendation Use: * Article * BreadcrumbList * Person for a verified author

Use FAQPage only if a visible FAQ section is later added. Internal-Link Recommendations * How to Expand Payments Into a New Country * International Payment Expansion Checklist * What to Evaluate Before Entering a New Market * How to Build a Global Payments Strategy * One Global PSP vs Multiple Local PSPs * How to Select a PSP for International Expansion * Payment Infrastructure for Global Expansion * Global Payment Gateway vs Local PSP * Merchant of Record vs PSP * Payment Orchestration for International Expansion * How to Launch Payments Without Rebuilding Your Stack * Authorization Rates by Country * Authorization Rates by Payment Method * Authorization Rates by Issuer * How Authentication Affects Conversion * Why Customer Payments Are Declined Authoritative External-Source Recommendations Use current versions of: * IMF World Economic Outlook * DANE economic, ICT, household, and digital-economy data * Colombian Chamber of Electronic Commerce reports * Banco de la República payment-infrastructure reports * Official Bre-B documentation * Superintendencia Financiera financial-inclusion reports * ACH Colombia and PSE documentation * DIAN VAT and electronic-invoicing guidance * Official bank, wallet, card-network, and acquiring documentation

Original Asset Recommendations 1. Colombia Checkout Trust Diagnostic Purpose: Help merchants identify whether loss occurs through access, trust, authentication, payment state, refund, or settlement. Intended reader: Product, payments, engineering, marketing, support, and finance teams. Diagnostic stages: * Method access * Merchant trust * PSE visibility * Card suitability * Mobile authentication * Payment-state clarity * Refund readiness * Settlement traceability * Fraud recovery Data required: * Checkout sessions * Method visibility and selection * Redirect completion * Authorization * support contacts * refunds * settlement exceptions Recommended format: Diagnostic decision tree with red, amber, and green outcomes. Placement: Immediately after the country snapshot. 2. PSE Merchant Payment Journey Purpose: Explain how the customer, merchant, PSP, ACH infrastructure, and bank interact. Intended reader: Engineering, payment operations, customer support, and finance. Flow: Checkout → PSE request → financial-institution selection → bank authentication → payment result → provider notification → merchant status → settlement → refund Data required: * Order ID * payment-intent ID * provider reference * bank status * callback * settlement batch * refund reference Recommended format: Customer-and-system swimlane. Placement: Within the PSE section. 3. Colombia Trust-to-Payment Matrix Purpose: Match customer trust and financial access to the most appropriate method.

Intended reader: Market researchers, payment strategists, and growth teams. Example rows: * Banked customer avoiding card entry * Recurring SaaS customer * Mobile wallet user * Higher-value installment buyer * International traveler * Payment-cautious physical-goods buyer * B2B invoice customer Columns: * Trust barrier * Available instrument * Best method * recurring suitability * refund complexity * operating cost * launch priority Recommended format: Segment matrix. Placement: After “How Customers Pay.” Visual Recommendations Hero image concept Show a Colombian mobile shopper at the center of a trust-based payment ecosystem: * PSE bank payment * Card * Wallet * Bre-B instant payment * Installments * Refund and support The merchant checkout should visibly connect to bank authentication, order status, and settlement. Avoid generic Bogotá skyline, flag, or cashless-payment imagery. Suggested caption: Colombia’s payment opportunity depends on connecting trusted bank and wallet access with cards, clear status communication, refunds, and settlement. Alt text: “Colombian mobile shopper choosing between PSE, payment card, digital wallet, Bre-B instant payment, and installment options.” Diagram concept Where a Colombian Checkout Loses Trust Stages: Merchant identity → COP price → method availability → PSE or card authentication → customer return → order confirmation → refund → settlement Alt text: “Colombia checkout trust diagnostic showing payment access, authentication, order status, refund, and settlement stages.”

Chart concept Use the Colombian Chamber of Electronic Commerce’s 2024 figures to show: * More than COP 105 trillion in online sales * 26.7% annual sales growth * 21% annual transaction-count growth State that these are ecommerce-industry measures and do not represent the entire digital economy. (Cámara de Comercio Electrónico) Instant-Payment Evolution Timeline Show: * Established PSE ecommerce role * Transfiya and other existing immediate-transfer products * Bre-B launch in October 2025 * Early 2026 adoption * Future merchant-payment capabilities subject to verification Avoid suggesting that Bre-B has already replaced PSE. Human Review and Contribution Recommendations Required before publication * Colombia regional payments specialist: Validate PSE, cards, wallets, installments, cash behavior, and Bre-B implications. * Payment product specialist: Review method hierarchy and checkout-state design. * Legal or compliance reviewer: Verify payment-system, wallet, marketplace, and provider-role statements. * Tax reviewer: Confirm VAT, foreign-service, electronic-invoicing, and marketplace language. * Operations and reconciliation specialist: Validate refunds, settlement, and financial traceability. * Colombian Spanish reviewer: Review terminology and customer-facing language. Strongly recommended * Fraud specialist: Review PSE, card, wallet, instant-payment, gaming, marketplace, and social-engineering risks. * Treasury specialist: Review COP settlement, FX, reserves, and payout structures.

* Subscription-payments specialist: Review card recurring and account-based alternatives. * Marketplace specialist: Review seller onboarding, payouts, safeguarding, disputes, and tax. * Mobile integration reviewer: Validate bank-redirect and app-return guidance. * Market analyst: Confirm vertical and digital-commerce claims. Optional enhancement Include one approved first-hand contribution about: * A card-only launch adding PSE * A bank payment succeeding while the order remained pending * A customer retrying because a PSE return page was unclear * A wallet appearing popular but contributing few incremental orders * A merchant discovering that installments required a different acquiring arrangement * A PSE or transfer refund needing unexpected manual processing * A marketplace struggling to reconcile buyer payments and seller payouts * A Bre-B use case that was available for transfer but not yet mature for ecommerce Do not imply that any contribution has already been collected. Final Fact-Check List Verify immediately before publication: * Colombia’s current nominal GDP and global rank * Population and year * Ecommerce sales value and growth * Online transaction count * Digital-economy definition and any current GDP estimate * Internet and smartphone use * Mobile-commerce share * Financial-product access and active use * Cash usage * PSE merchant, user, and transaction statistics * PSE participating institutions * PSE refund functionality * Wallet adoption and active use * Digital-deposit usage

* Card ownership and online card use * Installment adoption * Cash-on-delivery and voucher use * Bre-B user, alias, merchant, and transaction statistics * Bre-B ecommerce functionality * Local-acquiring availability * Entity and bank-account requirements * COP settlement * Recurring-payment support by method * Provider regulatory roles * Marketplace payment and payout obligations * VAT rate and foreign-service obligations * Electronic-invoicing requirements * Settlement timing and reserves * Marketplace, gaming, education, travel, fashion, digital-media, SaaS, and on-demand growth claims

* Any claimed merchant result or performance improvement

Before publication, confirm: * COP presentment * COP processing * COP settlement * Colombian-issued card support * Domestic debit and credit-card support * International cards * PSE * PSE bank coverage * PSE mobile and desktop flows * PSE refunds and partial refunds * Specific wallets * Digital deposits * Bre-B or instant-payment support * Bank transfer * Cash voucher or cash-based payment * Cash-on-delivery support, if any * Installments * Local acquiring * Merchant eligibility * Local entity requirements * Colombian bank-account requirements * Hosted checkout * Direct API * Mobile SDK * Redirect and app-return recovery * Tokenization * 3-D Secure * Recurring payments * Account updater * Full and partial refunds * Chargeback support * Settlement timing * Reconciliation reports * Marketplace support * Seller payouts * Merchant of Record availability * Fraud tools * Spanish-language checkout and support * Any quantified merchant outcome