Skip to main content
This is a pre-production deployment of Warehouse. Changes made here affect the production instance of PyPI (pypi.python.org).
Help us improve Python packaging - Donate today!

MercadoPago integration for django

Project Description

django-mercadopago is a simple django application for interacting with MercadoPago, aiming to be rather simple, and only covers the basic uses cases.

Features

Our intention is not to cover 100% of the features of the upstream API, but rather provide a simple app that allows accepting and tracking payments. This should suffice for simple sites like shopping carts, online sales, etc.

Pull requests are always welcome. Please don’t hesitate to open an issue if you encounter a problem. New features will generally only be added as needed, but again, accepted if you submit a patch.

Installation

Installation should generally be done via pip:

pip install django-mercadopago

Configuration

You’ll need to obtainer your API credentials (app id and secret key) here and create an Account object with them. This creation can be done via the django admin included with this app or programmatically.

You should also expose the notifications endpoints like this:

url(r'^mercadopago/', include('django_mercadopago.urls'), namespace='mp'),
# Make sure namespace is 'mp', since we assume it is for notification URL
# contruction.

Note that these endpoints are required, since notification callbacks won’t work without them.

There are also a few Django settings that configure the behaviour of this app. All these settings are included in a single dict inside your Django settings:

MERCADOPAGO = {
    'autoprocess': True,
    'success_url': 'myapp:mp_success',
    'failure_url': 'myapp:mp_failure',
    'pending_url': 'myapp:mp_pending',
    'base_host': 'https://www.mysite.com
}

AUTOPROCESS

Required

If set to True, notifications will be processed as soon as they are received. Otherwise, it’s up to the developer to process them.

A signal is always fired when a notification has been created, and a common pattern if not auto-processing is to have a celery task to process them:

@receiver(notification_received)
def process_notification(sender, **kwargs):
    tasks.process_notification.delay(notification=sender)

SUCCESS_VIEW

Required

The named URL pattern where requests are redirected after a user successfully completes a payment. This url will receive as an argument the id of the notification created for this payment.

For example, this if this value were set to payment_recived, a corresponding URL pattern would look like this:

url(
    r'pago_recibido/(?P<pk>.*)$',
    order.OrderPaidView.as_view(),
    name='payment_received',
),

FAILURE_VIEW

Required

The named URL pattern where requests are redirected after a user payment fails. This url will receive as an argument the id of the preference that the user attempted to pay

PENDING_VIEW

Required

The named URL pattern where requests are redirected after a user completes a payment, but confirmation is pending (for example, a transaction that takes a few days, bank deposit, etc). This url will receive as an argument the id of the preference that the user is attempting to pay.

BASE_HOST

Required

Defines the domain name to use for notification and callback URLs. It’ll be prepended to the exact URL of the exposed notifications endpoint.

Usage

MercadoPago lets you create preferences, for which you’ll later receive notifications (indicating if it was paid, or what happened):

self.preference = Preference.objects.create(
    title='the product name',
    price=10.0,
    reference='order-38452',
    success_url='http://example.com/mp_done',
    account=account,
)

If your app will only be using a single MercadoPago account, just use:

account = Account.objects.first()

Finally, you can handle payment notifications in real time using a post_update hook:

@receiver(post_save, sender=MercadoPagoPayment)
def process_payment(sender, instance=None, created=False, **kwargs):
    do_stuff()

Backwards compatibility

As of v5.0.0, the notification and callback URL formats generated by v4.2.0 and earlier is no longer supported. Users must upgrade to v4.3.0, and run this version until all pending payments are completed (or expire), and only then upgrade to v5.0.0.

Note that, prior to v4.2.0, this package was called django-mercadopago-simple on PyPI. Older release exist under that name.

Version 2.0.0 changes the database schema quite a bit. While older data is retained, some missing fields had to be filled. Auto-generated data will have negative key values, and should easily be recognizable.

Regrettably, filling in this data automatically is not possible. However, there is no data loss involved.

Licence

This software is distributed under the ISC licence. See LICENCE for details.

Copyright (c) 2015-2018 Hugo Osvaldo Barrera <hugo@barrera.io>

Release History

Release History

This version
History Node

5.0.1

History Node

5.0.0

History Node

4.6.3

History Node

4.6.2

History Node

4.6.1

History Node

4.6.0

History Node

4.5.0

History Node

4.4.0

History Node

4.3.0

History Node

4.2.0

History Node

0.0.4

History Node

0.0.3

History Node

0.0.2

Download Files

Download Files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
django_mercadopago-5.0.1-py3-none-any.whl (27.9 kB) Copy SHA256 Checksum SHA256 py3 Wheel Jan 13, 2018
django-mercadopago-5.0.1.tar.gz (19.2 kB) Copy SHA256 Checksum SHA256 Source Jan 13, 2018

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting