Recurring payments
Keep recurring payments connected to the customer relationship
Create and manage card subscriptions, monitor their status and recover failed charges with configurable retries. Live today in Colombia, Mexico and Peru; for other markets, our team maps a recurring flow on local payment methods with you.
- Scheduled or on-demand billing
- Configurable retries
- Every renewal traceable
Overview
USD
1,284,560.00
+4.2%
BRL
3,420,118.40
+12.8%
MXN
8,905,332.10
+6.1%
- Pay-in · Pixorder_8F2K-1043+ R$ 1,250.00
- Payout · SPEIseller_0921− MX$ 18,400.00
- FX · BRL → USDfx_3b7q250,000.00 USD
- Pay-in · Bre-Border_9A1C-2210+ COP 890,000
- Live today · other markets on request
- CO · MX · PE
- Scheduled and on-demand charges
- 2 models
- Configurable attempts and intervals
- Retries
- On every charge
- Webhook
Card subscriptions
Subscriptions with configurable retries
Everything you need to bill on a schedule, recover failed charges and keep your systems in sync.
Scheduled or on demand
Bill on a fixed schedule from a plan, or charge on demand when usage or events require it.
Configurable dunning
Set how many times to retry a failed charge and the interval between attempts, to fit your billing model.
Clear payment status
If all retry attempts fail, the subscription is marked accordingly so your team can take the next action.
Every charge is traceable
Every renewal is recorded as an individual transaction, with its own status, webhook and reporting data.
Plans API
Create, update and query plans with preset amounts and billing intervals.
Full control
Update the amount, frequency or payer details, change plans or cancel a subscription through the API.
Money flow
How a subscription charge runs
The card is tokenized once; each renewal is charged automatically, with configurable retries.
- 1
CustomerYour platform:
Subscribes with a card
Card data is tokenized once by Localpayment for recurring use.
- 2
Your platformLocalpayment:
Create the subscription
Plan, amount and billing cycle linked to the token.
- 3
LocalpaymentLocal rail / bank:
Charges each cycle
Local acquiring, so the issuer sees a domestic transaction.
- 4
Local rail / bankLocalpayment:
Approved or declined
Declines are retried on the schedule you configure.
- 5
LocalpaymentYour platform:
Webhook per charge
Your platform extends or pauses access based on the result.
Illustrative flow. Card subscriptions are available in Colombia, Mexico and Peru; see the country pages.
How it works
How a subscription runs
- 01
Create
Choose a fixed plan or a custom amount and frequency, then send POST /api/payin/subscriptions with the card token. You get the subscription ID back.
- 02
Renew
Each cycle is charged automatically, or on demand. Failed charges are retried according to your settings, and webhooks report every result.
- 03
Manage
Update the amount, frequency or payer details, change plans or cancel through the API, and track every change by webhook.
Specifications
Recurring payments at a glance
Card subscriptions
- How it works
- Available in Colombia, Mexico and Peru
- Details
- Scheduled or on demand billing with tokenized cards
Plans
- How it works
- Create and manage plans through the API
- Details
- Define amount, currency and billing frequency
Retries
- How it works
- Configure retry rules for failed payments
- Details
- Set the number of attempts and interval between retries
Subscription management
- How it works
- Update or cancel subscriptions through the API
- Details
- Manage amount, frequency, payer details or plan changes
Reporting
- How it works
- Track every renewal as an individual transaction
- Details
- Monitor status through webhooks and reporting
Limits and pricing
- How it works
- Defined by market and payment method
- Details
- Contact our team for details
Card subscriptions are currently available in Colombia, Mexico and Peru. Specific capabilities and commercial terms are confirmed during onboarding.
Operations
Renewals your finance team can trace
Because each renewal is recorded as an individual transaction, card subscriptions reconcile exactly like one-time payments — same identifiers, same webhooks, same reports.
- Your externalId plus our internalId on every charge
- HMAC-SHA256 signed webhooks for charges, failures and changes
- Chargeback handling for subscription charges
- Business Portal reports with XLS export
- 09:41:02.11409:41:02PayIn100 INPROGRESS20084 ms
- 09:41:05.90209:41:05PayIn200 COMPLETED20091 ms
- 09:42:18.33009:42:18PayOut100 INPROGRESS20077 ms
- 09:42:40.01809:42:40PayOut200 COMPLETED20088 ms
- 09:43:00.55109:43:00VirtualAccount200 COMPLETED20080 ms
POST https://example-merchant.com/webhooks/localpayment
x-Signature: HMAC-SHA256 3f9a1c0e…b47e2b
{ "transactionType": "PayIn", "transactionFlow": "DIRECT",
"data": { "externalId": "order_8F2K-1043",
"status": { "code": "200", "description": "COMPLETED" } } }For developers
Create a subscription in one call
Send the plan, the card token and your retry policy. Localpayment runs each charge from there and reports back by webhook.
- Fixed plans (planId) or custom amounts and frequencies
- retry.repetitions, retry.intervalValue and retry.intervalUnit
- Update or cancel through the API at any time
# Illustrative — fields simplified; see docs.localpayment.com for the full contract
curl -X POST https://api.stage.localpayment.com/api/payin/subscriptions \
-H "Authorization: Bearer $ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"paymentMethod": { "type": "CreditCard", "code": "1900", "flow": "DIRECT" },
"externalId": "5d7c2a90-0000-4000-8000-000000000031",
"country": "COL",
"currency": "COP",
"planId": "<your-plan-id>",
"accountNumber": "<your-account-number>",
"conceptCode": "0001",
"merchant": { "type": "COMPANY", "name": "Comercio Ejemplo S.A.S." },
"payer": {
"type": "INDIVIDUAL",
"name": "Andrés",
"lastname": "Gómez",
"document": { "type": "CC", "id": "1000000000" },
"email": "andres.gomez@example.com"
},
"card": { "token": "<card-token>" },
"retry": { "repetitions": 3, "intervalValue": 1, "intervalUnit": "day" }
}'Use cases
Built for businesses that bill again and again
Streaming & digital content
Monthly or annual plans, with tiers for different feature sets.
Streaming & digital content —SaaS
Software plans for B2B and B2C, with upgrades and downgrades through the API.
SaaS —Memberships & clubs
Gym memberships, club fees and loyalty programs on flexible billing cycles.
Utilities & telecom
Recurring payments for internet, mobile and other monthly services.
Frequently asked questions
Where are card subscriptions available?
In Colombia, Mexico and Peru, with both scheduled and on-demand models.
What happens when a renewal fails?
We retry according to the rules you configure. If every retry fails, the subscription is marked accordingly and no further automatic charges are attempted, so your team can take the next action.
Can I change a subscription after it starts?
Yes. You can update the amount, frequency or payer details, change the plan, or cancel through the API.
Do renewals show up in my reports?
Yes. Every renewal is recorded as an individual transaction, so it appears in your reports and webhooks like any other payment.
Can I collect subscriptions with local payment methods?
Card subscriptions run in Colombia, Mexico and Peru. For other countries, our team can map a recurring flow on local methods with you.
Also on the same API
Cards
Tokenization in Argentina, Colombia, Mexico and Peru; 3D Secure and installments in Colombia, Mexico and Peru.
Cards —Checkout
Capture the first payment with hosted fields or a no-code checkout.
Checkout —Reporting & reconciliation
Reports and APIs that tie every renewal back to your ledger.
Reporting & reconciliation —
Keep subscribers renewing
Tell us about your billing model and the markets you sell in: we’ll set up card subscriptions or map a recurring flow on local methods.

Scheduled or on-demand billing