Weave Code
Sdk Laravel Package
mercadopago/sdk
Official Mercado Pago SDK for PHP. Add payments, checkout, subscriptions, and refunds to your Laravel or PHP app through a consistent API for managing preferences, customers, payments, and webhooks, making it easy to accept and process payments across Latin America.
DEPRECATED - MercadoPago PHP SDK
Frequently asked questions about Sdk
- Is mercadopago/sdk still maintained for Laravel?
- No. The repository is explicitly deprecated, and the last release was in 2019. It has no security patches, API version guarantees, or vendor support. Treat it only as a temporary adapter in legacy apps and plan migration.
- How do I install mercadopago/sdk with Composer in Laravel?
- Run composer require mercadopago/sdk and configure your access token through environment variables. Because the package is deprecated, its PHP and dependency constraints may conflict with current Laravel or PHP 8.x projects. Test installation in an isolated branch and sandbox, pin the version, and verify whether Laravel auto-discovery works or manual registration is needed. Do not assume Composer installation alone proves production compatibility.
- Does mercadopago/sdk support Laravel 10 and PHP 8.2?
- Not guaranteed. The last release was in 2019, before Laravel 10 and PHP 8.2 were current, so Composer constraints, Guzzle/PSR compatibility, and runtime behavior must be proven. Run a sandbox spike covering auth, payment creation, webhooks, and refunds. If conflicts appear, migrate to the current official SDK or a direct REST client.
- Can mercadopago/sdk create Checkout Pro preferences and process payments?
- The SDK provides preference and payment clients intended for Checkout Pro and Checkout API flows. However, it is deprecated, so the Mercado Pago endpoints and payload shapes it targets may have changed. Validate the exact flow in sandbox, then keep SDK calls behind a domain-owned gateway interface. Do not leak SDK models into controllers or jobs.
- How do I handle Mercado Pago webhooks or IPN in Laravel with this SDK?
- Create a Laravel route for the notification, verify Mercado Pago signatures and webhook secrets, and process updates asynchronously in a queue. The SDK includes webhook/IPN helpers, but you must confirm current payload compatibility and handle replay with idempotency keys. Log raw payloads, return quickly, and use reconciliation jobs for ambiguous states. Never trust an unverified notification to mark an order paid.
- Does mercadopago/sdk support subscriptions, marketplace split payments, and refunds?
- The SDK was designed with clients for subscriptions, marketplace split flows, and refunds, but each depends on your Mercado Pago account configuration and current API version. Because the package is deprecated, you must prove every required flow in sandbox against live documentation. Wrap these calls in an adapter and add contract tests. Do not assume marketplace or subscription support remains unchanged.
- How should I test mercadopago/sdk payments before going to production?
- Use Mercado Pago sandbox credentials and test users in a non-production environment. Keep test and live access tokens separate, and never put live credentials in CI. Exercise auth, preference creation, payment status transitions, webhook handling, refunds, timeouts, and error responses. Capture results as contract tests for the adapter you will keep after migration.
- What are the production risks of using a deprecated Mercado Pago SDK?
- Risks include breaking Mercado Pago API changes, auth or token expiry, webhook replay and signature failures, duplicate charges from retries, timeouts with ambiguous payment states, TLS or PHP runtime deprecations, and credential leakage. Add idempotency keys, bounded retries with backoff, queued payment workers, dead-letter queues, structured logs, metrics, alerting, and reconciliation jobs. Assign a named internal owner and scan dependencies for vulnerabilities. Manual review should catch stuck or mismatched payments.
- Should I wrap mercadopago/sdk behind an adapter in Laravel?
- Yes, that is the recommended containment strategy if you must use it. Define a domain-owned payment gateway interface and keep SDK models, exceptions, and raw HTTP details out of controllers, jobs, and domain services. Pin dependencies and vendor or fork the package under an internal namespace with explicit ownership. Budget a migration to the current official SDK or direct REST client.
- What is the migration path from mercadopago/sdk?
- Migrate to the current official Mercado Pago SDK if it fits your stack, or use a direct HTTPS REST client behind your own gateway interface. Inventory required flows, prove them in sandbox, add contract tests, and move one low-risk flow first. Run old and new paths in parallel where reconciliation allows, cut over with rollback, then decommission the deprecated SDK and rotate credentials.
Weaver
How can I help you explore Laravel packages today?