Skip to main content

PXPay payment plugin

Project description

This package contains pxpay for getpaid.


0.4 (2009-10-30)

  • add an explicit certs.pem and add known CAs that paymentexpress are using.

0.3 (2008-12-31)

  • put order id into TxnData1 so that exported DPS reports have an order id we can cross check against orders in getpaid order manager [matt.halstead]

0.2 (2008-08-29)

  • Added buildout files and general text documents to project root.

  • removed setup.cfg

Detailed Documentation

This is a Payment Processor for the PaymentExpress PXPay hosted Payments solution SEE:


You need to load both the package zcml and the overrides.zcml

In buildout, make sure you have the egg getpaid.pxpay installed, in the zope instance configuration, add the following:

eggs = getpaid.pxpay


We hook into the last checkout and payment step of the checkout so that the user is redirected to the pxpay web interface to fill out their credit card details and the redirected back to our site where we handle success or failure status of the transaction.

Deferred payment, repeating payments, authorisations, etc, are not yet implemented, but the PXPay interface supports them, so there’s no reason they can’t be added.

Orders and Finance workflow

An orders persistence and workflow is managed entirely by this payment processor. Since we hook into the last step of the checkout, we are responsible for creating the order, storing it in the manager, and handling the finance workflow.

When a user selects “make payment”

  • an order is created and stored in the order manager (i.e. it is now persistent in the zodb)

  • finance workflow: None –> REVIEWING

  • the order is authorized - which means a payment request is made to pxpay.

If pxpay returns saying this is ok and here is the url to redirect to, then we update the finance workflow: REVIEWING –> CHARGEABLE –> CHARGING (note: CHARGEABLE –> CHARGING is an automatic transition.

The user is redirected to the pxpay web interface to enter credit card details. The site then redirects them back to our callback and we negotiate a response message. This tells us whether the payment was successful or not.

If the payment was successful, then we update the finance workflow: CHARGING –> CHARGED

If the payment was unsuccessful, then we update the finance workflow: CHARGING –> PAYMENT_DECLINED

If there is an error in the communication with pxpay, then we update the finance workflow: * –> CANCELLED_BY_PROCESSOR with a comment that this was a communication error. We don’t destroy the cart though so the user can try again.

The error handler for a communications error is a utility so that it can be overriden easily, for example to redirect the user to another view.


  1. A developer account with PaymentExpress

  2. GetPaid core

  3. zc.ssl

  4. elementtree

  5. plone (tested on plone 3.1)


Darryl Dixon <> Matt Halstead <>


Project details

Download files

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

Source Distribution

getpaid.pxpay-0.4.tar.gz (30.8 kB view hashes)

Uploaded Source

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page