
Payflow is a leading employee benefits platform that charges corporate clients on a recurring basis. In a market where bank transfers remain the default method for B2B transactions (due to the large sums involved), the bottleneck isn’t the payment itself, but everything that comes after: determining who paid, what the payment is for, and when the funds are actually available. Payflow was one of the pilot clients that allowed Cobre to validate and productize Transfer-In. What began as a manual experiment with two corporate accounts became, after demonstrating its fit with the needs of the Colombian B2B market, a full-fledged product. Today, Payflow operates with 130 active dedicated accounts.
Before integrating Cobre, the Payflow team relied on incomplete references, free-form descriptions in the transfer memo, and confirmations via email or chat to identify who had paid and which invoice the payment corresponded to. Every incoming payment required manual intervention: opening the bank statement, cross-referencing the amount with a list of outstanding invoices, and verifying with the client when the reference did not match.
The problem escalated with volume. The more corporate clients there were, the greater the reconciliation burden and the longer the delay in cash availability for payroll, suppliers, and operational obligations. No partial solution—such as reference templates, text rules, or semi-automatic reconcilers—solved the root of the problem, because they all relied on the same weak link: a free-text field that the payer could fill in however they wanted. In a business with recurring payments, that model imposed an operational ceiling: growth meant hiring more people to reconcile, not serving more customers.
The specific limitations of the previous model were:
Transfer-In assigns each Payflow corporate client a unique bank account based on a simple rule: any deposit into Client A’s account belongs to Client A. The reference field is no longer a free-text field but becomes the account itself. Payflow creates the payment intent via API with the amount, the payer’s identifier, and the relevant metadata; Cobre issues a dedicated account under Payflow’s NIT through its partner bank and detects the incoming transfer by continuously polling the bank. When the payment arrives, the merchant’s balance is automatically credited, and a real-time webhook notifies the Payflow system with the amount, date, account, and reference.
This architecture solves the problem at its root because it shifts identification to the source of the payment, not the end. The funds become available within Cobre the moment they arrive, ready to be disbursed via Fast Pay to payroll, fees, or suppliers. At the end of the day, the funds are automatically consolidated into a Payflow account, with no GMF since it is a transfer between accounts held by the same account holder. The same workflow that operates for 2 clients operates for 130, with no rework required when scaling.
Features enabled by the integration:
Growth without a proportional increase in operational overhead. Payflow went from a pilot with two clients to 130 active dedicated accounts, increasing its monthly transaction volume by a factor of 4.3 without expanding the reconciliation team. The infrastructure handles the growth; the team focuses on exceptions.
Certainty in attribution from the very first second. Every payment arrives with a clear owner because the account serves as the reference. The team stopped asking the customer, “Was this transfer yours?” and the back office stopped relying on emails to close accounting cycles.
Cash available in real time for disbursement. Collections directly feed into Payflow’s Cobre balance, which disburses instantly via Fast Pay under amount and approval rules configured by the team. Incoming cash is reused immediately.
Auditable traceability without relying on the bank. Payflow checks the status of each payment via API or portal, with a complete history and webhooks that feed into its own systems. The information is no longer confined to a PDF statement but becomes structured data.
It is Cobre’s product for automating collections via bank transfer in Colombia. It assigns dedicated bank accounts to each payer, automatically detects incoming payments, and credits the merchant’s balance without manual reconciliation.
Each corporate client receives a unique bank account under the merchant’s NIT. Since the account itself identifies the payer, there is no reliance on free-text fields: every payment that arrives in that account unequivocally belongs to that client.
Any Colombian company that receives recurring transfers from corporate clients: payment platforms, B2B marketplaces, service providers, trust companies, and companies with cash-intensive operations. No technical expertise is required to use the portal.
Via API to create payment intentions and receive real-time webhooks with each deposit, or via the Cobre portal to operate without development. The webhooks provide the amount, date, account, and reference, ready for the merchant’s system to trigger billing, reconciliation, or disbursement.