Getting a Mercado Pago SMS code into your test run

What problem are teams solving at the Mercado Pago phone step?

Mercado Pago, the payments and digital-wallet platform from Mercado Libre, is part of everyday commerce across Latin America. Like most financial apps, it ties an account to a phone number: an SMS code confirms the number at sign-up, and the app may ask for a fresh code when someone signs in on a new device or recovers access. For teams that build around it, such as merchants wiring up checkout, agencies operating a client's seller account, or QA engineers testing a marketplace that offers Mercado Pago at payment, that SMS step is often the awkward part. Staff end up putting personal phone numbers on business accounts, or a test case stalls because the one person holding the right SIM is offline.

OTP Route turns that step into something your tooling can handle: a number on demand for the market you need, with the code delivered to your systems. That is the core of Mercado Pago SMS verification for testing.

How does the Mercado Pago verification code API flow work?

All requests hit https://otproute.com/api/v1 with a Bearer key (prefix or_live_) from the Developer console. The service id is mercado_pago; the country id is the api_country value for your market, for example br for Brazil or mx for Mexico.

1. GET /api/v1/prices?country=br&service=mercado_pago returns the live price and availability for that pairing.
2. POST /api/v1/activations with {"service": "mercado_pago", "country": "br"} returns the activation id and the number.
3. Enter the number at the phone step of the account you are setting up or testing.
4. Pick up the code when activation.sms_received reaches your endpoint, or by polling GET /api/v1/activations/{id}.
5. If the run ends early, call POST /api/v1/activations/{id}/cancel.

Use GET /api/v1/balance as a pre-flight check. Each account gets 10 keys, 5 webhook endpoints and 300 requests per minute; everything else is in the docs.

How should the webhook handler treat Mercado Pago codes?

Push delivery keeps test runners from spinning in polling loops. Every event comes with X-OTPRoute-Signature: t=<unix>,v1=<hex>; compute HMAC-SHA256 of <t>.<raw body> using the endpoint secret, compare in constant time, and drop requests with old timestamps. Then make the handler idempotent: store the activation id and ignore a second delivery of the same event, because retries happen. Listen for activation.expired and activation.cancelled too, so the runner can release its slot and flag the test for another attempt. If you would rather not host an endpoint, polling the activation every few seconds stays well inside the rate limit. Securing OTP webhooks has a fuller checklist.

Which country should the Mercado Pago number come from?

The mercado_pago service is listed in 201 countries on OTP Route, but the useful choice is almost always the market the account belongs to. Mercado Pago is best known in Brazil, Argentina, Mexico, Chile, Colombia, Uruguay and Peru, so that is where most test cases live. The catalog also reaches Ecuador, Bolivia, Paraguay, Costa Rica, Panama, the Dominican Republic, Spain, Portugal and the United States, among many others.

A number from the wrong country can fail validation or prompt extra checks, and it tells you nothing about how real users in that market experience the flow. Match the test case: Brazilian onboarding gets a Brazilian number, Chilean onboarding a Chilean one.

What can I do from the dashboard instead?

Non-developers reach the same result without code. Open the OTP Gateway, choose Mercado Pago as the service, choose the country, and check the price shown before ordering. Copy the number into the app, request the SMS, and the code appears on the activation card as soon as it is delivered. The number is held for 20 minutes; if nothing arrives, nothing is charged, since the amount returns to your wallet automatically.

Why might a Mercado Pago code not arrive?

Payment platforms are careful about phone numbers, and a virtual number for Mercado Pago may be refused in some or all flows. Routes also change during the day. If a code doesn't show:

• Let the 20-minute window finish; the refund is automatic.
• Avoid re-ordering in a tight loop. Space attempts out or come back later.
• Try another route for the same market if one keeps expiring.
• Check that the phone field received the number in the format the app expects.

When a flow consistently rejects virtual numbers, accept that result and use a real line for that account. Reducing failed OTP deliveries covers the wider diagnosis.

When does a Dedicated Number make more sense?

A one-time number handles one code. A business account that will ask for a fresh code months from now needs a number you still control. OTP Route's Dedicated Numbers fill that role in the United States and Canada, from $1.95/month: inbound SMS in the dashboard and on your webhook (number.sms_received), outbound SMS and browser calling, renewing from the wallet until you release the line. Outside those two countries there is no self-serve long-term line; email [email protected] to ask, with availability depending on local rules. See virtual numbers for details.

What rules apply when using these numbers with Mercado Pago?

Mercado Pago moves real money, and its identity checks exist for good reasons. A phone number from OTP Route does not replace those checks and must never be used to sidestep them: complete identity verification with genuine details, keep one account per real person or business, and follow Mercado Pago's terms alongside OTP Route's Acceptable Use Policy. The platform is for testing your own product and operating your own legitimate accounts, not for opening accounts in volume or claiming promotions. Billing is pay as you go from a prepaid USD wallet (card or USDT/USDC, with a PDF invoice for every top-up), and a sandbox with simulated codes is available on request for integration tests. Mercado Pago is a trademark of its owner, and OTP Route is not affiliated with it.

Frequently asked questions

Can I receive a Mercado Pago OTP without a local SIM in Brazil or Mexico?

Yes, when you are testing or operating your own account. Order a mercado_pago number for the right country and read the code from the dashboard, the API or a webhook.

What is the service id for Mercado Pago in the API?

It is mercado_pago. Combine it with the country id in the body of POST /api/v1/activations.

Does Mercado Pago accept virtual numbers?

Not always. It may reject them for some flows, which is why the full amount is refunded when no code arrives within 20 minutes.

How much does a Mercado Pago phone number for verification cost?

From $0.20 per code. The exact price depends on the country and is shown by the API and the dashboard before you order.

Can I use the same one-time number to log in again next month?

No. A one-time number receives a single code. Accounts that need repeat sign-ins are better served by a US or Canadian Dedicated Number.

Can my CI pipeline exercise the Mercado Pago flow without real charges?

Yes. Ask for sandbox mode on a development account; it returns simulated numbers and codes through the same endpoints.

Service names are trademarks of their respective owners. OTP Route is not affiliated with them. Use numbers lawfully, follow each service's terms and our Acceptable Use Policy.