In this article (17 sections)
In short: if you sell in Latin America, the usual approach to subscription billing is to combine two gateways: Stripe for customers paying with international cards, and Mercado Pago Subscriptions, available in seven countries in the region, for local payments. Both generate recurring charges, retry declined payments and handle trial periods. What they don't solve on their own is your business logic: plans, limits, access cutoffs and invoices. You build that yourself.
What "billing a subscription" means
Billing a subscription isn't charging once. It means storing a payment method, charging every month or year, and deciding what happens when a charge fails, when the customer changes plans or when they cancel. If it isn't handled well, the symptom is always the same: customers using the product without paying, or customers who pay and still lose access.
The cycle has five moments:
- Sign-up: the customer picks a plan and pays the first charge, or starts a free trial.
- Recurring charge: each period generates and collects the fee.
- Plan change: the customer moves up or down a plan, with the proportional adjustment that applies.
- Payment failure: the card expires or has no funds; the charge is retried and the customer is notified.
- Cancellation: the customer cancels, or access is cut after several failed attempts.
The two gateways most used
Stripe
Its documentation describes how, when you create a subscription, it generates invoices, attempts to collect them and manages the states of the cycle. It also handles payment retries and failed charges, and supports trial periods, plan changes and pauses (how subscriptions work in Stripe). It's the natural choice if you sell to businesses or individuals with international cards, or to customers in the United States and Europe.
Mercado Pago Subscriptions
According to its documentation, it allows automatic charges after the first payment, weekly, monthly or annual frequency, retries when a charge is declined, and free trial periods. It's available in Argentina, Brazil, Chile, Colombia, Mexico, Peru and Uruguay, and customers can pay with a Mercado Pago account or without one (Mercado Pago Subscriptions). It's the natural choice if your customers pay with local methods.
A comparison to help you decide
Criterion | Stripe | Mercado Pago Subscriptions |
|---|---|---|
Best for | Customers with international cards, global sales | Customers who pay with local methods |
Countries in the region | Depends on where your company is incorporated | Seven countries with documented coverage |
Charge retries | Yes, configurable | Yes, automatic |
Free trial | Yes | Yes |
Invoices | Generates invoices for each charge | Records the charge; the tax invoice is separate |
What you build yourself | Plans, usage limits and access cutoff | The same, plus the link to your system |
Before you choose, confirm that your company can open an account with each. Stripe's availability depends on the country where your company is registered, and commission terms vary by country and payment method.
What you still have to build
Gateways collect payments. Your SaaS decides what the charge does. You need to build:
- The plan catalog: prices, limits (users, projects, usage) and what each plan includes.
- The access cutoff: what happens when a payment fails. The usual approach is a few grace days, then limited access, not deleted data.
- Customer notices: a clear email before a charge fails and another when it does.
- Reconciliation: making sure what the gateway reports matches what your system reports.
- An admin panel: seeing who pays, who is on trial and who has fallen behind.
This panel is the piece that gets postponed most, and the one you need most in the first month. If you're deciding what goes into your product first, this article on a 30-day MVP helps set priorities.
The problem of declined charges
A charge can be declined because of an expired card, no available funds, or limits on international or recurring purchases. For that reason:
- Offer more than one payment method: cards and, where available, debit, bank transfer or cash payment.
- Retry with judgment: gateways include automatic retries, and setting them up well keeps you from losing charges to a temporary decline.
- Notify quickly: an email with a link to update the card helps more than waiting for the customer to notice.
- Don't cut access right away: a few grace days keep you from losing a customer over a temporary decline.
Currency: a separate issue
Charging in US dollars gives your revenue stability, but some local customers can't or don't want to pay in a foreign currency. Charging in local currency simplifies the sale, but exposes you to inflation and devaluation in that country. A common solution is to publish prices in dollars and charge in local currency at the day's exchange rate, or to keep price lists by country and review them every quarter. Set this rule at the beginning, because changing it with active customers is costly.
Invoices and taxes
A receipt generated by the gateway doesn't replace the invoice your local tax authority requires. That part depends on where your company is based and where your customers are, and it's worth defining with a local accountant before launch. What you can do from the design stage is have your system store the customer's tax details (legal name, tax ID, country) at sign-up, so you don't have to ask for them later.
Security: don't store cards
The organization that sets card security standards recommends storing as little as possible and delegating processing to a provider that meets the standard (PCI Security Standards Council). In a SaaS, that means card data never passes through your system: the gateway handles it and you only store a reference. If your product adds another gateway later, this article on integrating two systems explains what to expect in cost and timing.
What it costs to build
Integrating subscription billing is one part of building a SaaS, not a separate project. At Atomix, a complete SaaS with sign-up, plans, recurring billing and an admin panel falls in the range of USD 5,000 to 10,000 per project; only exceptional projects of much larger scope go above that. Before quoting, we deliver a free working demo in 24 to 48 hours, and in most cases the product reaches production in under a month. The service is described on the SaaS development page. If you want to review your billing model, you can book a call.
Frequently asked questions
Can I use only Stripe to charge across Latin America?
You can charge customers with cards in many countries, but some local customers will prefer methods that Stripe doesn't cover equally well. Combining it with a local gateway usually improves conversion.
What happens if a customer misses a payment?
The gateway retries the charge according to the rules you set. If it keeps failing, your system decides: send a notice, allow a few grace days and then limit access. Avoid deleting data at the first late payment.
Can I offer a free trial?
Yes, both gateways support it. The business decision is whether you ask for a card when the trial starts. That lowers sign-ups but raises the share of trials that convert to paying customers.
How do I change plans mid-month?
Gateways calculate the proportional adjustment for the remaining days. You decide whether the change takes effect immediately or at the next billing period.
Do I need a dashboard to manage subscriptions?
Yes. Without one, every customer question means logging into the gateway and matching data by hand. It's one of the first pieces worth having in place.