Package: django-mercadopago-simple
As of 4.2.0, this package will be renamed to django-mercadopago on PyPI.
Please update your references.Imports and modules remain unchanged.django-mercadopago-simpleis a simple django application for interacting withMercadoPago, aiming to be rather simple,
and only covers the basic uses cases.FeaturesOur 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.InstallationInstallation should generally be done via pip:pip install django-mercadopago-simpleConfigurationYou’ll need to obtainer your API credentials (app idandsecret key)hereand  create anAccountobject 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 arerequired, since notification callbacks won’t
work without them.There are also a few Django settings that configure the behaviour of this app:MERCADOPAGO_AUTOPROCESSRequiredIfMERCADOPAGO_AUTOPROCESSisTrue, 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)MERCADOPAGO_POST_PAYMENT_VIEWRequiredThe settingMERCADOPAGO_POST_PAYMENT_VIEWmust define name of the view
where users are redirected after a payment.  This view will receive as an
argument theidof the notification created for this payment.MERCADOPAGO_BASE_HOSTRequiredMERCADOPAGO_BASE_HOSTdefines the domain name to use for notification URLs.
It’ll be prepended to the exact URL of the exposed notifications endpoint.UsageMercadoPago 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 apost_updatehook:@receiver(post_save, sender=MercadoPagoPayment)
def process_payment(sender, instance=None, created=False, **kwargs):
    do_stuff()Backwards compatibilityVersion 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.LicenceThis software is distributed under the ISC licence. See LICENCE for details.Copyright (c) 2015-2017 Hugo Osvaldo Barrera <hugo@barrera.io>