Latin American merchants running ERPNext hit a wall the moment they try to collect money the way their customers actually pay. ERPNext core ships generic payment gateway integrations (PayPal, Stripe, Razorpay, and a handful of others), but it has no native concept of Pix, boleto bancario, cash vouchers, or card installments (cuotas/parcelas) — the payment rails that dominate Brazil, Argentina, and Mexico. So teams end up reconciling Mercado Pago payouts by hand in spreadsheets, chasing unmatched boletos, and manually flipping Sales Invoices to Paid days after the money actually cleared. That manual gap is where cash-flow visibility and reconciliation accuracy quietly break down.

ECOSIRE builds a proper Frappe app — installed into your own ERPNext bench as an app you own — that makes Mercado Pago a first-class payment method inside ERPNext. It ships a Mercado Pago Settings single DocType for credentials (access token, public key, sandbox/production toggle, country site MLB/MLA/MLM) with secrets stored via Frappe's encrypted password fieldtype, and a Mercado Pago Transaction DocType that records every preference, payment, payment_id, status, and payout so each transaction is auditable against its Sales Invoice or Payment Entry. Customers pay through Checkout Pro (hosted) or embedded Bricks, choosing Pix, boleto, cash voucher, or card with the installment plans you allow. On approval, hooks.py doc events and server-side logic create and submit the matching Payment Entry, allocate it against the invoice, and move the document to Paid — no manual touch.

The engine of the integration is the Mercado Pago webhook (IPN). We expose a whitelisted Frappe REST endpoint (@frappe.whitelist(allow_guest=True)) that receives payment notifications, verifies the x-signature HMAC to reject forged calls, then re-fetches the authoritative payment status from the Mercado Pago API before writing anything — so a spoofed "approved" ping can never mark an invoice paid. Asynchronous states (Pix awaiting scan, boleto awaiting bank clearing, in-review card payments) are handled by a scheduler_events background job that polls pending transactions and reconciles late clearings, plus refund and chargeback handling that reverses the Payment Entry. Role profiles and permission rules keep credential access and manual re-sync actions restricted to Accounts Manager, while client scripts surface a "Pay with Mercado Pago" action and live status on the invoice form.

Because this is build-to-order, nothing is a black box you download blind. We start with a scoping call to confirm your Mercado Pago country/site, the payment methods and installment rules you need, your ERPNext version (v15 or v16), and whether checkout is triggered from ERPNext web forms, the POS, or an external storefront hitting the REST API. We then build against a staging copy of your instance, run UAT with you using Mercado Pago sandbox credentials, and cut over to production with a rollback plan. Typical delivery is one working week from confirmed scope. You receive the full source, a git repository handover, technical and user documentation, a training session, and a post-go-live support window — and you own the code outright.