Edit
settings.py
and addpaypal.standard.ipn
to yourINSTALLED_APPS
:settings.py:
#... INSTALLED_APPS = [ #... 'paypal.standard.ipn', #... ]
For installations on which you want to use the sandbox, set PAYPAL_TEST to True.
/updatedb
Create an instance of the
PayPalPaymentsForm
in the view where you would like to collect money.You must fill a dictionary with the information required to complete the payment, and pass it through the
initial
parameter when creating thePayPalPaymentsForm
.Call
render
on the instance in your template to write out the HTML.views.py:
from paypal.standard.forms import PayPalPaymentsForm def view_that_asks_for_money(request): # What you want the button to do. paypal_dict = { "business": "receiver_email@example.com", "amount": "10000000.00", "item_name": "name of the item", "invoice": "unique-invoice-id", "notify_url": "https://www.example.com" + reverse('paypal-ipn'), "return_url": "https://www.example.com/your-return-location/", "cancel_return": "https://www.example.com/your-cancel-location/", "custom": "Upgrade all users!", # Custom command to correlate to some function later (optional) } # Create the instance. form = PayPalPaymentsForm(initial=paypal_dict) context = {"form": form} return render(request, "payment.html", context)
For a full list of variables that can be used in
paypal_dict
, see PayPal HTML variables documentation.payment.html:
... <h1>Show me the money!</h1> <!-- writes out the form tag automatically --> {{ form.render }}
When someone uses this button to buy something PayPal makes a HTTP POST to your "notify_url". PayPal calls this Instant Payment Notification (IPN). The view
paypal.standard.ipn.views.ipn
handles IPN processing. To set the correctnotify_url
add the following to yoururls.py
:from django.conf.urls import url, include urlpatterns = [ url(r'^paypal/', include('paypal.standard.ipn.urls')), ]
Whenever an IPN is processed a signal will be sent with the result of the transaction.
The IPN signals should be imported from
paypal.standard.ipn.signals
. They are:valid_ipn_received
This indicates a correct, non-duplicate IPN message from PayPal. The handler will receive a
paypal.standard.ipn.models.PayPalIPN
object as the sender. You will need to check thepayment_status
attribute, and thereceiver_email
to make sure that the account receiving the payment is the expected one, as well as other attributes to know what action to take.invalid_ipn_received
This is sent when a transaction was flagged - because of a failed check with PayPal, for example, or a duplicate transaction ID. You should never act on these, but might want to be notified of a problem.
Connect the signals to actions to perform the needed operations when a successful payment is received (as described in the Django Signals Documentation).
In the past there were more specific signals, but they were named confusingly, and used inconsistently, and are now deprecated. (See v0.1.5 docs for details)
Example code:
from paypal.standard.models import ST_PP_COMPLETED from paypal.standard.ipn.signals import valid_ipn_received def show_me_the_money(sender, **kwargs): ipn_obj = sender if ipn_obj.payment_status == ST_PP_COMPLETED: # WARNING ! # Check that the receiver email is the same we previously # set on the business field request. (The user could tamper # with those fields on payment form before send it to PayPal) if ipn_obj.receiver_email != "receiver_email@example.com": # Not a valid payment return # Undertake some action depending upon `ipn_obj`. if ipn_obj.custom == "Upgrade all users!": Users.objects.update(paid=True) else: #... valid_ipn_received.connect(show_me_the_money)
See the
variables
documentation for information about attributes on the IPN object that you can use.You will also need to implement the
return_url
andcancel_return
views to handle someone returning from PayPal.Note that return_url view needs @csrf_exempt applied to it, because PayPal will POST to it, so it should be custom a view that doesn't need to handle POSTs otherwise.
When using PayPal Standard with Subscriptions this is not necessary since PayPal will route the user back to your site via GET.
For
return_url
, you need to cope with the possibility that the IPN has not yet been received and handled by the IPN listener you implemented (which can happen rarely), or that there was some kind of error with the IPN.
If you are attempting to test this in development, using the PayPal sandbox, and your machine is behind a firewall/router and therefore is not publicly accessible on the internet (this will be the case for most developer machines), PayPal will not be able to post back to your view. You will need to use a tool like https://ngrok.com/ to make your machine publicly accessible, and ensure that you are sending PayPal your public URL, not localhost
.
The PayPal IPN simulator at https://developer.paypal.com/developer/ipnSimulator has some unfortunate bugs:
- it doesn't send the
encoding
parameter. django-paypal deals with this using a guess. the default 'payment_date' that is created for you is in the wrong format. You need to change it to something like:
23:04:06 Feb 02, 2015 PDT
subscriptions
encrypted_buttons